The current impl of demographics does not function against the non english lodestone. Re-implement this in such a way it captures it into a numeric value first, then translates it out as requested.
In doing so we will save space on messages for consumers too.
Use Case
As a consumer o
Proposed Solution
Map lodestone value --> numeric enum.
Numeric enum then can be mapped out to translated value either as part of function. Or by calling a separate translation function post-collection.
Values should be recorded in lodestone alphabetical order for ARR races, then based on date added
Other information
No response
Acknowledge
[ ] I may be able to implement this feature request
Description
The current impl of demographics does not function against the non english lodestone. Re-implement this in such a way it captures it into a numeric value first, then translates it out as requested. In doing so we will save space on messages for consumers too.
Use Case
As a consumer o
Proposed Solution
Map lodestone value --> numeric enum.
Numeric enum then can be mapped out to translated value either as part of function. Or by calling a separate translation function post-collection.
Values should be recorded in lodestone alphabetical order for ARR races, then based on date added
Other information
No response
Acknowledge