If a colonist is on fire-duty, and a tree right next to them is on fire, and it's a tree in the home area and its on fire, but another pawn on the other side of the map says they'll take care of it, the pawn right next to the burning tree will decide their duty is done and will stop to eat while sparks fall around them, or maybe will walk back to bed while the fire they were right next to spreads behind them, destined to destroy half the orchard.
You can't even micro-manage them by right clicking on the fire. (and you shouldn't have to - they're right next to a tree that's an inferno!)
Putting out fire should definitely NOT be reserved like this. (Although it was kind of funny, in a "poor life choices" kind of way)
While in this case it would be better when fire wouldn't be reserved.
But at the regular case, the pawn's spread out and beat 1 fire each pawn, which normaly works very well and bring down bigger fires.
When the fire isn't reserved anymore, all the pawn's prolly beat out the same fire, then run to the next one. Which isn't that bad on smaller and medium fires, but on larger ones it is definitiv better to spread out the pawn's so they keep a bigger area fire free.
Maybe firefight need am improved jobdriver, so when a pawn looks for the next job and got a fire close by reserved by someone there should be a range check and then he will takeover the job ?
Better might be: pick an unreserved fire if one exists, otherwise just pick a fire?
Could you upload a savefile where this happens? Fire reservations should be ignored if the pawn is more than 5 cells away.
I haven't seen this again?
I have not been able to reproduce this. Please upload a save if the issue occurs again.