Aoe2scenarioparser

Latest version: v0.1.67

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

Scan your dependencies

Page 10 of 14

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

---

0.1.10

**Support for the new 50292 update!**

Added

- Support for the new `1.42` scenario file version.
- The new attribute for conditions: `object_state` (Used in `objects_in_area`)
- The new `ChangeColorMood` effect (`trigger.new_effect.change_color_mood(...)`).
- The `ColorMood` and `ObjectState` dataset.

---

0.1.9

**More datasets! Including some from the newest [47820] update!**

[47820]: https://www.ageofempires.com/news/aoe2de-update-47820/

Added

- The `HOTKEY_ID` property to the `UnitInfo`, `BuildingInfo`, `HeroInfo` and `TechInfo`.
Example: `UnitInfo.ARCHER.HOTKEY_ID`. Or: `UnitInfo.from_hotkey_id(...)`
- The `Hotkey` dataset. These values can be used for static key assignments.
- The `HeroStatusFlag` dataset. Use `HeroStatusFlag.combine(...)` for combinations in the dataset.
- The `BlastLevel` dataset.
- The `DamageClass` dataset. (Credits: Alian713)
- The `ProjectileInfo` dataset. Thanks **[Alian713](https://github.com/KSneijders/AoE2ScenarioParser/pull/16)**!

Fixed

- Removed `location_object_reference` from the `Change View` effect.
- Trigger docs not updated with the new `UnitInfo` dataset.
- `Unit.name()` when a unit wasn't present in the datasets. Thanks **[newtonerdai](https://github.com/KSneijders/AoE2ScenarioParser/pull/13)**!
- The ID for `FARMING_GOLD_TRICKLE` from 235 to 236.
- A typo `TechInfo.FELMISH_REVOLUTION` to `TechInfo.FLEMISH_REVOLUTION`

Changed

- Renamed ObjectAttribute `ICON_GRAPHICS_ANGLE` to `GRAPHICS_ANGLE`.
- Renamed all `area_1_x` attributes to `area_x1`. Same goes for: `area_1_y`, `area_2_x`, `area_2_y`.
- **BACKEND** - retrievers attribute on sections has been swapped out for retriever_map.
It's now a `dict` instead of a `list` with the retriever name as keys. Reason: **Improve performance**.

---

0.1.8

Updated

- Several speed improvements

Fixed

- Hint in exception message when it was clearly not the cause of the error.
- A typo in the condition dataset `OBJECT_IN_AREA` to `OBJECTS_IN_AREA`.
- Unit docs not updated with the new `UnitInfo` dataset - [Issue 12].

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

---

Page 10 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.