3 of 23

TOURNAMENT

Schlumpf666aoe presents you with a unique 3v3 format team tournament.

Over the course of 6 weeks, the teams battle to see who has the best preparation. All teams are divided in 3 brackets based on their elo.

A special mapdraft allows the teams to prepare very well before the sets. But it also ensures that they have to play different maps from their own draft during the tournament, which makes it very diverse.

CONTACT

For any questions regarding the tournament or anything Admins:

related to the tournament please contact us via Discord: derhausmeister� chelbird�Host: aenybaenaeny schlumpf666aoe

SUMMARY

3 vs 3
Single elimination after group stage
Max. 5 player per team
3 best players elo used for seeding

1 set per week - max. 6 sets
Group stage - Best of 3
Quarterfinals + Semifinals - Best of 5
Finals - Best of 5

IMPORTANT LINKS

4 of 23

EVENT TIMELINE

Sunday August 20 Tournament Announcement

20:00 MESZ Live on stream

Sunday August 20 Registration open

20:00 MESZ

Friday September 08 Registration closed

23:59 MESZ

Sunday September 10 Seeding Announcement

20:00 MESZ Live on stream

Monday September 11 - 1 1 Set - Single-Elimination

Sunday September 17 BO3

GROUP STAGE

Monday September 18 - 2- 2-3 Sets

Sunday October 01 BO3

QUARTER FINALS

Monday October 02 - 1 Set - Single-Elimination

Sunday October 08 BO5

SEMI FINALS

Monday October 9 - 1 Set - Single-Elimination

Sunday October 15 BO5

FINALS + 3rd place match

Monday October 16 - 1 Set - Single-Elimination

Sunday October 22 BO5 played live on stream

MAIN EVENT

GOLD BRACKET

QUALIFIERS

REGISTRATION PHASE

5 of 23

GROUP STAGE

Wednesday September 20 - 2-3 Sets

Sunday October 15 BO3

QUARTER FINALS

Monday October 16 - 1 Set - Single-Elimination

Sunday October 22 BO5

SEMI FINALS

Monday October 23 - 1 Set - Single-Elimination

Sunday October 29 BO5 played live on stream

FINALS

Monday October 30 - 1 Set - Single-Elimination

Sunday November 05 BO5 played live on stream

GROUP STAGE

Wednesday September 27 - 2-3 Sets

Sunday October 22 BO3

QUARTER FINALS

Monday October 23 - 1 Set - Single-Elimination

Sunday October 29 BO5

SEMI FINALS

Monday October 30 - 1 Set - Single-Elimination

Sunday November 05 BO5

FINALS

Monday November 06 - 1 Set - Single-Elimination

Sunday November 12 BO5 played live on stream

MAIN EVENT

BRONZE BRACKET

MAIN EVENT

SILVER BRACKET

6 of 23

TOURNAMENT STAGE

The structure of each bracket depends on the number of teams per bracket.

For detailed information visit Toornament after the Seeding (September 10) is concluded:

https://play.toornament.com/de/tournaments/6976659768731033600/

After the first set (which is determined by seeding), winners and losers play against each other. Teams with two wins are qualified for Semi Finals.

Before each round, a civdraft must first be conducted.� The mapdraft is provided by the admins and created when both teams are set.

BEST OF 3

Before the first match starts, teams must complete a full civdraft. The left/upper team in Toornament of the match is the host of the draft.

Order of the games

GAME 1 Neutral map on the mapdraft

GAME 2 Map picked by the loser of game 1

GAME 3 Map picked by the loser of game 2

BEST OF 5

Before the first match starts, teams must complete a full civdraft. The left/upper team in Toornament of the match is the host of the draft.

Order of the games

GAME 1 Neutral map on the mapdraft

GAME 2 Map picked by the loser of game 1

GAME 3 Map picked by the loser of game 2

GAME 4 Map picked by the loser of game 3

GAME 5 Map picked by the loser of game 4

CIVDRAFT

