Pointercrate Rules and Guidelines

This section of Pointercrate documents the guidelines that the Demon List team uses when handling level placements and record submissions. Please note that these guidelines are not necessarily exhaustive and may receive updates. These updates are enforced immediately after their release, so players should take care to read the changelog to familiarize themselves with any recent changes or additions.

If you have any questions or concerns regarding these guidelines, don’t hesitate to contact any team member for clarification! The raw files used to generate this page are also located on GitHub, so if you notice a typo or any other error, feel free to submit a pull request!

Player Checklist

This checklist summarizes the most essential steps players should take to minimize delays in getting their record approved! More information can be found in the linked sections of the guidelines.

  • Complete the level on the rated version on the servers or on an “official” copy uploaded to the Pointercrate account.

  • If you complete a level on a copy, clear it with the list team first! This includes but is not limited to LDMs and bug fixes.

  • Raw footage is required for every submission! Be sure to provide a shared Google Drive link to avoid any delays in accepting your record.

  • Always include click sounds that are clearly audible and isolated in your raw footage. Barely audible clicks are considered equivalent to no clicks and will result in a rejected record.

  • Do not skip the dropdown endscreen after a completion! This will warrant an immediate rejection of your record.

  • Be sure to enable a readable FPS counter for all records!

  • Users of Mega Hack and other mods are subject to additional requirements.

  • If you record a liveplay (e.g. with your phone camera), make sure that your screen is clearly visible!


This archives the various changes the list team has made to the rules and guidelines of the Demon List. Our main notification system for new changes is in our Discord server, so if you are not a member there, it’s a good idea to check this section occasionally for new updates.

Changes listed here are ordered from most recent to least recent. Current version: v2.3

Changes from v2.2 to v2.3 (4/18/2024)

  • Reorganized and removed lots of redundant text from all sections, guidelines should be more readable now!

  • Removed the FPS limit for Geometry Dash version 2.2 and above.

  • Added rules for exploits/pause buffering.

Changes from v2.1 to v2.2 (8/14/2023)

Changes from v2.0 to v2.1 (1/08/2023)

  • Added in-mod fps counter requirement for Mega Hack v7+ users

  • Replaced old allowed hacks list with a comprehensive spreadsheet

Changes from v1.8 to v2.0 (7/17/2022)

  • Changed the wording of nearly every guideline on this site - it’s been a while!

  • Added an absolute requirement for audible clicks, raw footage, and an FPS counter.

  • Changed raw footage guidelines to require a Google Drive link instead of a YouTube video.

  • Added new guidelines related to the User Area and ongoing LDM Project.

  • Updated examples for bugs and skips on levels that are no longer on the list.

  • Updated the list of allowed hacks to reflect the latest Mega Hack version.

  • Updated the Key Takeaways and Player Checklist to reflect these changes.

Changes from v1.7 to v1.8 (4/26/2021)

  • Changed the wording of our skip guidelines.

  • Added a guideline that prohibits the use of alternate accounts on the Demon List.

  • Added a guideline raising the maximum framerate to 360FPS. Players must also use an FPS counter if their framerate exceeds 300FPS.

  • Added a special rule in the list of allowed hacks that prohibits the Trail Always On hack if the level uses a Hide Player trigger for difficulty

  • Added a guideline prohibiting players from enabling or disabling hacks after the start of an attempt to abuse or otherwise change the difficulty of the level.

Changes from v1.6 to v1.7 (3/17/2021)

  • Changed the wording of our framerate guidelines.

  • Added a guideline that allows players to directly submit legacy records to the list team only if they were achieved before the level fell off the list and if they conform to today’s eligibility guidelines.

  • Added a guideline that allows players to submit records that use a Type III or patched Type II skip as if they had achieved progress right before taking the skip.

  • Added a guideline that prohibits the use of shaders for record on the list.

