Aoe2scenarioparser

Latest version: v0.2.15

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

Scan your dependencies

Page 8 of 18

0.1.46

Removed

- Development logging information

---

0.1.45

**Support for the new 66692 update!** (Scenario version 1.47)

---

0.1.44

Added

- String Table ID alternatives to `MessageManager` attributes.
- `message_manager.instructions_string_table_id = 123`

Fixed

- `Retriever.commit_callback` wasn't called on commit causing text fields on Effects to corrupt (sometimes)
- `UnitInfo.THIRISADAI` showing as castle unit in `UnitInfo.unique_units()`

---

0.1.43

Added

- The `MessageManager` (`scenario.message_manager`)
- The ability to change the 6 text fields in the message tab (instructions, hints, victory etc.)
- `MessageManager` documentation: [link](https://ksneijders.github.io/AoE2ScenarioParser/cheatsheets/message/)
- The `is_dirty` attribute to retrievers to see if they were manually changed (from outside managers)
- A setting that stops managers from overwriting dirty retrievers (on by default)
- `settings.ALLOW_DIRTY_RETRIEVER_OVERWRITE`

Changed

- **BackEnd**: Partially rewritten construct & commit logic (slight performance improvement)
- **BackEnd**: Renamed all references to `UUID` named: `host_uuid` to just `uuid`

---

0.1.42

Fixed

- Issue with `Effect.armour_attack_class` attribute not being displayed (correctly) when printing triggers/effects
- Incorrect ID for `EffectId.DISABLE_OBJECT_DELETION`

---

0.1.41

Fixed

- `DifficultyLevel.EXTREME` is now properly available. Representing `-1` `:yFE:`
- The `quantity` field not being shown when printing the `Difficulty level` Condition when the difficulty was set to `EXTREME (-1)`
- `TechInfo.INDIANS` not being renamed to `TechInfo.HINDUSTANIS`

---

Page 8 of 18

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.