7 of 23

PARTICIPATION

To participate in the tournament as a team, please follow the steps below.

Join the official Discord server used for the event. The Discord server will be used for updates prior to and during the event and actively used for scheduling and communication with other players or admins.
Please register for the event by using the following link: https://play.toornament.com/de/tournaments/6976659768731033600/
The registration will be accepted once the players have joined the Discord and the Elo verification has been successful to ensure a fair and competitive bracket.
Registration closes Friday September 08 at 23:59 MESZ

Teams may register with 3-5 players. The strongest three players will be used for seeding.

Please provide the following sign-up information for your team at Toornament:

Team name
Team captain (responsible for communication and scheduling)
Player information (for all players in the team)

Player name
aoe2insights profile link
Discord username
E-mail is not necessary, just type a fake mail into it, like test@rt.com

INSTRUCTIONS

Official Discord Server

Want to participate?

Participating teams

8 of 23

By registering for the tournament, all participants accept all rules and settings stated in this rulebook.
The in-game name must be pronounceable and must not contain insults and offensive words or language.
In case of multiple accounts, the account with the highest 1v1 rating must be specified during registration. A violation can lead to disqualification in case of damaging intent towards the tournament (smurfing for lower bracket).
If, despite the registration conditions (minimum 1v1 RM), the account has abnormalities (winrate, winning streak), the tournament hosts reserves the right to an individual examination, which may result in a refusal or adjustment of the Elo.
Participants are not allowed to register with an account that does not belong to them.
The tournament host reserves the right to refuse registrations.

§1 REGISTRATION REGULATIONS

To participate it is necessary to have read and understood all rules and conditions of participation. �
All participants must have joined the Discord server:

All participants must have played at least 50 1v1 ranked games on the main account, and at least 5 ranked games within the four weeks before the tournament starts.
If the above conditions are not (or cannot be) fulfilled, the tournament host reserves the right to permit or refuse participants to the tournament after individual examination.

§2 ELIGIBILITY

Official Discord Server

9 of 23

§3 BRACKETS

GOLD BRACKET

BRONZE BRACKET

SILVER BRACKET

To calculate the 1v1 elo, we run this formula:

current 1v1 elo * 0.66 + highest 1v1 elo * 0.34 = calculated 1v1 elo

If the respective requirements only apply to certain team constellations, the team can still register, but only play together in this constellation.

Players must have at least 1700 1v1 elo to participate.
This bracket has no elo restriction (highest elo).
This bracket is international.

The average of the top 3 players of the team must be under 1700 calculated 1v1 elo.
The calculated elo for the highest ranked player must be under 1800.
This bracket is for the german community only.
International teams can sign up via Discord #waiting-list-international-teams to enter the waiting list. Free spots will be filled up with the international teams from this list.

The average of the top 3 player of the team must be under 1350 calculated 1v1 elo.
The calculated elo for the highest ranked player must be under 1450.
This bracket is for the german community only.
International teams can sign up via Discord #waiting-list-international-teams to enter the waiting list. Free spots will be filled up with the international teams from this list.

QUALIFIER:

For each bracket there can either be 8, 12 or 16 teams. If there are too many registrations, there will be a qualifier including one set per team (Bo3, 11th - 17th of September) depending on their seeding, with the highest seeded teams automatically being qualified.

Participating teams

10 of 23

GENERAL GUIDELINES

Participants must own a legal copy of the game Age of Empires II: Definitive Edition.
If the game receives a patch during the event, the following matches will be played on the new one.
All DLCs are allowed, but not necessary.

§4 GAME & PATCH

Any attempt of cheating will be punished with the immediate disqualification from the tournament.
During a set any communication with third parties (all persons who are not opponents, team members who are playing the current map and admins) is prohibited. This includes being in a Discord channel, regardless of whether individual persons are “muted”, or being present during the game in a cast. It is recommended to seek out possible game broadcasts on Twitch only after the full set has been streamed.
The use of scripts and macros is strictly prohibited. Performing multiple commands with one action is considered illegal.

