Dofusdude

Latest version: v0.9.0

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

Scan your dependencies

Page 1 of 3

0.9.0

- Adds `reward_kamas` field for Almanax.

0.8.3

- One item set bonus was impossible to differentiate from a two item set bonus. A new field is added now that explicitly shows the amount of items you need for each effect. The ordering inside the effects array is therefore irrelevant now but will be kept as is. This also introduces a new effects type since this only applies for sets.
- The list entries defined in the OpenAPI spec did not include all fields that can be included. Therefore the SDKs did not deserialize the entries correctly with list endpoints.

0.8.2

Increase Almanax look-ahead

0.8.1

Changelog

- conditions: Previously dofusdude only supported "and" -- now any combination of "or" and "and" with the `condition_tree` field is correctly modeled. The previous `conditions` field stays for backwards compatibility but it will only show "and" combinations, which can be wrong(!) if there are additional or's. Because of that, `conditions` is now marked as deprecated.
- titles: Titles are now correctly templated for items that have the effect.
- active effects: Weapons with '-1 MP' failed to be marked as active. Instead of detecting it by naming features, now a stable Ankama-internal flag is used for translating the API's `active` to Ankama's "used in a fight".
- search Almanax bonus: A new meta endpoint enables search for a bonus category. All dofusdude languages except "pt" are supported.
- search engine update: The search server jumped from 1.3.5 to 1.6.0, mainly for faster indexing which now leads to even faster startup and update circles.

0.8.0

General Search

0.7.2

- Added: persistent `id` field for item types
- Fixed: `highest_equipment_level` field for sets were incorrectly named `level` in SDKs.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.