FYI these will be tested in our next build.

[siRkid]

I am putting these out because they were requested by the players who post on this board. I thought you might like to know we are working on some of your sujestions.

1. There is now an added demolition routine that looks at the number of engineers at a base when it is captured and gives them a chance to damage factories, airfields and ports before the capture.

2. On the TF orders screen there are now values for the TF AA (derived value), Guns (derived value), Torpedoes (number of tubes), and ASW (derived value), and with each of the 4 a percentage representing the percentage of ammo of that type remaining On the list all TF screen we have added ammunition remaining for AA, Guns, Torpedoes, ASW.

3. Add Max range for air groups which allows players to set a range which the air unit will not exceed when flying strike missions.

[Flying fortress]

3. Add Max range for air groups which allows players to set a range which the air unit will not exceed when flying strike missions.

Thank God!!!:D

Any chance to set a option that says:

Do not fly without fighter escort
Fly without fighter escort

[siRkid]

Originally posted by Flying fortress
Thank God!!!:D

Any chance to set a option that says:

Do not fly without fighter escort
Fly without fighter escort

I knew you guys would like this one. We can always ask.

[Luskan]

I like all of them.

[mogami]

Originally posted by Flying fortress
Thank God!!!:D

Any chance to set a option that says:

Do not fly without fighter escort
Fly without fighter escort

Hi, Just set max range to max range of fighters. Poof bombers will not fly without escorts. (unless you forget to set fighters to escort) If you want them unescorted don't set fighters to escort or set range beyond fighter range.

[von Murrin]

Beautiful!

Like everyone else, I'm quite pleased with #3 in particular.

Oh, and if a way to get CV CAP to only fly when needed (i.e. attacked) could be added somewhere down the road, I wouldn't need to die to go to heaven. :p

[caine]

I think these are very good choices.Anyway, what about having the option to maintain a Task Force a number of hexes away (if possible) from enemy airfields during movement? In that way, we could avoid massive air attacks against those Task Forces.

[Mike Scholl]

Originally posted by Kid
I am putting these out because they were requested by the players who post on this board. I thought you might like to know we are working on some of your sujestions.

1. There is now an added demolition routine that looks at the number of engineers at a base when it is captured and gives them a chance to damage factories, airfields and ports before the capture.

This is a step in the right direction, but puts a premimum on
the engineers present when the base falls. The Dutch had very
few engineers in the East Indies, yet did a better job of demo-
lition than the rest of the Allies simply because they "read the
handwriting on the wall" and prepared to destroy their
facilities ahead of time. Any chance of a "prepare for demolition"
order that would increase the amount of damage when a facility
fell based on the length of preparation?

Point 3 will be greatly appreciated by every player I know...

[madflava13]

Mike,
I'm not very familiar with the Dutch actions in the opening days of WW2, but it seems to me that prepping things for demolition still requires engineers. Is it possible that engineers had at some point been at the Dutch bases (setting up demo charges, etc.) and then left the grunts to light the fuse?

[worr]

Originally posted by Kid
3. Add Max range for air groups which allows players to set a range which the air unit will not exceed when flying strike missions.

Praise the Lord, and pass the ammunition.

Can we get this UV too?

Worr, out

[TIMJOT]

Originally posted by Mike Scholl
This is a step in the right direction, but puts a premimum on
the engineers present when the base falls. The Dutch had very
few engineers in the East Indies, yet did a better job of demo-
lition than the rest of the Allies simply because they "read the
handwriting on the wall" and prepared to destroy their
facilities ahead of time. Any chance of a "prepare for demolition"
order that would increase the amount of damage when a facility
fell based on the length of preparation?

Mike,

I think it would be a mistake to have a prepare for demolition order. If it were available, wouldnt most players imediately prepare all bases for demolition on turn one, making successful demolition a foregone conclusion?

Successful demolition had more to do with the will and the means than advance prep. For instance the Brits in Malaya had longstanding denial protocals yet when pushed came to shove the troops responsible panicked and bolted leaving most of the northern air bases instact. The Dutch on the otherhand may not have had many military engineers but they did have an abundance of qualified civilian oil and mine workers adept at handleing explosives along with Dutch resolve to carry it through.

IMO engineers presence coupled with some sort of morale check is the way to go, because if you do not have the means (aka engineers Knowhow & explosives ) or the will then no amount of prep time is going to get the job done. In the special case of the Dutch I would simply add engineer squads to the Dutch garrison units to model their intrinsic civil engineer capabilities.

[Nikademus]

I would agree that having a voluntary demolition order would be very vulnerable to "abuse" via the "hindsight" factor. Kind of similar to why the "scuttle" feature cannot be selected unless a certain level of damage is present.

Testing should give us a better idea of how it works within the greater framework of the game.

[Drongo]

Just to let you guys know,

