You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix!(lua.utils): gamestate enhancement field uses localized text instead of stable key #194
After adding an enhancement to a playing card, the modifier.enhancement field in the gamestate response contains the localized text from card.ability.effect (e.g. "BONUS") instead of a stable identifier. This breaks any automation that depends on reading the enhancement type, especially in non-English locales.
Steps to Reproduce
Start a run
Add a playing card with an enhancement: add({"key": "H_A", "enhancement": "BONUS"})
Inspect the gamestate response
Expected Behavior
modifier.enhancement should contain a stable, locale-independent key (e.g. "m_bonus").
Actual Behavior
modifier.enhancement contains "BONUS" — derived from the English string "Bonus Card" via :gsub(" Card", ""). This breaks in other languages.
changed the title [-]fix(lua.utils): gamestate enhancement field uses localized text instead of stable key[/-][+]fix!(lua.utils): gamestate enhancement field uses localized text instead of stable key[/+]on Jun 12, 2026
Activity
[-]fix(lua.utils): gamestate enhancement field uses localized text instead of stable key[/-][+]fix!(lua.utils): gamestate enhancement field uses localized text instead of stable key[/+]feat(lua): migrate Enhancement enum from ALL-CAPS to m_* keys
feat(lua): migrate Enhancement enum from ALL-CAPS to m_* keys
S1M0N38 commentedon Jun 12, 2026
Following commits also move from custom defined enumns to key-based enumns in a similar spirit of transition from
BONUStom_bonus