Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This happens with other Zones, too, when there's a zone-specific job in progress and the Zone is deleted.
For example, I assigned an Office to a dorf. They were on their way to do something in it, maybe to have a "Meeting" or some other thing that is Zone specific. I deleted it and... <crash>
The best I can figure is that when there's a zone-specific function or task/job involved and the zone is deleted, some of those things fling errors that don't get caught. It's got to be very Zone specific, though, and a hole in the code that doesn't catch it, where it can crash through. Placing something in a chest may or may not cause it, but drill down to something extremely zone-specific, like Burying, and that seems likely to fling it if the zone is deleted.
You used to be able to just throw a bunch of graves in a room and call it a graveyard.
I've noticed a few streamers who were obviously used to Classic mechanics being puzzled over this, too.