Setup
Configuration Standards
How to edit Iconix configuration files without breaking update paths or production behavior.
Configuration principles
Keep local changes deliberate, documented, and easy to reapply after updates.
Do not hard-code player identifiers in unrelated logic.
Prefer adapter configuration over editing core files.
Keep a copy of changed config files in version control.
Environment-specific values
Separate staging and production values when a resource connects to permissions, Discord roles, or external APIs.
Before release
Treat config changes like releases.
- Test normal flow.
- Test permission denial.
- Test resource restart.
- Test player reconnect.
- Document changes.
Need product-specific instructions?
Open the related product documentation from the sidebar, or ask Iconix support with your framework and dependency list.