balance: naming inconsistency in content data #105

Closed
opened 2026-03-23 15:41:37 -07:00 by hikari · 0 comments
Owner

Issue

There is a naming inconsistency in the content data files. Some entities use one naming convention whilst others in the same category use a different pattern, making the data harder to maintain and potentially causing confusion for players reading IDs in debug output or the codex.

Expected Behaviour

All content IDs within a given category should follow a consistent naming convention (e.g. category_number or category_descriptor_number).

Steps to Reproduce

  1. Review the data files in apps/api/src/data/
  2. Compare ID patterns within each category

Suggested Fix

Standardise all IDs within each category to follow the same naming pattern. Ensure any changes to IDs are reflected in all references (quests, unlock requirements, achievements, etc.).

Priority

🟢 Low — cosmetic/maintenance issue, no gameplay impact

This issue was created with help from Hikari~ 🌸

## Issue There is a naming inconsistency in the content data files. Some entities use one naming convention whilst others in the same category use a different pattern, making the data harder to maintain and potentially causing confusion for players reading IDs in debug output or the codex. ## Expected Behaviour All content IDs within a given category should follow a consistent naming convention (e.g. `category_number` or `category_descriptor_number`). ## Steps to Reproduce 1. Review the data files in `apps/api/src/data/` 2. Compare ID patterns within each category ## Suggested Fix Standardise all IDs within each category to follow the same naming pattern. Ensure any changes to IDs are reflected in all references (quests, unlock requirements, achievements, etc.). ## Priority 🟢 Low — cosmetic/maintenance issue, no gameplay impact ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-23 17:28:30 -07:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/elysium#105