Changes from v1.5 to v1.6 (1/31/2021)

  • Added statements that more clearly states the importance of clicks to the key takeaways and player checklist pages.

  • Removed the guideline about auto sections from Key Takeaways, as it was removed from the full guidelines in v1.5.

  • Added RGB icons and Fast Reset to the list of allowed hacks.

  • Added a guideline allowing players to adjust their framerate midway through an attempt, as long as it does not exceed their set maximum framerate.

  • Added a statement to Key Takeaways clarifying that we only accept Twitch highlights, not stream archives.

  • Added a guideline requiring records to be on the current version of the game.

  • Specified that any record without orb pulses requires an FPS counter. Records that have wave pulses but no orb pulses are not exempt from this guideline!

  • Added a guideline stating that the list team almost never retroactively rejects records after a guidelines update.

  • Clarified that players should send a NoClip run of a custom LDM to the list team so we can respond to their request quickly.

  • Expanded the texture pack guidelines to prohibit anything that makes the text of the endscreen unreadable.,

Changes from v1.4 to v1.5 (12/05/2020)

  • Transferred the original PDF document to the Pointercrate website, with similar organization to the documentation. The original PDF is now deprecated and will no longer be updated.

  • Removed the requirement for full raw footage with the Hide Attempt hack and changed it to a requirement for raw footage in general.

  • Given that these rules are now available for everyone on this website, adjusted the raw footage guidelines so that players need to provide raw footage along with their submission if they have it. The list team will not be reaching out as frequently for raw footage as we did previously, because it would often result in records staying as “Under Consideration” for far too long.

  • Added a requirement for an FPS counter for every record on a level with an “official” in-game song.

  • Clarified that if a list demon has a strong LDM built into the level, the list team will primarily consider opinions from those that use it, because it would represent the easiest “official” version of the level.

  • Added a guideline that includes a public confession as part of the procedure to turn an indefinite ban into a temporary ban.

  • Removed the guideline regarding removing auto sections, as it did not really serve much purpose. To keep the level length the same, players would have to replace an auto section with…another auto section. The level length guideline is now in the Custom LDMs section.

Changes from v1.3 to v1.4 (10/29/2020):

  • Added guidelines for creator lists and verifiers for list demons, including the various definitions of a “creator” and special privileges for megacollab hosts.

  • Added a guideline requiring players to respond to a team member’s request within three days before their record is automatically rejected. Responding later will not penalize players or impact the eligibility of their records in any way

  • Added a guideline allowing use of 360Hz only with proven possession of the monitor. This guideline transcends the traditional “hardware vs. software” argument because the lag and subsequent heavy LDMs required for 360fps bypass was determined to be too detrimental for the list to be acceptable.

  • Removed the hard requirement of raw footage for first submissions, replacing it with “strong encouragement.” Players that are obviously legit with proof such as streams, a handcam, etc. will likely be an exception. Players should still be sure to provide raw footage with their submissions, just in case!

  • Emphasized that records without clicks, a handcam, or a live stream are almost guaranteed to get rejected.

  • Added a guideline with understanding that changes to submission requirements may catch players off-guard. The list team may grant a one-time exception to these guidelines in these situations.

Changes from v1.2 to v1.3 (8/24/2020):

  • Added new guidelines for players submitting raw footage with their records. They fully describe the process players will need to follow to minimize the risk of a rejected record.

  • Clarified the texture pack guidelines to allow all packs that only change the appearance of the player icons (e.g. ship, ball, wave, etc.).

Changes from v1.1 to v1.2 (8/14/2020):

  • Added a guideline that allows Practice Mode records from 0% only with a visible FPS counter.

  • Changed the LDM guidelines to allow minor color changes whenever the original level causes problems to eyesight.

  • Added No Glow to the list of allowed hacks, since the same effect occurs with the in-game Low Detail Mode.

Changes from v1.0 to v1.1 (7/19/2020):

  • Changed the placement time limit from two months to one month.

  • Changed the Type I skip example to 3% on Sakupen Hell (since not many people are familiar with Freedom08).

  • Added the Hide Attempt hack as an allowed hack ONLY with full raw footage or a stream (changed to a general raw footage requirement in v1.5).