§5 CHEATING

All participants, streamers and administrators are obliged to behave respectfully towards others. This includes refraining from offensive statements, racism and sexism before, during and after the set and in the general environment of the tournament (Discord, Twitch).

Any violation will be taken seriously and should be reported to the administration immediately.

All participants must cooperate with an appropriate attitude and help in any situation to ensure the smooth running of the event.

§6 RESPECT & COOPERATION

11 of 23

§7 RECORDED GAMES

All games during the entire event must be recorded.

As soon as a game series has concluded, the team captain whose team is named in Toornament first must provide the recorded games in the #recorded-games of the tournament Discord. Potential restarts and restores must also be included. The civdraft must be added as well.

To save the games in the Discord, go to the tournament Discord in the #recorded-games channel.
Type in: /result
The AoE Tournament Bot creates a new private thread in that channel. Go on the left side to that new channel, called “result dialog…”.

Now follow the instructions of the Bot.
If you do everything correct, the recs appear in the #recorded-games channel.
If something goes wrong, try it again or ping the admins for help.

Players should arrive on time for a scheduled game. If no three players are present after 15 minutes, the team waiting gets an admin win for the first game.
After 30 minutes, the waiting team gets the win for this entire set.
In the circumstance that there are technical difficulties, a match date can be rescheduled at short notice.
If a team is unable to play at the scheduled time, it is their obligation to offer an alternative as soon as possible.
If there are significant difficulties in finding a new date, the admins must be informed immediately.

§8 PUNCTUALITY

12 of 23

If there is any violation of the handbook, the tournament host reserves the right to issue warnings or penalties.

These may range from written warnings to prize money reductions or disqualification.

Repeated rule violations may result in disqualification.

§11 PENALTIES

In the event of a game crash, out-of-sync, internet, power or PC failure, the game must be saved and restored. If a drop causes a clear disadvantage for a team, an admin should be contacted.
The team that caused the drop must take care of the restore.

If it's not possible to restore the game or both teams agree on a restart, the disconnected team gets the admin loss for this map.

§10 TECHNICAL ISSUES

The tournament host reserves the right to change the rules at any time.
The tournament host reserves the right to decide individually on all cases not covered by the rules.

§12 MISCELLANEOUS

After registration, all developments should be regularly followed on Discord and Toornament.

Communication with other participants takes place on the tournament Discord.
The tournament Discord must not be muted during the tournament period.
During a set both teams must be reachable via Discord for the administrators.

In case a game is casted live, both teams should ideally be in a voice channel on the Official Discord server.

§9 COMMUNICATION

13 of 23

EVENT SETTINGS

During the event, all civilizations (including DLC civs) can be played.
If a player selects a restricted civilization, the game must be restarted as soon as possible. The team with the wrongly chosen Civ can choose two of their remaining civilizations. The opposing team can then decide which of the selected ones they will play.

Prior civilizations, players positions and participating players for the restarted map must remain the same.

In each set, the team captains have the option to open a thread in the Tournament Discord channel #gold-civs/#silver-civs/bronze-civs to enter their chosen civs. This way you can avoid the penalty for picking the wrong civ. This is optional.
Teams may not re-select a civilization that has already been played in the matchup.

§14 CIVILIZATIONS

Teams will be seeded by 1v1 elo, using a mixture of current and peak elo, as well as the current elo of the top 3 TG elo scores in the team divided by the average top 3 TG elo scores across all registered teams. �

We will run this formula for every signed up player:

(a/b) * (c * 0.66 + d * 0.34) = X

a = average of the top 3 current TG elo scores within the team

b = average of the “a” parameter across all registered teams

c = current 1v1 elo of the player

d = highest 1v1 elo of the player

For the team-rating the combined rating of the strongest possible team/player-combination will be calculated.

§13 SEEDING

14 of 23

§16 MAP- AND CIVDRAFT

