> For the complete documentation index, see [llms.txt](https://adofaieditor.gitbook.io/english/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adofaieditor.gitbook.io/english/level-preparation-and-assisting-techniques/good-practices/bpm-speeds.md). # BPM Speeds From Good Practices {% hint style="info" %} This practice is related to [Set Speed](/english/events/gameplay-events/set-speed.md) Events {% endhint %} ## • Hidden Speeds

These should never be on the same tile together

### Ways around this rule ### -> **BPM building** These builds, as long as previously informed, allow the player to take a guess on what the following tiles should be played

Example - BPM Build up scenario for hidden speeds

## • False speed changes

Example - Speed random value

Example - Speed Double Value

Typical game plays have an **unwritten rule** that helps keep consistency at all levels. That rule is simple: Speeds should always be **Double** or **Half** the tempo of the current BPM. You may also **Quadruple** or **One-fourt**h the speed as the game presents it with a double rabbit/snail

Example - Double Tempo

Example - Half Tempo

### Ways around this rule ### -> Text Indication Indicating in text format the speed is going to change in an inconsistent way, usually helps players get prepared ahead for an irregular gameplay style, making it a great way to stop surprises

Example - Speeds with a bpm text, indicating the next speed

Example - Speeds with a multiplier text, indicating the next speed