v0.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.

v0.8.0

General Search

v0.7.2

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

v0.7.1

• is_active boolean flag for effect types to determine what is really affecting the target (like -1 AP from bow).
• limit query parameter for all search endpoints to request more results from the search engine. defaults to 8 (like before).

v0.7.0

Ankama RSS, Twitter and Almanax Discord Webhooks

• Blacklisting
• Whitelisting
• Mentions based on Almanax bonus
• Previews (weekly, monthly, daily)

v0.6.0

• Adds all possible detail fields in the list endpoint using fields[]. example: fields[item]=description,recipe
• Adds a new (alias-)endpoint /all to every listing endpoint for easily getting all data with disabled pagination (page[size]=-1) and all possible additional fields for this type.

v0.5.6

Adds more examples.

v0.5.4

Removes has_-fields for preventing collisions with generated null checking functions.

v0.5.3

Fixes optional field[recipe] for items.

v0.5.1

First npm release.