Translations:Contributing/53/en

1. Coding standards
   • Use descriptive variable and method names.
   • Format code consistently (indentation, spacing and so on).
   • Write comments for complex logic.
2. Documentation
   • Update or add documentation for new or changed features.
   • Make sure this wiki reflects major changes.
3. Testing
   • Test thoroughly across the relevant scenarios, including a dedicated server (runServer) when your change touches client classes, networking or server logic.
   • Fix any linting or compilation issues before submitting your pull request.
4. Compatibility
   • Many systems read JSON that players, server owners and add-on authors edit (configs, quests, wishes, Dragon Ball packs). Don't rename or remove config keys, JSON fields, NBT save keys or registry names without discussing it first: older worlds and configs must still load.
   • Network packets are identified by registration order: add new packets at the end of NetworkHandler.register(), never in the middle.
   • Validate everything a client sends on the server; never trust the client for stats, unlocks, quests, wishes or progression.
5. Project docs
   • CLAUDE.md and the AI/ folder (Agents.md, Context.md, Memory.md, QuestAddonAPI.md) describe the architecture, data systems, build and release automation in detail. They are written for AI coding assistants but are just as useful for human contributors: read AI/Context.md before larger changes.