1. About RankedTiers
RankedTiers is a Minecraft PvP tier-testing community. Players are tested by approved testers in specific gamemodes and earn a tier that appears on the tierlist.
Tests are not tied to one official server. Testers and players pick any Minecraft server they like (see section 3). A Discord bot runs queues, tester roles, strikes and permissions.
Items marked [CONFIRM] are values the owners set (exact cooldowns, durations, channel and command names).
2. Staff Roles at a Glance
| Role | Purpose | Key requirement |
|---|---|---|
| Helper | Support and first-line moderation | 1 week trial period |
| Tester | Run tier tests per assigned gamemode | Min. 14 players/week in each assigned gamemode |
| Moderator | Enforce rules and handle escalations | Consistent, fair enforcement |
| Regulator | Look after testers and helpers; keep staff numbers healthy | Professional at all times |
| Admin | Oversee the whole server | Accountable for every occurrence neglected |
Authority flows upward: Helper → Moderator → Regulator → Admin. A Tester role is separate and sits alongside Helper/Moderator duties; never mix hats inside one case.
3. How Tier Testing Works
- Request: the player requests a test in the request channel with gamemode, exact IGN and region.
- Queue: the player joins that gamemode's queue.
- Pull: a tester approved for that gamemode opens the queue (testers can only open queues for their own gamemode) and calls the next player.
- Ticket: a private test channel opens for the player and tester.
- Test: they meet on any Minecraft server they choose and play the test. The server must be low-lag with good ping for both the tester and the player; if either has bad ping, switch server or reschedule rather than scoring a laggy test.
- Result: the tester submits it; the bot assigns the tier role and the tierlist updates.
- Cooldown: a waiting period starts before the next test in that gamemode.
Tiers
High Tier (HT) and Low Tier (LT), ranked highest to lowest: HT1 > LT1 > HT2 > LT2 > HT3 > LT3 > HT4 > LT4 > HT5 > LT5.
Normal vs High test
Higher tiers may need a stricter, reviewed high test with a longer cooldown.
Cooldowns
Mandatory 7-day wait after each test so players cannot spam. Only authorised staff may reset one.
Unfinished tests
A test that cannot be completed is skipped/closed as discontinued, never scored.
4. Helper
Responsibilities
- Answer questions about testing, tiers, roles, the server and website.
- Help players request tests correctly (gamemode, IGN, region).
- Claim, resolve or escalate support tickets.
- Light chat moderation: remind, warn, report.
- Report scams, fake tier roles and staff impersonation immediately.
Helpers cannot
- Test players or decide/edit tiers or the tierlist
- Skip cooldowns or promise retests
- Strike testers, ban, or touch bot configuration
Daily checklist
- Claim open support tickets.
- Check request/queue channels for confusion.
- Skim chat for violations and scam links.
- Read staff pings; log notable cases before going offline.
Common questions
Use the request-test channel: pick gamemode, give exact IGN and region, wait for a tester. Do not ping testers.
Testers are volunteers, each limited to their own gamemodes. Wait times depend on availability and region.
Confirm the result was submitted, then escalate with IGN, tester and time.
On any Minecraft server you and your tester agree on, as long as it is low-lag and you both have good ping.
Result disputes and tester complaints
- Stay neutral; do not agree or disagree.
- Collect IGN, tester, gamemode, date/time, ticket link, evidence.
- Escalate to a Regulator or Moderator. Never promise a retest or tier change.
- Tell the player the case was forwarded.
5. Tester
Duties
- Open queues only for your assigned gamemodes.
- You may test on any server you want, but pick a low-lag one where you and the player both have good ping.
- Test patiently, fairly and by the same standard for everyone.
- Submit accurate results promptly after each test.
- Close unfinishable tests as discontinued; do not score them.
- Tell a Regulator about leave in advance.
Fairness rules
- Never test yourself, alts, or players you have a stake in (close friends, clan mates)
- No favours, payment, revenge or tier selling
- Never test a gamemode you are not approved for
Accountability
Misconduct, quota misses and bias lead to strikes issued by Regulators. Strikes are stored per tester and persist across bot restarts.
6. Moderator
Moderators enforce rules and take the cases Helpers escalate.
- Mute, kick and request/issue bans according to the table in section 9. [CONFIRM ban authority]
- Investigate suspected cheating, alts, boosting and tier manipulation with a Regulator.
- Review Helper tickets and support Helpers during trial.
- Log every action with user, reason and evidence.
- Recuse yourself from any case involving friends or personal conflicts.
7. Regulator
- Care: check in on testers and helpers, resolve friction, support new staff through trial.
- Quota oversight: track the 14-per-week per-gamemode quota and act on misses.
- Staffing: keep every gamemode covered; recruit testers and helpers when numbers drop (
/recruit tester). - Discipline: issue strikes (
/strike) fairly and with documented reasons. - Complaints: review tester bias and misconduct reports neutrally.
- Conduct: lead by example, stay calm, keep decisions consistent and private matters private.
Only Regulators may use /strike and /recruit tester.
8. Admin
- Own the server, bot and role setup (
/setup_roles,/setupstrikesand other configuration). - Make final decisions on appeals, bans and staff discipline.
- Handle bot bugs, missing roles and permission problems.
- Supervise Regulators and Moderators; step in on staff conflict or misconduct.
- Handle anything legal, safety-related or involving minors immediately.
- Guard tokens and access: never share credentials; keep staff permissions minimal and reviewed.
9. Conduct and Moderation
Use the lowest effective response: remind, warn, escalate.
| Violation | Helper action | Escalate to |
|---|---|---|
| Spam, caps, off-topic | Reminder, then warning | Moderator if repeated |
| Mild toxicity | Reminder, then warning | Moderator if targeted |
| Begging for tiers / pinging testers | Point to queue | Moderator if repeated |
| Harassment, hate, threats | Remove, report at once | Moderator / Admin |
| Scams, phishing, impersonation | Remove, report with evidence | Moderator + Admin |
| Cheating, alts, boosting, tier selling | Collect evidence only | Moderator + Regulator |
| Ads for other servers | Remove, warn | Moderator if repeated |
Durations for mutes and bans: [CONFIRM].
All staff
- Be kind, fast and consistent
- Quote the rule you enforce
- Escalate early with evidence
- Admit when you do not know
- Log every action
- Promise or hint at tiers
- Punish on rumour
- Argue publicly with players or staff
- Use powers for friends or revenge
- Leak staff channels or tickets
Tierlist integrity
No favouritism, no selling or trading tiers/tests/roles, no fake roles or edited screenshots, no alt or boosting abuse. Report with evidence instead of accusing publicly. Step aside if a case involves someone close to you.
Security
- Never share your Discord token, bot token or passwords. Staff never ask for them.
- Do not open files or links from unknown people.
- Enable two-factor authentication and report a compromised account at once.
Activity and discipline
Check the Discord daily [CONFIRM minimum]. Announce absences ahead of time. Discipline ladder: reminder, written warning, final warning, removal. Serious abuse (favouritism, leaks, selling tiers, harassment) can mean immediate removal. Promotion comes from activity, quality and trust, not from asking.
10. Escalation Guide
| Situation | Go to |
|---|---|
| Tester bias, misconduct, missed quota, rudeness | Regulator |
| Serious violations, ban requests | Moderator |
| Suspected cheating or tier manipulation | Moderator + Regulator |
| Result or role not applied, bot bug, permissions | Admin |
| Staff conflict, legal, safety or minors | Admin immediately |
Escalation format
Case type: Player IGN / Discord: Tester (if relevant): Gamemode: Date and time: Summary (2-3 lines): Evidence / ticket link: What I already told the player:
11. Quick Reference
Bot commands
| Command | Who |
|---|---|
| Queue / test commands | Gamemode testers (own gamemode only) |
| Cooldown / profile lookup | Staff and players [CONFIRM name] |
/strike, /recruit tester | Regulators only |
/setup_roles, /setupstrikes | Admins only |
Message templates
Hi! I'm [name] from RankedTiers support. What can I help you with?
Go to request-test, choose your gamemode, enter your exact IGN and region, and wait for a tester. Please don't ping testers.
I can't change results myself, but I've passed your case to senior staff with the details. Please share any evidence here.
Hi [name], reminder about rule [#]: [rule]. Please avoid this so we don't need to take further action.
Glossary
IGN in-game name · HT/LT High/Low Tier · FFA free-for-all · Duels one-on-one · Cracked non-premium account · SEA South-East Asia · Queue waiting list · Cooldown delay between tests · Strike recorded mark against a tester · Alt alternate account.