*.vcproj.*.user files contain user specific settings.
*.vcproj.user files contain general settings, e.g. for the debugger, which
are required for our unit tests.
This macro causes OOS because it changes the gamestate during the unsynced ai_turn event.
Also it doesn't handle custom recall costs.
This commit also fixes MAKE_AI_SIDE_PERSISTENT. But i think this macro should be removed too since just writing 'persistent=yes' in [side] is much easier to understand than using this macro.
* HttT S19c: Change dialog about direction options, preparing for map change.
* HttT S19c: comment change missed in previous commit.
* HttT S19c: Remove the undead.
* HttT S19c: Remove the swamp from the map, replace with mountains.
* HttT S19c: Adjust side #'s to compensate for removal of undead.
* HttT S19c: Simplify dialog about impassable mountains.
* HttT S19c: Add changelog entries.
Both bugs had the same effect: if a unit could not get to its goal
location, goto moves by all other units during the same turn were
abandoned. However, there were two separate causes for:
1. The goal location was unreachable. This was due to a typo in the
code.
2. The goal was theoretically reachable, but blocked by allies. In this
case, it could happen that the unit did not move, resulting in the CA
being blacklisted.
I may be a pedant, but it's not correct to use 'the most' when referring to the greater of only two things. Plus, I don't really think the bad grammar adds any 'character' here.
apply_to=variation/type should have no effect when object were reapplied for example at unit creation. This is also the 1.12 behaviour. This also prevents infinite recursion.
Currently t_string isn't threadsafe, of one thread executes a 't_string
a("a")' and another threads does 't_string b("b")' the progamm might
crash even of those object are completeley unrelated at first glance.
This commit tried to fix this by wrapping the acces to the shared
hash_map object in mutex locks, another attempt to fix this problem
might be to remove the shared hash_map implementation of t_string
completeley. Unfortunateley i don't know why it was implemented this
way in the first place so i don't know which disadvantages removing it
would have.
