1 Stack toward one idea
The stated goal is peak powerup perfection and becoming absurdly overpowered. With over a hundred options and a limited run length, that only happens if the pieces reinforce each other.
This is also why a second copy of something you already have is often a better pick than a new effect. Stacking is explicitly named as the intended behaviour.
2 Divide the powerups across the group
In a co-op roguelite the group is the build, not the individual. Eight players who all took the same offensive route have no answer when something goes wrong.
| Role | What that player should prioritise |
|---|---|
| The wall | Defensive picks such as a barrier. Someone has to survive long enough to revive the others |
| The engine | Pure stacking damage. This is the player the group protects |
| The clearer | Area effects, so trash waves do not reach the engine |
| Everyone else | Whatever they enjoy. Beyond four players, specialisation matters less than communication |
3 Weapon swapping as a group tactic
Free weapon swapping is usually treated as a personal preference. In a group it is better used as coverage: if everyone is in melee, nothing punishes an enemy that stays at range, and the reverse is equally true.
A simple habit fixes it. When the group commits to a fight, one player checks whether anyone is covering the opposite range and switches if not.
4 Plan the run before you start it
Choices made when picking ingredients and quests determine which bizarre enemies, cursed locations and bosses appear. That is a genuine lever, and using it deliberately is the difference between a roguelite you play and one that happens to you.
5 Large lobbies need rules
Eight players is enough that the group becomes the hardest thing to manage. Three small conventions solve most of it.
| Convention | Problem it prevents |
|---|---|
| Call revives before moving | Four people abandoning damage for the same downed player |
| One person calls the advance | The group splitting across two rooms with half the powerups in each |
| Use the horn as a signal, not a toy | The rally tool becoming background noise that nobody responds to |
Custom volume controls exist in the options, and they matter here. If effects drown out voices, none of the above conventions can work.
6 Chasing 69 achievements
Sixty nine is a moderate list, large enough to guide you toward content you have not tried but small enough to be plausible to finish. In an Early Access game it may also grow.
Use it the way you would use a checklist of systems. An achievement referring to a weapon or powerup you have never used is a prompt to build a run around it, which is more interesting than grinding the one build you already trust.
7 Mistakes that cost runs
| Mistake | Fix |
|---|---|
| Taking the most impressive powerup every time | Take what compounds with the two you already have |
| Everyone building damage | Someone takes defence so revives are possible at all |
| Locking into one weapon | Swapping is free. Use it to cover the range nobody else is covering |
| Skipping the pre run choices | They decide the enemies and bosses. Read them |
| Brute forcing a boss with a bigger build | The store says learn the dance. Patterns beat numbers here |
Commit to one powerup direction by your second or third pick and refuse everything that does not feed it, taking duplicates freely since stacking is the intended play. Split roles across the group so somebody survives to revive, and use free weapon swapping to cover whatever range nobody else is covering. Treat the pre run ingredient and quest choices as a real lever, repeating them while learning and varying them for fun. In a large lobby, call revives, let one person call the advance, and keep the horn meaningful.
Comment
No comments yet. Be the first to post one.