# How do I craft a tutorial with many mechanics and not scare players with too much information? — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/75e377d892adb30d

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-11-06 17:12 ingested 2026-11-07 02:38

[original source ↗](https://www.reddit.com/r/gamedev/comments/1xpi9o4/how_do_i_craft_a_tutorial_with_many_mechanics_and/)

## retained text



```
I started development of my game, RuneEra, 4 years ago, if not more already.

It's a colony simulation with RPG elements. Similar to RimWorld with Valheim-like progression and RPG combat with fluid classes.

For transparency, I used AI in the last year of development to meet the art demand, since I completely overscoped, in my artist's opinion. Around 2,000 sprites: lots of plants, animals, ability icons and effect icons.

I [posted here a year ago](https://www.reddit.com/r/gamedev/comments/1mfoyx7/after_3_years_of_solo_dev_my/) and must say I have come very far, and currently my biggest problem is crafting an engaging tutorial with minimal initial mechanic explanations.

Since testers come from my close circle, for most of them this genre is very niche, and they have never played anything like this before. As such, they are overwhelmed with new information and game systems from the initial tutorial. A few managed to go through it without much problem since they play similar games and are embracing complexity.

Some even wanted better and more in-depth explanations upfront, but I think discovering and mastering mechanics is the game in itself.

What I did so far:

- I added breaks in the tutorial so players can slow down and play the game while exploring the newly learned mechanic.
- All tutorial steps are skippable. If you get stuck somewhere, you can just continue.
- A separate guide section explains mechanics in detail, which players can visit any time.

I know it is impossible to please everyone, and I should only focus on feedback from players interested in this genre.

Should I approach this differently? If so, how? How do you decide which mechanics to explain immediately and which ones players should learn later, especially when testers have different levels of experience with the genre?
Where should I go to find feedback from players interested in this genre?

```



document fetched 2026-11-07 00:25 · canonical https://reddit.com/r/gamedev/comments/1xpi9o4/how_do_i_craft_a_tutorial_with_many_mechanics_and
