[Potrock]

Requested by Patrick · project thread

What this is

A fix. When barbarians caught a worker, it became theirs, and then barbarianTurn ran it as a raider. It went for the nearest of its old owner's units and "attacked" them with 0 strength, so it died at once. It looked like it had simply vanished.

Now, Civ V style:

• A captive walks back to its captors' camp (to the nearest camp if theirs is gone) and waits there. If another captive is already in the camp, it waits beside it. If no camp is left, it stays where it is.
• It can be taken back. Step a soldier onto it on the way, or clear the camp. This uses the existing capture path, so bots recapture too.
• Captives don't count toward the raiders a camp keeps out, so a camp holding one still sends raiders.
• A capture clears the worker's automation, stance and settler site. The victim's note now says the worker is being taken to the camp. A civ that frees one is told so.
• On the map, a unit's owner is now kept current. Before, a captured worker walking out of sight played the "sinks away" animation as if it had died.
• The Barbarians page in the in-game encyclopedia explains captured workers.

Before and after, from 6 bot games on small maps (160 turns each, barbarians on):

	captured by barbarians	gone (killed)	reached a camp	taken back
before	6	6	0	0
after	6	0	6	6

Screenshot or clip

None. I didn't check this in the browser because the wasm toolchain isn't in my environment. The rules tests and bot games above cover the behaviour.

Checklist

• npm run build passes (CI). Locally, type-check is clean for Blockilization and the boundary check passes.
• npm run test:headless passes (CI). The rules suite (tests/effects.ts) passes 258/258, including a new test for this. The new test fails on main.
• No new names or assets

🤖 Generated with Claude Code

https://claude.ai/code/session_01NTPcknrRzzKZVG96rQjwXG