- A new property to the `Area` object: `Area.maximum_coordinate` - Mimics the previous behaviour of `Area.map_size` (read fix below)
Fixed
- The `Area` object returning the wrong `map_size` value (returned `map_size - 1`) - This also impacts multiple related functions which used it internally
---
0.1.69
Many thanks to `Alian713` for all his dataset work! ❤️
Fixed
- Outdated datasets (Updated to match UGC Guide) (Thanks Alian) - Internal scenario name not matching new filename on writing - Affected the names of data files created by XS
---
0.1.68
Added
- Ability to register functions to run on scenario write for easier 3rd party support - Can be used as a `scenario.on_write` decorator or called directly
---
0.1.67
Fixed
- Effect `change_object_civilization_name` missing the `source_player` attribute
---
0.1.66
Added
- 3 new functions to the `Area` object - `move()` move the selection relatively by an x/y offset - `move_to()` move the selection to a coordinate from on any corner of the selection - `is_within_bounds()` see if the selection is currently within the bounds of a map size - 1 function to the `UnitManager` - `clone_unit()` clone an existing unit and only edit attributes you like to edit
Fixed
- Missing `TechInfo.SAVAR` entry - XS code being duplicated if it was added through the `XsManagerDE.add_script(...)` and it was called in between two `XsManagerDE.initialise_xs_trigger()` calls