ZaTiers Bot

This guide is for testers only.

It covers the normal testing flow from the moment a player opens a ticket to the moment the result is posted and the ticket is archived.

What Testers Actually Do

A tester has three jobs:

1. Pick up the right ticket.
2. Run the test properly.
3. Submit the final result correctly.

If you do those three things cleanly, the bot handles the rest:

• player profile update
• role update
• result embed
• ticket archive

Before You Start

Make sure you are only handling the gamemodes you were assigned to test.

If the bot tells you that you are not allowed to accept or submit a result for a gamemode, that means you do not have permission for that gamemode yet.

How A Test Starts

Players do not pick their own tier.

They use the public test panel, choose the gamemode they want, and the bot opens a private ticket.

When that happens:

• the tester role for that gamemode gets pinged
• the ticket shows the player IGN
• the ticket shows that the test is a First-To match

First-To Matches

ZaTiers uses First-To matches for testing.

That means you do not stop after a fixed number of rounds.

You keep fighting until one side reaches the target number first.

FT7

First player to reach 7 wins takes the match.

Example:

• Tester: 7
• Player: 5

The tester wins the match.

FT10

First player to reach 10 wins takes the match.

Example:

• Player: 10
• Tester: 7

The player wins the match.

Why We Use It

It gives a better read on actual skill.

One lucky round should not decide somebody's tier.

Step 1: Accept The Test

Once you are ready to take a player, use:

/accepttest player:<member> gamemode:<mode> format:<FT7 or FT10>

Example:

/accepttest player:@Jaeden gamemode:crystal format:FT10

This does two things:

• marks you as the tester for that request
• locks in the format you are using

Pick the format before you begin the test.

Step 2: Run The Match

Use the accepted format and play the test properly.

While testing:

• keep score carefully
• make sure both sides know the score
• do not guess the final score later
• do not let the player pick their own tier

Your job is to decide the final rank after the match.

Step 3: Submit The Result

When the match is finished, use:

/result player:<member> gamemode:<mode> rank:<tier> [wins] [losses] [notes]

Example:

/result player:@Jaeden gamemode:crystal rank:HT3 wins:10 losses:6 notes:Good mechanics, weak under pressure

What This Does

Submitting the result will:

• save the player's rank
• update their ZaTiers points
• update their combat rank
• assign the matching Discord role
• post the official result embed
• archive the ticket automatically

How To Pick The Rank

The format decides how long the test is.

The result of the match helps you judge the final tier.

The bot does not calculate the tier for you.

You decide the rank based on how the player performed in the set.

That means:

• score matters
• consistency matters
• overall skill matters
• one flashy round should not override the full test

When To Use Notes

Use notes when the result needs a bit of context.

Good examples:

• strong aim but poor consistency
• good crystal sense, weak under reset pressure
• close set, placed lower due to repeated mistakes

Do not write essays.

Keep notes short and useful.

If The Ticket Needs To Be Closed Without A Result

If a test is not finished, use:

/closeticket

Use this when:

• the player leaves
• the test is cancelled
• the ticket was opened by mistake
• the ticket is no longer usable

This cancels the active request and archives the ticket so the player can open a fresh one later.

Result Embed

When you submit a result, the official result embed shows:

• player mention
• player IGN
• gamemode
• assigned tier
• tester mention
• tester IGN
• match format
• score
• points
• combat rank

So if your Minecraft account is not linked to ZaTiers, your tester IGN may not show properly.

Tester Rules

• Only accept tests for gamemodes you are assigned to.
• Do not let players choose their own rank.
• Use FT7 or FT10 properly.
• Keep the score honest.
• Submit the final result as soon as the test ends.
• Close broken or cancelled tickets instead of leaving them hanging.

Quick Examples

Accept a crystal test as FT10:

/accepttest player:@Player gamemode:crystal format:FT10

Submit a result after the match:

/result player:@Player gamemode:crystal rank:LT2 wins:10 losses:8 notes:Solid test, needs better consistency

Close a dead ticket:

/closeticket

Final Reminder

The player requests the test.

The tester chooses the format.

The tester decides the tier.

The bot records the result.