Leonhard S.

Hey, thanks for the report! There is not much to add to your elaboration I think - that table has been flaky for years though, so adding a big "warning:...

Hi, thank you for the report! > [...] grenade assist experience events (IDs 550-555) unintuitively have character_id = killing player & other_id = player killed. So the `character_id` matches the...

The background polling required to detect the member change requires a scheduled task, which would have to be part of the trigger itself. This means that triggers must provide a...

*The following is an attempt to stick to a single `Event` object.* We cannot use the `auraxium.Event` initialiser to pass event-specific data; not without fighting pydantic over the initialiser. An...

Putting this on hold until #34 is resolved.

Closing as there is no real benefit to modelling this as a pseudo-event rather than a simple scheduled check. Users wanting to check for outfit joins are advised to just...

Hi, thanks for the report - good catch. The PS2 datatypes themselves had (now deprecated) overrides that would handle these optimizations, but these will be removed to remove redundancy and...

Fixed in [0.2.3](https://github.com/leonhard-s/auraxium/releases/tag/v0.2.3).

Hi, thanks for the report. I am unable to reproduce this issue with any of my characters - do you happen to have a character name or ID for which...

There is unfortunately not a lot I can do without being able to repro the issue. Could you share more details about your platform, Auraxium version, or an MRE?