The mapdraft will be created by the admins, at least 1 day after the next opponent is known. In the tournament Discord under the #map-draft channel the mapdrafts are published and each team gets a ping after the draft is published.

Depending on the schedule, both teams have time to prepare for the maps.

The selected maps are chosen randomly based on 2 factors:

Home map
Every team chooses 6 maps before the start of the tournament as their homemaps.
The admins chose 1 map of that selection for the set randomly.
That map is blocked for the following set.

Neutral map
Every team selects 3 maps before the start of the tournament as their banned maps.

This selection only applies to the neutral map.

The neutral map is chosen by the admins randomly from all maps that are not picked as a homemap or banned from one team (before the tournament).
That map is blocked for the following set of each team.

�

Before the first match starts, the teams must complete a full civdraft. The left/upper team in Toornament is the host of the draft.

Players must choose their color according to their position and team.

Each team must use the color choice given below.

§15 COLORS

FLANK

+ + VS + +

POCKET

FLANK

POCKET

FLANK

Civdraft Best of 3

Civdraft Best of 5

15 of 23

MAPPOOL

RISING TEAMS MAPPACK

ARABIA

ARENA

BLACK FOREST

COASTAL FOREST

TEAM ISLANDS

BEACHFIGHT

CANBERRA

CHAOS PIT

DONUT

FOREST POND

FRONTLINE

NOMAD

16 of 23

MAPPOOL

The last 6 Maps, voted by the teams:

GOLDEN LAKES

GRAND BARA

GROSSROX

MAGHREB

RING OF REEDS

RIVULET

COLOSSEUM

DECENTRING

KAWASAN

REGICIDE FORTRESS

TEAM ACROPOLIS

TWO RIVERS

17 of 23

LOBBY SETTINGS

Players must find a server that provides an equally good connection for both.

In case of a problem, an admin should be contacted immediately to decide in case of doubt.

Hidden Civ has to be activated.
All lobbies must be hosted publicly.
Spectators must be allowed.
A spectator delay of 2 minutes is suggested but not a must.

§17 PRE-LOBBY

Both teams are equally responsible for the correct lobby settings. Make sure the lobby settings are correct before launching the game. Incorrect settings result in a restart.

§18 IN-GAME LOBBY

18 of 23

INGAME RULES

§19 RESTARTS

Sending of resources is allowed if the sending player is at least one age ahead of the receiving player or both have reached the Imperial age.

If slinged not compliant with the rules, the amount sent must be returned immediately (trading fees will be lost). If this is not the case and the resources are used and not returned immediately, the disadvantaged team can demand an admin win.

§20 SLINGING

A game is considered lost as soon as a player of the corresponding team resigns.

This rule does not apply for defeated players. Giving hints or generating other advantages by the insights of a defeated player is strictly forbidden.

§21 RESIGNATION

In general, restarts are not allowed.
Teams can request a restart if their map is bugged or otherwise incorrectly generated.

Nomad-Maps are an exception to that rule. Each team can request one restart.
For this, use the ingame chat, type “restart” and resign after that.

A restart must be requested within the first 4 minutes of a game.
When restarting, colors, civilizations and players remain the same.
Administrators reserve the right to restart a game at any time.

Conditions for a restart:

Missing resources
Resources that are significantly blocked (can be gathered from less than two sides)

In case of a bug related restart, please pause the game and contact your opponent and an admin.

If there is no admin available during the game time or is not responding within 5 minutes, it is up to the players to find a solution in mutual agreement.

19 of 23

Players are only allowed to pause a game if they or their opponent experience serious problems.

Pausing to take a breather, use the toilet, smoke or address any other non-technical or non-health concern is not allowed.

An administrator can order a break at any time for any reason.
The player who pauses the game must also be the player who ends the pause.

Before the break ends, it must be ensured that the opponent is ready for the game to continue.

§23 PAUSES

Laming is not allowed within the first 5 minutes of the game.

�Laming is understood as:

Killing or stealing enemy herdable or wild animals

Only in case of a nomad start: killing wild animals without gathering from them

Actively blocking or killing villagers that are hunting their own boars (excluding neutral ones like on beachfight)

Other vills may be attacked with a scout, e.g. a dock or walling vill

Interactions from villagers at the enemy base, such as vill fights, fighting buildings, deleting farms etc.
Walling in enemy ressources or villagers

�The following maps are exceptions from the laming rules described above: coastal forest, chaos pit, frontline, black forest

§22 LAMING

Intentionally utilising any bugs, glitches or errors in the game is strictly forbidden.

The tournament host has the right to give a restart if they deem it necessary due to the exploitation of a bug.

If in doubt, contact the administrators to ensure what is considered exploitation of bugs.
Should a new bug occur due to a new game version, this must be reported to the tournament host as soon as possible.

§24 EXPLOITS

20 of 23

PRIZEPOOL

§25 RULES & CONDITIONS

§26 PRIZEPOOL

The prizepool will be distributed via PayPal.
In the event of fraud, the administrators reserve the right not to pay out the prize money to a team.
The team captains of the eligible teams are responsible for coordinating the prize. Winnings will be equally distributed to each member of the teams if not stated otherwise.

The initial prizepool is $110. The current prizepool is $1000.
The prizepool is sponsored by Schlumpf666aoe.
Donations to https://matcherino.com/tournaments/99844/overview during the tournament will be added to the prizepool.
The prizepool splits into four parts: 50% for the winning team of the gold bracket, 25% for the second place, 15% for the third place and 10% for the fourth place.

21 of 23

CONTENT CREATION

The stream title must mention the name of the tournament (Rising Teams or RT) and the host (Schlumpf666aoe).
Streamers must add a command for the tournament in the chat: !rt → Rising Teams is a 3v3 tournament hosted by Schlumpf666aoe https://twitch.tv/schlumpf666aoe
Also there must be a command !prizepool → All donations on Matcherino go to the prizepool of Rising Teams: https://matcherino.com/tournaments/99844/overview
The commands must be mentioned in the title of the stream.
During the broadcast of the tournament games, the logo of the tournament must be visible.
The official logo is available on the tournament Discord in the channel #important-infos.
Players are allowed to stream their POV. A stream delay is suggested but not required.

If there is no stream delay, there should not be a spectator delay.

§27 BROADCASTING

If content from this tournament is uploaded, the title of the tournament and the name of the host must be mentioned in the title of the content.
A link to the stream of the tournament host must also be included.

§28 RECORDED CONTENT

Streaming of the games is allowed under the following conditions:

22 of 23

CHANGELOG

All changes made to the handbook after the release will be listed below.

Version 1.0

20th of August, 2023

Initial release

Version 1.1� 26th of August, 2023

§3 Brackets�Changed: if the requirements only apply to certain team constellations, the team can still register, but only play together in this constellation.
§13 Seeding �Changed: which players are taken to calculate the seeding.
§20 Slinging�Added: consequences for breaking the rule are added

Version 1.2� 2nd of September, 2023

§26 Prizepool�The split of the prizepool has been updated.

Version 1.3� 5th of September, 2023

§17 Pre-Lobby�Changed: a spectator delay is no longer required
§27 Broadcasting �Changed: a stream delay is no longer required

Version 1.4� 9th of September, 2023

§22 Laming�Changed: Laming is - in case of a nomad start - killing wild animals without gathering from them
§17 Pre-Lobby�Added: In case of a problem with deciding on a server, an admin should be contacted immediately to decide in case of doubt. �

23 of 23

CHANGELOG

Version 1.5

10th of September, 2023

§22: Laming�Added: maps that are an exception to the laming rule: black forest
Mappool�Added: the last six maps from the voting were added

Version 1.6

12th of September, 2023

§22: Laming�Changed: the laming rules were specified�

Version 1.7

26th of September, 2023

§22: Laming�Changed: the laming rules were specified