THE RULES

Section 1: Completion/Verification rules.

All completions/verifications must have recorded proof of verification (i.e. no

screenshot proof or "just trust me bro" proof).

All records MUST have audible clicks

If you are asked, PLEASE provide your raw footage.

Before you submit a challenge, make sure to check if the level is allowed for the
list (read section 2 for info on what a list challenge is and isn't allowed to
have).

this is optional, but if you have submitted a challenge to the list, please post it
on youtube, it speeds up the placing process since we don't have to post it
ourselves, thanks! :)

the highest fps allowed is 360, and the lowest is 59.

if you use an fps value other than a levels intended fps value (i.e. using 60hz to
make a 360hz frame perfect easier) your completion will not be accepted.

Section 2: Submission rules.

Levels must have some sort of decoration, and before you ask, the challenges on the
list that are layouts were added before this rule was implemented.

Levels must be shorter than 30 seconds long

Your levels decoration also has to be tolerable, as in no...

-item spam
-epilepsy inducing flashes
-laggy deco without an ldm

Submitted challenges cannot be copies of already existing levels that you did not
get permission to reupload (reuploading your own level is fine).

Submitted challenges cannot be a part of a verified demon (i.e. taking a wave from
garbage vortex and turning it into a challenge) unless it is buffed/changed

Submitted challenges cannot be buffed versions of existing levels that are already
on the challenge list unless it is your level/you get permission from the original
level creator.
(Buffed versions of challenges will replace the original if it was already on the
list)

No spam challenges
(Spam is really hard to define, but the actual challenge list says that "if it's
the cps thats required, not the consistency, it cannot be accepted" so lets just go
with that)

If your level requires a low fps value (i.e. 15 fps challenges) it can't be
accepted. (The lowest fps value allowed is 59 fps.)

Submitted challenges cannot have the icon invisible for the entirety of the
challenge (due to it being incredibly easy to noclip) (cool transitions are fine)
 Section 3: Allowed/Dissallowed hacks

Allowed hacks:

Fps bypass (from 59fps to 360fps)

No wave pulse
No pulse
No death effect
RGB Icons
Hide attempts
Hide pause button
No particles
Accurate percentage
Texture packs (as long as it doesn't help you see where the hitboxes are)
Icon hack
Trail on/off

anything that is purely visual is usually fine; ask a list mod if there is any
confusion

Dissallowed hacks:

FPS abuse (using higher than 360fps/lower than 59fps)

Physics bypass
Hitbox multiplier
ANY sort of macro/bot/clickbot
Noclip/nospike
Noclip accuracy
Speedhacks
Semi autoing levels
Secret nerfs
Illegal bug fixes (i.e. changing a 360fps challenge to be possible on 60fps)
Cut completions
Show hitboxes

basically, USE COMMON SENSE.

(I know these are incredibly obvious, but some people take "not on the rules page"
as "feel free to do this" so we kinda had to)

Section 4: Other stuff

You are allowed to make ldms for levels, just DO NOT delete ANY objects that
cover/obscure your vision, as that is nerfing the level.

If you are caught hacking it WILL result in a permanent ban. However, if it is a

first time offence, or you confess to the hack before we catch you, it will result
in a more lenient ban.

If you have any questions/anything you want to tell the mods, don't be afraid to
ping a member of the mod team.