the new WITP Alpha was released today and I've just finished a quick play with some of the new features/changes (there are far more new ones than those listed at the start of the thread).

To put it mildly -

It is really starting to shape as the dream game for many (I wont say all :p ) of those players who had pet hates about some of UVs routines (or lack of).

I'm sure the other testers will elaborate (if allowed) while I'm away on holidays.

Cheers

[siRkid]

It's hard to tell what is ok to release and whats not but I think it won't hurt to let these three out of the bag.


1) Set Speed (allows the TF to be told to always move at full speed, always move at cruise speed, or follow commander’s discretion which is the current method of speed selection used in UV).

2) Reaction range. This can be set between 0 and 6 and determines the maximum number of hexes the TF will move if it reacts to the enemy – this can be impacted by the Set Speed order because if it is set to always move at cruise speed the TF will never react more than cruise speed distance – also, if 0 is selected, air combat TFs will not make the automatic one hex move to close with enemy carriers. This reaction range takes the place of the old React/Do not React order. If you don’t want an Air Combat or Surface Combat TF to react, set this value to 0.

3) Unload/Don’t Unload which allows you to tell a TF not to unload cargo when it reaches its destination hex but instead to remain loaded.

[siRkid]

Originally posted by Drongo
Just to let you guys know,

the new WITP Alpha was released today and I've just finished a quick play with some of the new features/changes (there are far more new ones than those listed at the start of the thread).

To put it mildly -

It is really starting to shape as the dream game for many (I wont say all :p ) of those players who had pet hates about some of UVs routines (or lack of).

I'm sure the other testers will elaborate (if allowed) while I'm away on holidays.

Cheers

Hey who authorized any holidays?

[Apollo11]

Hi all,

Originally posted by Kid
It's hard to tell what is ok to release and whats not but I think it won't hurt to let these three out of the bag.


1) Set Speed (allows the TF to be told to always move at full speed, always move at cruise speed, or follow commander’s discretion which is the current method of speed selection used in UV).

2) Reaction range. This can be set between 0 and 6 and determines the maximum number of hexes the TF will move if it reacts to the enemy – this can be impacted by the Set Speed order because if it is set to always move at cruise speed the TF will never react more than cruise speed distance – also, if 0 is selected, air combat TFs will not make the automatic one hex move to close with enemy carriers. This reaction range takes the place of the old React/Do not React order. If you don’t want an Air Combat or Surface Combat TF to react, set this value to 0.

3) Unload/Don’t Unload which allows you to tell a TF not to unload cargo when it reaches its destination hex but instead to remain loaded.

Oh my... oh my... I am speachless...

WOW !!!


Leo "Apollo11"

[TIMJOT]

Fanstastic! improvements, especially #3, no more sailing convoys in circles in mid ocean just to keep them from unloading.

[Sonny]

Originally posted by TIMJOT
Fanstastic! improvements, especially #3, no more sailing convoys in circles in mid ocean just to keep them from unloading.

Got that right!!

These features are great! And you can keep your commanders in line or let them do their thing.

[dwesolick]

All of the changes sound great!!!!!!!!!! WitP sounds like it is shaping up as the best wargame...EVER! (Until Matrix does a WitP-style Russian Campaign )

A simple way to handle base demolition might be something like this: A player would click the "base demolition" button and (starting by the next turn) the fuel and supply in the base would immediately degrade...perhaps by 5%, 10%, or 20% per turn, depending on number of engineers in hex. If no, or few, engineers, then 5%, if lots, then 20%. This seems like it would provide a DIS-incentive to players setting demolition too early, they would, after all, be blowing up their own supplies, and, in case the base was held, or the enemy went elsewhere, the player would have to laboriously rebuild.

I guess it could work the same for demolition of airfields/ports/oil fields. Say, 1 point reduction every two or three turns with few engineers, 1 point per turn with lots of engineers.

Just thinking out loud. Either way, the game is going to be great. Can I just buy my copy now????:D

[Tanaka]

Originally posted by Kid
It's hard to tell what is ok to release and whats not but I think it won't hurt to let these three out of the bag.


1) Set Speed (allows the TF to be told to always move at full speed, always move at cruise speed, or follow commander’s discretion which is the current method of speed selection used in UV).

2) Reaction range. This can be set between 0 and 6 and determines the maximum number of hexes the TF will move if it reacts to the enemy – this can be impacted by the Set Speed order because if it is set to always move at cruise speed the TF will never react more than cruise speed distance – also, if 0 is selected, air combat TFs will not make the automatic one hex move to close with enemy carriers. This reaction range takes the place of the old React/Do not React order. If you don’t want an Air Combat or Surface Combat TF to react, set this value to 0.

3) Unload/Don’t Unload which allows you to tell a TF not to unload cargo when it reaches its destination hex but instead to remain loaded.

#2- Does this mean surface task forces will still only react to enemy task forces at a friendly base or has this been changed as well?