Aoe2scenarioparser

Latest version: v0.2.15

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

Scan your dependencies

Page 13 of 18

0.1.16

Fixed

- Type validation in dataset functions. -- [25] (Alian713)
- Issue with creating modify_attribute effect.

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

---

0.1.15

Added

- **Alian713** as an author! **The dataset wizard!**
- Filters to dataset functions. -- [22] (Alian713)
- `CORRUPTION` and many `MODDABLE...` to the `TerrainId` dataset. -- [24] (Alian713)

Improved

- Doc strings, error messages and type annotations for datasets. -- [24] (Alian713)

Fixed

- Issue with order lists updating when directly removing items from the list (using `.pop()` or `.remove()`)
- Issue with reading `1.40` maps.

[22]: https://github.com/KSneijders/AoE2ScenarioParser/pull/22
[24]: https://github.com/KSneijders/AoE2ScenarioParser/pull/24

---

0.1.14

Fixed

- Issue with converting `armour_attack_quantity` and `armour_attack_class` inside the parser.
- Some missing attributes for the newly added effect and condition attribute.

---

0.1.13

Fixed

- Issue with displaying `armour_attack_quantity` and `armour_attack_class` as `None` in `get_content_as_string()`.
- Issue with writing scenarios where `quality` was non truthy but not `None`.

---

0.1.12

Added

- Support for the old `1.36` scenario file version. (Used for many campaign scenarios)
- Colourful print statements!
- Warnings for certain situations.

Fixed

- Issue with the `quantity` field with the effect `Modify Attribute` when choosing attribute `Attack` or `Armor`.
- Issue in manager construction phase while loading older scenarios.
- Issue with when committing `RetrieverObjectLink` with `support` attribute.

Reworked (backend)

Only useful if you're working with the 'sections' parts of the parser:

- The `armour_attack_quantity` and `armour_attack_class` fields have been removed from the sections (structure file).
They are still available in the effect object, and are split using bitwise operations in the `Effect` object itself.

---

0.1.11

Fixed

- Issue with adding effects to any trigger [Issue 21].

[issue 21]: https://github.com/KSneijders/AoE2ScenarioParser/issues/21

---

Page 13 of 18

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.