Hidden Twirls and On-beat rotation
From Good Practices
Last updated
From Good Practices
Last updated
This practice is related to Twirl Events
Twirls, when placed on bad spots in a level, can cause the gameplay to be impossible to read, as it may be covered by the track itself, making it hard/impossible for the player to know what to do next.
In cases like these, it's better to move the twirl somewhere it's visible, while not affecting the gameplay itself in any way. But if that's not possible (In this case, for demonstration purposes), Position Track events can always be used in order to fix this issue.
On-Beat Rotation is when the angle turns don't add up to 180° or 360°, which represents the On-Beat of the song, and because of that, the sum of the angles, becomes the On-Beat of the song, despite not being 180° or 360°.
In the first pattern, the angles add up to 360°, avoiding On-Beat Rotation. 90+45+45+90+90=360°
In the second pattern, the angles add up to -90°, causing On-Beat Rotation. Each time a twirl is used, the current operation is reversed. For example, in the image below, a twirl is used at the 45° turn, thus -45
, and is used again for the next 45° turn, thus +45
. 90-45+45-90-90=-90°
This can be used well if you know what you can with it, but to avoid it, the easiest way would be to only use twirls when there's an angle distance of 90°, 180°, 270° and 360° from the starting angle. Of course, On-Beat Rotation is not always guaranteed to happen when twirls are used on non-cardinal angles, but beware of where you place them, so it doesn't happen unintentionally.