Welcome to the RageZone Release Tag Standards page. This guide provides essential notes for our community members on how to properly tag their releases.
When posting a release, it's important to use clear and consistent tags. This helps users easily find and categorize content. Below are the recommended standards:
- Game Type: Specify the genre (e.g., MMO, RPG, FPS).
- Platform: Indicate the platform (e.g., PC, Console).
- Version: Include the version number of the release.
- Status: Use tags like 'Beta', 'Stable', or 'Deprecated' to indicate the release state.
By following these standards, you contribute to a more organized and user-friendly forum experience. Thank you for being a part of the RageZone community!
Putting Release Tags into Practice
Knowing which tags exist is only half the job. The other half is applying them the same way every time, so that a member scanning the Releases section can tell at a glance whether a post is worth opening. A few habits make a big difference.
Order and formatting
Place tags at the start of your thread title, in a fixed order: game type, platform, version, then status. A title such as [MMO] [PC] [v1.2.0] [Stable] Custom Login Server Pack reads cleanly and sorts well when members search. Use square brackets, keep each tag short, and avoid stacking synonyms like [Beta] [Testing] [WIP] on the same post. One status tag is enough.
Versioning that means something
A version tag is only useful if it changes predictably. Many developers follow a simple major.minor.patch pattern: bump the patch number for small fixes, the minor number for new features that do not break existing setups, and the major number when users must reconfigure or migrate data. If your release targets a specific game client build, mention that client version in the first line of the post body rather than cramming it into the title.
Keeping status tags honest
- Beta should mean the release runs but still has known issues. List them in the post.
- Stable should only be used once the release has been tested beyond your own machine.
- Deprecated tells readers to move on. Link to the replacement thread if one exists, and leave the old post up so existing users can still find support history.
Remember to update the title when the status changes. An abandoned project still marked Beta years later wastes everyone's time.
What tags cannot replace
Tags help people find a release, but they do not explain it. Every release post should still include a plain description, setup requirements, credits for any work you built on, and clear notes on what has changed between versions. If you are unsure how to write good install steps, the Tutorials section has examples worth borrowing from. Posts that misuse tags or mislabel content may be edited by moderators, as covered in the forum Rules.
Also on this site: The very best intelligent guided