Track testing is the system that is used to verify tracks. It is mostly run through Google Sheets and the game's Discord server. Most of the information here is available on the sheets as well.
Rubric[]
A track needs to have an average score above 18 and the majority of the 5 testers need to give above 18 in order for a track to be verified.
Aesthetics[]
- 1 = no/minimal props
- 2 = some basic decor, nothing fancy
- 3 = average, use of props is logical and makes sense
- 4 = heavy use of props to create a cohesive picture
- 5 = "world building" vivid background upon which the track is played.
Flow[]
- 1 = lots of poor/incorrect connections between pieces (track is mostly pieces almost randomly combined)
- 2 = one or more incorrect connections, but the track is mostly correct
- 3 = track pieces are connected correctly, however there are some flow issues (i.e. blind jumps, sharp turns after boosters, etc.)
- 4 = only minor flow issues
- 5 = smooth/seamless gameplay.
Innovation[]
- 1 = track is jart (Just Another Race Track) with nothing memorable about it, or track is a near-copy of an existing verified track
- 2 = track features commonly used elements/layouts
- 3 = track is memorable thanks to some unique element
- 4 = track has a complete unique feel to it
- 5 = track is not only unique, but innovative in the way the players complete the race.
Enjoyability[]
- 1 = hated it
- 2-4
- 5 = completely neutral
- 6-9
- 10 = loved it
Penalties[]
- -2 = mind-numbingly easy
- -1 = easy, no resets needed
- 0 = average difficulty, maybe a reset or two needed
- -2 = hard and/or multiple resets needed to clear one or more checkpoints
- -4 = frustratingly hard, more than 10 resets needed per checkpoint.
- -1 = fps drops below 40fps at one or more locations
- -2 = fps drops below 30fps at one or more locations
- -3 = fps drops below 20fps at any point
- -4 = fps drops below 10fps at any point.
- Track is shorter than 30 seconds = -2 for every 5 seconds shorter than 30 seconds
- Track is longer than 2 minutes = -2 for every 20 seconds longer than 2 minutes
- Flickering track pieces = -1 to -5 depending upon the severity of flickering
- Track has fewer than three checkpoints (for lap races multiply the number checkpoints plus the start by the number of laps and subtract 1) = -2
More Info[]
Cycles[]
Track testing runs on cycles. There is one cycle per week and 20 total tracks per cycle. Each of the 5 testers has to choose 2 tracks from the Discord and 2 tracks they find from people who aren't in the discord.
Rotation[]
To become a track tester, join the discord server and DM @orang0474 on Discord. Every cycle, everybody is moved up in the rotation by 4. When you get to the top, you move back to the bottom. The top 4 people in the rotation and the head track tester are the active testers for that cycle.
Other[]
- After getting a track verified, you cannot have another track verified in the next week
- Active testers always go on cooldown after getting a track tested, even if it's not verified
- Tracks are not tested twice unless there are major changes made or the head track tester marks it for retesting
- If more than 4 tracks score above 18 in one week, some of them will be reserved. Reserved tracks are saved and verified during a week where we get less than 4.
- You can't have 2 tracks by the same person tested in the same week