Slotbound’s v1.0.0 (8) update adds Turkish localization, an in-run Collection screen and faster auto-resolve after your army falls. The patch continued the solo developer’s rapid post-launch cadence โ this was one of nine updates shipped within days of the November 12 release.
Key Facts at a Glance
- Turkish language added to the localization set
- The Collection opens mid-run: battlefield tab, C key, or gamepad View button โ even during Class Promotion
- Once all units fall in regular waves, the rest of the battle auto-resolves faster
- The Fate Stone quest “Gauntlet” was replaced by “Four Lines at Once” (4 winning lines in one wave)
- Golden Lever fix: all units from X2 summons now receive the rarity upgrade
What the Changes Improve
The in-run Collection is the quality-of-life headline: checking unlocks and unit info no longer costs a run interruption. Faster auto-resolve respects the player’s time in lost waves instead of forcing a spectator session. The replaced Fate Stone quest targets the same goal โ “Gauntlet” produced forced playstyles, while “Four Lines at Once” rewards the core slot-machine line-building fantasy.
Why Localization Expands Reach
Turkish is a high-engagement Steam locale that many indie launches skip; adding it signals the solo developer is watching region-specific demand. Combined with the tutorial improvement (stat icons now show names), the patch lowers the onboarding barrier that slot-mechanic games need to survive review scores.
The Patch Cadence
This update is part of a run of nine post-launch patches the developer credits to player reports โ the 100,000-copies milestone announcement landed alongside them three days after launch, and the Fate Stone quest rework followed in v1.0.0 (9).
Keep Reading
- Slotbound game hub โ trailer, screenshots and wiki
- 100,000 copies sold in three days
- v1.0.0 (9): Fate Stone quests reworked
Source: v1.0.0 (8) Update on Steam News
100k copies in three days for a solo dev. The nine updates in that window are the real flex.
Reported two bugs on launch night and both were fixed by morning. Best dev communication I've seen.