Aoe2scenarioparser

Latest version: v0.2.15

Safety actively analyzes 703159 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 18

0.1.52

Fixed

- Issue when updating `TerrainTile` list in the map manager
- Not all player resource names being present in the resource name file

---

0.1.51

Added

- `Attribute.FORAGING_WOOD_PRODUCTIVITY` -- [40] (Alian)

Fixed

- Warning showing more bytes were found in scenarios
- Present since 31st of January console update with '_no functional changes_'.
- Minor docstring copypasta mistake (`VictoryTimerType`)

[40]: https://github.com/KSneijders/AoE2ScenarioParser/pull/40

---

0.1.50

Added

- New error message for certain type of errors which might help find the cause of the issue faster.
- New unit to the `UnitInfo` dataset, named: `Sogdian Cataphract`.
- **Deprecation** warning to `scenario.remove_store_reference()`, see the docstring for more info.

Updated

- Scenario store now uses `WeakValueDictionary` instead of normal dictionary.

Fixed

- Multiple issues when printing an effect with `selected_object_ids` that had invalid references.
- Issue when trying to write a scenario with an effect containing an invalid effect ID.

---

0.1.49

Added

- **[API Docs (Beta)](https://ksneijders.github.io/AoE2ScenarioParser/api_docs/aoe2_scenario/)**!
- `corner1` and `corner2` attributes to the `Area` object.
- The ability to use `Area` objects without linking them to a scenario.
- Example: `area = Area(x1=0, y1=0, x2=5, y2=5)`.
- Example: `area = Area(corner1=Tile(0, 0), corner2=Tile(5, 5))`.

Updated

- Warnings now use the [Python built-in warning system](https://docs.python.org/3/library/warnings.html).

Fixed

- Issue when copying the entire terrain list to another scenario (`mm2.terrain = mm.terrain`).
- Issue when using UTF-8 characters in fixed length strings.

Removed

- The `create_hill` function in the map manager. Use `set_elevation` instead.

---

0.1.48

Added

- More ways to get access to scenario object and its managers without having to drag them everywhere.
- `scenario <object>.get_scenario()` i.e. `scenario = trigger.get_scenario()`
- `scenario = AoE2DEScenario.get_scenario(obj=trigger)`
- `scenario = AoE2DEScenario.get_scenario(name="coolname")`
- You can set the names like this:
1. Defaults to filename: `AoE2DEScenario.from_file('path/coolname.aoe2scenario')` (name: coolname)
2. Explicitely setting the name: `AoE2DEScenario.from_file('path/othername.aoe2scenario', name="myname")` (name: myname)
- Time indicators for status messages and execution time per scenario

Fixed

- The `EnableTechnologyStacking` effect missing the `quantity` attribute.
- The `item_id` attribute not updating properly for all use cases.
- The `ChangeView` effect missing the recently added (to this effect) `quantity` field.
- An issue that occurred when reading scenarios which had the `civ` field set to `0`.
- An issue with copying `Variable` objects from one scenario to another.
- The ordering of units returned from `object` data triggers not being consistent with the condition/effect input order

---

0.1.47

Fixed

- Issues with reading new 1.47 scenario

---

Page 7 of 18

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.