Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[itg]

Beekeeping bug are nothing new, but at the moment I've got a project for which beekeeping is actually kind of important, and the workarounds I'm aware of aren't helping.

The problem at the moment is that my beekeeper keeps trying to install a non-existent colony in a hive. I only have beekeeping enable on one dwarf. The "colony" is not in his burrow, but the beekeeper doesn't care--he just ignores the burrow. I've tried making the "colony" inaccessible by spawning magma on and around the spot, but it just causes job cancellation spam as the moron keeps trying to harvest invisible bees but can't find a path to them.

Is there any workaround for this circumstance? I'm fine with using dfhack.

[4maskwolf]

One thing that works is an interesting thing that helped with statue trapping back in 2-d. I had something similar happen pen to a dwarf, and I conscripted him and activated his squad, if I remember correctly. Also deactivated beekeeping, but that had nothing to do with it.

[Larix]

All you need to do is disable the "install colony" setting on the offending beehive, then switch it back on after the game has processed it. To find the correct hive, the easiest way is to go through the 'j'ob screen - look for the "install colony in hive" job assigned to the stuck dwarf, zoom to the building. That's the culprit. Messing around with the beekeeper or the spot won't properly stop the job - it is generated by the hive and will never properly cancel unless you "reboot" the hive.

Once the faulty job has been cleared by toggling the install option, the hive (and beekeeping in general) will work properly again. With this simple fix in mind and an open eye for errant beekeepers, you can run a forty-hive-five-beekeeper industry without a hitch.

[itg]

Ah, that actually makes a lot of sense, now that I think about it. I must have destroyed a colony after the hive generated the job to go harvest it, but no one told the hive, so it keeps sending the drunken midgets to the last known location of the bees.

So far, it looks like the "reboot" did the trick. Thanks!

[wierd]

As far as I have been able to determine, the bug is caused by a combination of 2 things:

1) the hive/bees do not get locked for task, meaning they can be harvested by somebody else.
2) there is no job cancellation check for item misplaced or destroyed on bees/hives.

Forcing the game to recompute available hives for the install colony job makes it put a valid source on the job, allowing it to be completed. "Rebooting" the hive does exactly that.

The lack of a cancellation message makes it difficult to consistently track when urist McBeekeeper decides to watch the grass grow instead of working though. It would be nice if toady put a simple item availability check on the beekeeping jobs that forces the equivalent of this reboot when the selected hive is invalid.

Until then, the hive reboot method is a suitable workaround. It's easier with a single beekeeper though. Less likely for one bearded bastard to cause a race condition for a hive.