As mentioned earlier, the reduction of the flame tank cost from $800 to $600 made it a bit too powerful. Playtesting with damage reduced to this level seemed to be reasonable.
The reason for reducing the cost to $600 was that few people were playing with the flame tank, since it costed a lot more than other units like the light tank. It seemed to be too much of a specialist and the added construction time (and cost) didn't appear to be worth it to players. It also seemed that people were not interested in risking the unit in battlefield offensives due to its cost. Part of the changes to the unit (increased damage vs. light, heavier armor, lower cost) were to make it more accessible for use against light vehicles (such as artillery), which it can destroy quickly, but which often result in its own death. A lower cost made the unit more usable in most mixed forces.
In playtesting, the Flame Tank has shown to be too powerful, especially when combined en masse with recon bikes. This is because its cost was reduced to $600 from $800. Reducing a few traits in further playtesting has made it more balanced.
Removes final set of 16 sequences for all walls as it appears that these
are not actually supposed to be used as damage states for the actual
wall, but as end pieces for each wall. One of the pieces in particular
caused a single wall to be seen as invisible. Fixes#5654
Allows for any helicopter to enable or disable the turn before landing
but sets it to default off for the chinook. (may be desireable for
single player missions visual effect like Allies01?) Also gives the
chinook a faster ascend/descend speed. Fixes#5054
- Change Map.LoadMapTiles and Map.LoadResourceTiles to read the whole stream into memory before processing individual bytes. This removes the cost of significant overhead from repeated calls to ReadUInt8/16.
- Remove significant UI jank caused by the map chooser by not including the placeholder widget. The maps render fast enough that it is no longer worthwhile and it was causing a lot of flushes which were the source of the jank.
- Trigger async generation for all maps when the chooser is loaded. This means in practice all previews will be ready by the time the user begins to scroll the selection. Since generation is fast, there is no issue with scrolling straight to the bottom and having to wait for the backlog to clear.
