Larian Banner: Baldur's Gate Patch 9
Previous Thread
Next Thread
Print Thread
Joined: Jul 2013
S
stranger
OP Offline
stranger
S
Joined: Jul 2013
I think a change needs to be made in how the game determines when to auto resolve battles. If I'm not mistaken, currently the game will only auto resolve when both players choose that option, otherwise it goes into RTS mode.

I think this is a problem because a high percentage chance to win the auto resolve does not translate into a high chance to win the RTS battle because of how easy it is to build new units. This means that if you have a low chance of winning the auto resolve there really aren't many good reasons to auto resolve, your chances go up significantly of winning if you enter RTS mode.

One way to fix this would be to only allow one RTS battle per turn, players would have to strategically decide which battle they want to manage personally. If there is a disagreement between the players the game could randomly choose 1 battle for them to play.

It just seems right now that the more units you start out with in an RTS battle the more you stand to lose, when it should be the opposite, the guy with fewer units should be the one taking the risk.

Any other ideas? Or maybe reasons why I am wrong about this aspect of the game?

Joined: Mar 2003
Location: Canada
Support
Offline
Support
Joined: Mar 2003
Location: Canada

In the single player campaign you can only have one RTS battle per turn, and only assign each general to one battle when auto-resolving.

For multi-player I can see wanting to limit the number of RTS battles, but I think each player would have to be given an opportunity to chose one battle to do manually, otherwise you could have two home countries invaded in the same turn, which neither party would want to auto-resolve if they left it relatively unguarded.

There was talk at one point of the possibility a multi-player mode of just the strategy map part of the game (no RTS combat), but I don't know if it will be included.

Joined: Jul 2013
S
stranger
OP Offline
stranger
S
Joined: Jul 2013
That is a good point about having both home countries being invaded. It seems the way the game is currently there is little reason to spend much money on building units on the strategic map. Maybe that is what the developers intended, I guess you are supposed to just use hunters to get around really fast and then build your actual army in the RTS battle.

Joined: Mar 2003
Location: Canada
Support
Offline
Support
Joined: Mar 2003
Location: Canada

There is still time to balance strategy map vs RTS units. The latest beta reduces country populations, so that at least puts some restrictions on RTS unit building (which presumably was always intended, but I would assume not to the exclusion of building units on the strategy map).

Joined: May 2013
addict
Offline
addict
Joined: May 2013
I would add that a significant force of hunters and armors versus a small invading force still translates to an easy win: RUSH. The difference lies in amount of units lost. Auto-resolve tends to lose fewer units (except for cases like sending in 2 hunters and a transport against an opponent's 1 trooper resulting in total wipe out and the trooper still there).


Unless otherwise specified, just an opinion or simple curiosity.
Joined: Jul 2013
S
stranger
OP Offline
stranger
S
Joined: Jul 2013
It occured to me that another way to deal with auto resolve could be to allow each commander to choose 1 battle to command personally, BUT if they both pick different battles then both battles will be fought RTS style. That way you still have to prioritize which battles are most important for you to win.

My main concern is that currently a player who is good at the RTS part of the game has a significant advantage in a multiplayer campaign. He can easily win by personally commanding each battle. Limiting the number of RTS battles will help make the strategic map a more significant part of a multiplayer campaign.


Moderated by  Issh, Larian_QA, Raze 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.5