You start Fortune Mill with a single battler standing against a screen that’s already filling with mobs, and within a few waves you realize the real game isn’t fighting them directly — it’s deciding how many more units you can afford to add to your line before the formation falls apart.
| Genre |
Auto-battler survival roguelite |
| Platform |
Browser |
| Team size |
Up to six units |
| Passive tree |
Over 1,000 nodes |
Building a Team of Six in Fortune Mill
The core loop scales a single battler up into a full team of six, each pulling from one of six available classes, fighting hundreds of mobs at once as waves escalate. Beginners almost always make the same mistake early: filling out all six slots as fast as possible without checking whether the classes actually complement each other, which leaves a team that looks full but folds the moment enemy density spikes.
What separates a team that survives late waves from one that doesn’t isn’t unit count alone — it’s whether abilities across the six slots actually chain into each other. With 36-plus abilities available across the roster, overlapping cooldowns and shared trigger conditions between two or three units routinely outperform six units picked without any synergy in mind.
The Passive Tree Fortune Mill Builds Every Run Around
Beyond the active team, a passive tree of more than a thousand nodes sits underneath every run, and planning a path through it before committing resources is one of the advanced techniques most new players miss entirely. Early runs tend to spend passive points reactively, node by node, rather than plotting toward a specific late-game payoff several branches away.
- Check class synergy before filling every one of the six unit slots.
- Plan a passive-tree path toward a specific payoff rather than spending reactively.
- Craft gear to patch a team’s weakest stat rather than its strongest.
Gear crafting layers on top of both systems, and with 50-plus items in circulation, the temptation is to chase whichever item looks strongest in isolation. Players who instead craft toward covering a team’s weakest stat, rather than stacking its strongest, tend to push noticeably further into late-wave density than players optimizing for raw numbers alone.
Choosing How Hands-On Fortune Mill Actually Is
One detail that sets the game apart from most entries in the genre is choice over control itself: play fully automatic and let the six-unit formation fight on its own, take full manual control instead, or mix the two depending on the wave. Community discussion around Fortune Mill circles back to this constantly — some players consider full automation the entire appeal of an auto-battler, while others feel manual control is where the actual skill expression lives, and neither side is entirely wrong.
By the time a run reaches its later waves, mob density stops being a minor annoyance and becomes the actual test of whether a team’s synergies were planned or improvised. That’s the moment where players who leaned on passive-tree planning and deliberate class pairing pull noticeably ahead of players who filled slots and hoped for the best.
How many classes and abilities does Fortune Mill actually have?
Six active classes with more than 36 abilities between them, alongside over 50 craftable items — enough that class-and-ability pairing matters far more than any single powerful pick.
Is full manual control necessary to do well in Fortune Mill?
No — the game supports fully automatic play, full manual control, or a mix of both, and none of the three is required to progress through the passive tree or survive later waves.
What’s the biggest difference between an early team and a late-run team?
Early teams tend to be six units chosen for raw stats; late-run teams that actually hold up are built around ability synergy and a passive-tree path planned several nodes in advance.
None of Fortune Mill’s depth is obvious from the first few waves — it reads as a simple six-unit auto-battler until the passive tree, the item pool, and class synergy all start compounding on each other, and that compounding is the entire reason runs that looked identical at wave one end up nothing alike by the end.
