Water Primary
The source-block rule: flowing water between two sources becomes a source. This is the mechanic the entire video rests on, and it is vanilla behaviour, not a DonutSMP plugin.
Video source notes
The drainers are not losing to griefers. They are losing to the way water works, and that part is documented in the game itself.
The asymmetry, in game terms
The core idea
Minecraft’s water is not a fluid being simulated; it is a rule being applied. Flowing water between two source blocks becomes a source block itself, and then that new source can do the same thing again. Placement is a one-time cost paid by a player; spreading is an ongoing cost paid by the server.
There is no inverse rule. To remove a water block, something solid has to occupy that exact coordinate, or a sponge has to absorb it — and a sponge takes 65 blocks before it is spent and has to be dried. A flood machine is one block tall and drops water from build height where there is nothing to collide with. A drain wall has to be as tall as the flood is deep, has to survive contact with terrain and bases, and has to miss nothing, because any gap it leaves starts refilling behind it.
“They’re fighting the source code, and the source code doesn’t get tired, doesn’t log off, and never runs out of slime blocks.”
The one thing both sides share is chunk-loading: a flying machine stops the moment its chunks unload, so a flooder has to fly behind their own machine and a drainer has to walk behind theirs. Placed water needs neither. That is the whole argument, and it does not require anyone’s testimony.
The population figures quoted in the video are community shorthand. The tracked weekly averages are tighter and are the ones to cite: 28,020 in the week of 28 May 2026, 13,076 in the week of 4 June.
Primary sources
The source-block rule: flowing water between two sources becomes a source. This is the mechanic the entire video rests on, and it is vanilla behaviour, not a DonutSMP plugin.
Absorption limit and the drying requirement — the reason draining scales with human attention and flooding does not.
The weekly averages either side of the June 2026 update, used in preference to the rounder figures quoted on screen.
The 30M-block plan referenced at the end — the map the drainers would have to defend. Fan-edited wiki.
Both sides’ own material
Cited as evidence of technique and of the two camps existing. Not as evidence of who is winning.
The drainers’ site: working drain machines rebuilt from .litematic files, plus the observation that almost nobody files these builds under “drain”.
Community comparison of the machines each camp uses.
A published, downloadable flooding machine — proof the build is standardised and distributed.
Promotional site for the flooding side. Useful as evidence of organisation and framing; not a neutral record.
Conflict log · what the sources dispute
The mechanics are settled. The population numbers and the outcome are not.
| Claim | What the video says | What the sources say | Position |
|---|---|---|---|
| Player collapse | ~35,000 → ~10,000 | trackers recorded 28,020 → 13,076 across the update week | Trackers preferred. The round numbers are community shorthand. |
| Who is winning | the drainers cannot win | no one has published how much map is flooded or drained | Argument is about the mechanic, not a scoreboard. No outcome claimed. |
| Terminology | “drain machine” | the same builds are filed as ocean clearing / ocean remover | Named in the video because the naming gap is part of the story. |
| Border’s effect | drainers must defend a far bigger map | expansion is announced with no confirmed date | Stated conditionally. |
Nothing here claims the server is beyond repair as a matter of fact. The claim is that manual draining loses to an automatic spreading rule, and that is a statement about Minecraft, not about DonutSMP’s staff.