Skip to content

docs: add text output section to C++ code standards #1178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Nyeriah merged 2 commits into from
Mar 19, 2026
Merged

docs: add text output section to C++ code standards #1178

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
097361d
docs: add text output section to C++ code standards
Nyeriah Mar 13, 2026
7413c31
Potential fix for pull request finding
Nyeriah Mar 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/cpp-code-standards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,3 +329,13 @@ All Header files should contain header guards

#endif // MY_HEADER_H
```

### Text Output

All C++ script/system/command text output must use [acore_string](acore_string) whenever possible (e.g., ChatHandler messages, script system messages).

NPC dialog, emotes, and other in-game text that is managed via database text systems (such as `creature_text`, `broadcast_text`, etc.) should continue to use those systems instead of `acore_string`.

When adding new strings, localization must be provided for all available languages.
Copy link
Copy Markdown
Member

@Kitzunu Kitzunu Mar 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is eh in my mind


**Tip:** You may use AI to assist with translating localization strings.
Loading