Testing Gameplay

There are multiple options and features within the editor that can help you sufficiently playtest your level. This guide will go over these options/features in depth.

These are playtesting-related features that you will encounter while in the editor interface.

The Editor Playtest button is on the left hand side of the screen, in between the Music Playtest and Zoom In/Out buttons. 

This button lets you quickly play your level from your latest StartPos, and marks your movements with a green line. This is a useful feature that saves time and helps you keep track of the player's movement in order to build your gameplay. Keep in mind that the physics are slightly different in the editor and it is advised to still playtest your level in normal mode.

The Music Playtest button is right above the Editor Playtest button, and below the Undo/Redo buttons, once again on the left of the screen.

These are the playtesting-related features that you’ll find by pausing the editor and/or going into the options menu.

Note that Hide Invisible, Preview Mode, Preview Animations, Preview Particles, Preview Shaders, and Show Ground can also apply to Editor Playtest.

In addition, you can purchase the Practice Music Unlock feature in the Diamond Shop, which allows you to listen to the actual song in practice mode. This opens up practice mode as another viable form of playtesting if you want.

Alongside Show Hitboxes in the previous section, Show Info Label is an option that you can enable when you’re playing the game and you want to view the level’s status. It’s the equivalent of Show Object Info but from the player’s perspective.

• Level ID: Displays the ID of the level that you are playing. If it’s not yet uploaded, it will have an ID of 0.

• Time: Shows how long you've been playing the level. It resets when you die or restart, and keeps on going even when you stay in the “Level Complete” screen.

• Attempts: Displays how many times you’ve died. The attempt count resets if you leave or complete the level.

• Taps: Shows how many inputs you’ve made on the current attempt.

• Timewarp: Displays the timewarp trigger’s setting. Its default number is 1.

• Gravity: Shows the player’s current gravity in a level. By default, it’s set to 1.

• X: Shows the player’s horizontal distance. They are expressed in Small Steps,so 30 small steps is one normal block’s size.

• Y: Shows the player’s vertical distance from ground level. On the default ground with a normal-sized cube, the player is 105 small steps high. In mini however, that shrinks to 99 small steps.

• Active: Displays the amount of elements on screen (e.g., the player and objects). It does not count triggers or any objects that are offscreen or invisible. However, transparent objects and objects that are assigned to a link visible trigger do count.

• Gradients: Shows how many active gradient triggers are present on screen.

• Particles: Displays how many particles are on screen (such as portals, pads, and even custom particles).

There are only two descriptions here that will tell the player how many songs and SFX are active in the level.

In Coaster Mountain by Serponge, despite the song download stating that there are 3 songs and 43 SFX, the info label will display mostly 1 to 4 at any given moment (that’s if you stick to one attempt). If you die and respawn on the next attempt, the SFX increases.

• Move: Measures how many objects are affected by the move trigger (can sometimes apply for offscreen objects, though not guaranteed).

• Rotate: Calculates how many objects are affected by the rotate trigger.

• Scale: Estimates how many objects are affected by the scale trigger.

• Follow: Counts how many objects are affected by the follow trigger.

The last 4 are different in the sense that they are expressed as fractions. The denominator increases first when an area trigger is activated. Then, once an object that was assigned to the area trigger shows up on screen, it will increase the numerator.

• Move: Calculates how many active objects are affected by the area move trigger. Colon’s Dash review provides evidence that there is a correlation between high move areas and lag.

• Rotate: Counts how many active objects are affected by the area rotate trigger.

• Scale: Measures how many active objects are affected by the area scale trigger.

• ColOp: Estimates how many active objects are affected by either the area fade or area tint trigger. If the same objects are affected by both area fade and area tint, the ColOp denominator will double.