Welcome to the Mod Credits Template page. Here, we provide essential guidelines for properly acknowledging the contributions of mod creators within the RageZone community.
When creating or sharing mods, it's important to give credit where it's due. This not only fosters a respectful community but also encourages collaboration and innovation among developers.
Below are some key points to consider when writing mod credits:
- Identify Contributors: List all individuals or teams who contributed to the mod, including artists, coders, and testers.
- Specify Contributions: Clearly state what each contributor did, whether it was designing assets, coding features, or providing feedback.
- Link to Profiles: If possible, include links to the contributors' profiles or portfolios to give them proper recognition.
- Respect Licenses: Ensure that you are following any licensing agreements associated with the assets or code used in your mod.
- Update Regularly: Keep your credits updated as your mod evolves and new contributors join the project.
By following these guidelines, you help maintain a positive and collaborative atmosphere in the RageZone community. Thank you for contributing to the world of modding!
A Ready-to-Use Credits Layout for Your Release Thread
Guidelines are easier to follow when you have a concrete structure to copy. The layout below works for most mod and server-file releases, whether you are posting a small texture pack or a full emulator rework. Paste it into your release post or a CREDITS.txt file in your download, then fill in each section.
Suggested structure
- Project name and version: the release name plus a version number or date, so readers know which build the credits apply to.
- Original authors: whoever wrote the base files, source or client you built on. If you forked someone's work, they go first.
- Core team: one line per person, with their forum username and role, for example scripting, map edits, 3D models or database fixes.
- Third-party assets and libraries: name each asset pack, tool or code library, its author and the licence it is released under.
- Testers and feedback: people who reported bugs or ran test servers. A short list is fine; leaving them out is not.
- Changelog of credits: a note such as "v1.2: added shader work by [username]" so contributions stay traceable across updates.
Common mistakes to avoid
- Vague thanks: "Thanks to everyone who helped" gives nobody real recognition. Name people.
- Dropping credits on repacks: if you repackage an existing release, keep the original credits block intact and add your own changes underneath.
- Assuming free means unrestricted: a free download can still require attribution or forbid commercial use. Read the licence or the author's terms before redistributing.
- Crediting without permission to share: crediting someone does not grant you the right to publish their private or unreleased work. Ask first.
When you are unsure who made something
Older MMO files often circulate through many hands, and the original author can be hard to trace. Say so honestly, for example "origin unknown, found in [release name]", and invite readers to help identify the creator. Searching older threads in the archive or asking in the forums often turns up the first poster. Before publishing, it is also worth rereading the forum rules on redistribution, since releases that strip or misattribute credits may be edited or removed by moderators.
Also on this site: Tips for producing a fascinating