64 | | r20084, r20085, 20086 Convert the Introductory Tutorial to a tutorial map[[BR]] |
| 73 | r20084, r20085, r20086 Convert the Introductory Tutorial to a tutorial map[[BR]] |
| 74 | r20115, r20117, r20118 Allow selecting biomes for random maps[[BR]] |
| 75 | r20123 Speed up target finding for gaia wolves on polar sea[[BR]] |
| 76 | r20127 Move the random biome code to a new library[[BR]] |
| 77 | r20129 Move biome definitions to JS and JSON files to allow mods to add new ones easily[[BR]] |
| 78 | r20131 Remove hardcodings to allow mods to remove biomes.[[BR]] |
| 79 | r20139 Biome descriptions[[BR]] |
| 89 | r20120 Allow specifying the gravity affecting projectiles |
| 90 | |
| 91 | This allows for different flight paths (eg mortars, magical projectiles). |
| 92 | |
| 93 | To keep the same behaviour as previous iterations of the game add `<Gravity>9.81</Gravity>` to the `<Attack>` tags of your templates.[[BR]] |
| 94 | r20141 Add -unique-logs parameter to make debugging of OOS issues locally easier[[BR]] |
| 95 | r20181 Move placeable templates out of special/. |
| 96 | |
| 97 | Specifically `special/territory_pull` is now `other/territory_pull`, and `special/trigger_point_[A-K]` are `trigger/trigger_point_[A-K]`, update your map xml files and trigger scripts accordingly. |
| 98 | |
| 99 | This is part of a change from a placeable filter approach (where one has to explicitly list all folders/templates that can be placed in atlas) to an unplaceable filter approach. This should make it easier for modders to use a different folder structure than the public mod, and having it work without any changes. We assume that adding unplaceable templates happens less often and that modders will notice if they can suddenly place something they added that shouldn't be placeable.[[BR]] |
| 100 | r20196 Add FloatDepth property to Position. |
| 101 | |
| 102 | This allows to have amphibious units that swim at a certain depth. |
| 103 | |
| 104 | To keep the current behaviour add `<FloatDepth>0.0</FloatDepth>` to all `<Position>` tags of your templates (probably as high up in the inheritance hierarchy as possible).[[BR]] |