View source for Test and Dev Team

==What is the Test and Dev Team?==
The HeRO Test & Dev Team, also called T&D or TD, is comprised of a group of players who want to help the server.
<br>
<br>
We discuss a variety of topics regarding potential future content, past content, bug fixes, etc. through different mediums such as a special T&D Discord, and a Kanban Board. We also have access to a test server in which we test content before releasing.
<br>
<br>
You can help by discussing and testing future content, or if you're inclined to create content, you can help out with game art such as or sprites/banners, 3d assets, and graphic editing in general, or coding such as scripting quests, features, etc. 
<br>
==Requirements To Join==
To join the Test & Dev team, you must meet the following requirements:
<br>
<br>
*Have been playing heRO for at least 2 months
*Must have been active for the past month
<br>
If you meet these requirements and would like to join, message GM-Ciar on the HeRO Discord Server or Forum, saying you want to join the Test & Dev team. 
<br>
==Rules==
All Test & Dev members must follow the rules listed below, in addition to the normal [[Server Rules]]:
<br>
<br>
*Access to the Test Server, T&D Discord, etc. is limited to members of the Test & Dev Team
*T&D discussions, projects, etc. are kept private and not shared with other players under any circumstance
*Members must be active participants of the group, and must test content at least once a month or two, to be considered active
*The test server is not for playing around. As its name indicates, it's for testing game content.
*Members must not abuse their access to T&D knowledge. Example of this includes but is not limited to using upcoming content knowledge to manipulate the market, etc. 
<br>
Note: Members removed due to inactivity may always rejoin. Simply contact the T&D recruiter GM.
<br>
==Additional Notes==
Currently, the T&D team is looking for new members. We're specifically interested in testers. 
<br>
<br>
A tester serves many important roles. There's a chance that you're going to play the game a lot, doing the same thing all over again, to find a way to break a game. Then, you will be going through a loop of finding and pointing out glitches, grammar mistakes, graphical or audio issues. Other times, you will writing about your first impressions about a certain feature in the game and your feedback to improve it. Another time you will be writing clear details of ways to consistently reproduce a bug. This will go towards providing information to the other developers on how to make game better.
<br>
<br>
You will be ensuring whatever you're testing gets released in top, assured quality. You are the person who can potentially make a difference between a bad, broken feature and a great feature!
<br>