1 Before you start
Two settings decisions are worth making before the first run, because both are awkward to change once you have muscle memory.
| Decision | Why it matters here |
|---|---|
| Pad or keyboard | Controller support is listed as partial. Test yours in a throwaway run rather than a serious one |
| Frame rate over fidelity | The game sells itself on instant response. A stable frame rate is worth more than any visual setting |
| Screen shake and effects | Heavy effect layering is normal in this genre. If a slider exists, turning it down makes enemy telegraphs readable |
2 Picking your first hero
Four heroes are available, each described by their weapon: razor sharp blades, heavy cannons, frost forged power and one more in the same spirit. Each carries more than 180 skills.
That number is the reason not to sample all four immediately. A hero with 180 skills reveals itself over dozens of runs, not two, and switching early means you learn four movesets shallowly instead of one properly.
3 What a run is made of
The store describes dynamic runs where every attempt reshapes itself with new events, routes and encounters. Three collectible layers feed into your character during that run.
| Layer | Role | Scale |
|---|---|---|
| Skills | Your hero moveset | 180 or more per hero |
| Relics and gear | Passive modifiers to combine | 130 or more |
| Embers, Spellcards, Legendary Gear | Fused together for chain reactions | The stated route to overpowered builds |
The fusion is where the game happens. Collecting good individual pieces is the beginner behaviour. Combining pieces that multiply each other is what the design is asking for.
4 Learning the movement first
In a game built around speed, the first skill to acquire is not a damage skill. It is knowing exactly how far your evade travels and how long you are vulnerable after it.
Once you can identify which of your attacks commits you and which can be cancelled, the difficulty of the early areas drops noticeably without any build improvement at all.
5 Your first ten runs
| Runs | Goal |
|---|---|
| 1 to 2 | Learn the controls and where the menus are. Expect to die early and do not mind |
| 3 to 5 | Read every skill and relic you are offered, even the ones you reject |
| 6 to 8 | Try to build around one theme per run instead of taking the strongest looking option |
| 9 to 10 | Deliberately repeat a theme that worked, to see whether it works twice or you were lucky |
The point of runs 9 and 10 is separating a genuinely strong combination from a run where the offers happened to fall well. In a roguelite with 130 relics, that difference is easy to misread.
6 Reading skills and relics
With this many options, the text on each one matters more than the numbers. Three categories are worth separating in your head as you read.
A run that collects five additive bonuses is weaker than a run that collects two triggering effects that feed each other, even though the first one looks better on a stat screen.
7 When to stop for the night
Fast action roguelites punish tiredness harder than most genres, because the failure mode is reaction time rather than decision quality. If your deaths start coming from inputs you know are wrong rather than situations you did not understand, the session is over.
There is no penalty for stopping. Progress in a roguelite is stored in what you have learned about the systems, and that survives a break better than a tired session does.
Set frame rate above fidelity and test your controller early, since support is only partial. Commit to one hero rather than sampling all four, because each carries over 180 skills. Learn your evade distance and attack recovery before worrying about builds. Read offers as additive, conditional or triggering, and favour the triggering ones, since the fusion of Embers, Spellcards and Legendary Gear is where the intended power lives. Repeat a successful theme once to check it was the build rather than the luck.
Comment
No comments yet. Be the first to post one.