The sobosuba score 0 achievement requires finishing a game with a final score of exactly zero. In developer keepeetron's soft-body physics puzzle, newly spawned blobs do not contribute points to your scoreboard until they participate in their first merge. Unlocking this achievement requires forcing an immediate game over before any blobs touch and combine.
How the Score 0 Mechanic Works
In an official Steam Community explanation, developer keepeetron clarified that a run's score represents the total value of eligible blobs on the screen. Newly spawned blobs appear with faded number labels and contribute zero points to the scoreboard. They only become counted once they take part in a merge.
Because unmerged pieces carry no numerical score, a fresh run always sits at zero points. A game ends when the playfield becomes overfilled and blobs trigger the upper boundary threshold. If the game-over condition activates while every blob on screen remains unmerged, the game concludes with a verified score of 0, immediately unlocking the achievement.
Player Methods for Ending a Run at Zero Points
Because sobosuba has no manual forfeit button or time limit, players must deliberately overfill the top boundary on the opening move. Community guides and Steam discussion threads document specific ways to force a game over without triggering an accidental merge:
- Launch in opposite directions: The Steam 100% Achievement Guide by Menace123 notes that players can throw one Sobo in one direction and quickly throw the other in the opposite direction so they do not collide with each other.
- Synchronize bumper impacts: In a Steam community thread regarding the achievement, players reported seeing red beams without the game ending if the pieces bounced clear too quickly. A player response advised launching the first blob slightly slower than the second so both hit the upper boundaries simultaneously, clogging the top zone and securing the fail state.
- Prevent contact at all costs: If two identical blobs collide and merge, the resulting piece becomes eligible for scoring, instantly invalidating the attempt. If a merge occurs, restart the session immediately.
Version 1.2 adjusted launching so shots add velocity rather than overwriting existing movement, and added center-cancelling for aiming arrows. Players aiming for quick boundary jams should watch the movement of the float bar before firing.
Exact-Score Achievements in sobosuba
The score 0 achievement belongs to a distinct category of exact-score challenges added by keepeetron. Each of these challenges requires ending a run on an exact number rather than chasing a high score.
| Achievement Name | Official Requirement | Reward |
|---|---|---|
| score 0 | Finish a game with a score of exactly 0. | Unlockable color style |
| score 10 | Finish a game with a score of exactly 10. | Unlockable color style |
| score 100 | Finish a game with a score of exactly 100. | Unlockable color style |
| score 1000 | Finish a game with a score of exactly 1000. | Unlockable color style |
Every unlocked achievement in sobosuba awards a cosmetic color style, allowing players to customize the visual appearance of their blobs across future runs.
Frequently Asked Questions
What reward do you get for unlocking score 0 in sobosuba?
Unlocking the score 0 achievement grants one of the game's unlockable color styles. There are 30 achievements in the Steam release, and each one unlocks a distinct color style.
Why does a game over with starting blobs result in zero score?
Developer keepeetron designed fresh blobs to spawn with faded numbers that do not count toward your total score until they successfully complete a merge. Ending the run before any merge takes place leaves the scoreboard at zero.
What causes a game over in sobosuba?
A run ends when the playfield becomes overfilled past the top area, which activates red indicator beams and ends the session.
Can you get the score 0 achievement if two blobs merge?
No. Once any two blobs merge, they become counted on the scoreboard, raising your total above zero. If any merge happens, the run must be restarted.
