HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...
Ruleset-flexible combat duration
Right now combat happens in turns and ends "when one of the opponents is dead".
Instead, make it possible to have N rounds of combat. "N" will be defined in the ruleset, either globally, for a unit class or for each individual unit (preferably all of the above, with the more specific class overriding OR adding to the more general value).
Terrain can modify N, which is also defined in the ruleset (combat ends sooner in forest because it's easier to disengage or safely retreat).
For N=0 combat ends as before, "when one of the combatants dies".
#3 Updated by Marko Lindqvist about 3 years ago
- File 0066-Add-server-setting-combatrounds.patch 0066-Add-server-setting-combatrounds.patch added
- Status changed from New to Resolved
Attached patch implements something like that as a server setting.
Veterancy can be gained even if the combat does not end to the total defeat of one side. In fact, it's even possible that both sides gain veterancy in such a combat.
#5 Updated by Marko Lindqvist about 3 years ago
- Category set to General
- Assignee deleted (
- Sprint/Milestone changed from 3.1.0 to 3.0.0
This was requested by several people, so it makes sense to try to introduce this in 3.0 already, despite the risks associated with changing core assumptions of the combat code.