Matrix Games Forums

Max Rounds Per Battle
It is possible to set Max Rounds Per Battle (MRPB) value for a scenario by using the Edit > Set Max Rounds Per Battle item in the Force and Deployment Editor menus.

This value sets the maximum number of rounds that the attacking forces will execute, for all battles, in each series of combats. The default value is 99. The minimum value is 1 and the maximum is 99.

This value can have a wide variety of different effects, particularly when coupled with shock events. Low MRPB values can minimize “turn burn” but at the cost of attacks not having enough tactical rounds to retreat defenders. Low MRPB values can also yield better results from using tactical and local reserve deployment settings. You can more safely use progressively higher loss tolerance settings for attacks, with low MRPB values, since the number of tactical rounds that stubborn units continue attacks and defenses will be attenuated.

While some scenarios will benefit from very low MRPB values, it is generally not recommended to set it lower than 3, as this also attenuates the number of rounds that artillery, naval, and air units will bombard for, at their higher loss tolerance settings, and may also adversely affect the net bonuses that positive shock values have in reducing the number of tactical rounds expended during combat. It is recommended that scenario designers using shock events generally set this value to be no less than ((highest value shock – 70)/10). Your mileage may vary. Playtest for overall effect through the campaign.

Another effect to keep in mind when setting this value, is that the chance for ending the turn by a “proficiency check” is not affected. Thus, while players may realize more sets of attacks throughout their turn, with low MRPB values, they will conversely be more likely to have the turn ended (eventually) by a failed proficiency check, since one is made at the end of each series of attacks. See Turnover, on page 58.

Scenario designers who change this from the default should indicate in their scenario briefing, the value used.

ORIGINAL: JAMiAM
For the initial release, it will be limited to being set in the scenario editor, and once set, is in effect for both players during the course of the entire scenario. However, if it is well enough received, we might be able to talk Ralph into figuring out how to make the feature work, as a player-adjustable option, that can be changed over the course of the game, or even within a turn.

Modifiable by event, however, would be good.

ORIGINAL: golden delicious

I take it that with the value set at 99 the game will perform the same way it does currently?

ORIGINAL: ralphtrick

One thing that Jamian forgot to mention (I'm sure he just forgot [;)]) was that this a setting of 3 does NOT mean that combat will stop on rounds 4, 7 and 10. If you move a unit across the map and attack,using up 9 rounds in moving before attacking, The battle will start on round 9, and then last one round, and the turn will end. This is not something totally brainless that you can rely on, you're going to have to think a little, and make some decisions.

ORIGINAL: ralphtrick

One thing that Jamian forgot to mention (I'm sure he just forgot [;)]) was that this a setting of 3 does NOT mean that combat will stop on rounds 4, 7 and 10. If you move a unit across the map and attack,using up 9 rounds in moving before attacking, The battle will start on round 9, and then last one round, and the turn will end. This is not something totally brainless that you can rely on, you're going to have to think a little, and make some decisions.

ORIGINAL: JAMiAM

ORIGINAL: ralphtrick

One thing that Jamian forgot to mention (I'm sure he just forgot [;)]) was that this a setting of 3 does NOT mean that combat will stop on rounds 4, 7 and 10. If you move a unit across the map and attack,using up 9 rounds in moving before attacking, The battle will start on round 9, and then last one round, and the turn will end. This is not something totally brainless that you can rely on, you're going to have to think a little, and make some decisions.

I didn't "forget". More of an active neglect really, since it wasn't really necessary to mention that. The section quoted is where the feature is described in the manual and help files. The greater context of when battles begin, the use of the attack planner, sequencing, et cetera, is described in other portions of the manual and help files. It will fall on new players to read the manual to learn how to play the game, for returning players to refresh themselves, and for grognards to spot any changes we neglect to mention in the various preview and feature lists that we publish before the release.

ORIGINAL: Jeff Norton

Dumb question time, but what language is TOAW written in, if you can say?

ORIGINAL: ralphtrick

...several features crept up at the last moment. I think you'll like them.

Ralph
Programmer, TOAW 3

ORIGINAL: sstevens06

ORIGINAL: ralphtrick

...several features crept up at the last moment. I think you'll like them.

Ralph
Programmer, TOAW 3

Oh no, the dreaded 'scope creep!' [X(] (I'm sure it'll be worth the wait...thanks for the update.)

ORIGINAL: macgregor
I took the 'no news is good news' as a positive development. IOW it's good news in that Ralph is pleased with the progress, yet no news in that he can't say what that progress is yet. That's all I would expect. It's when nobody posts that I begin to think the progress has slowed.