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 did not happen in my current 1.0 start.
-----------
I would say build a 1 tile stockpile right beside that dead mech and test it that way. If it works then its a pathing issue with your storage in your base. If it doesn't its proibably a mod conflict.
Good luck.
Sometimes stock & dumping zones become "sealed-off" when a pawn
is already taking something there.
Try forbidding the lancer in pause, unpause, then unforbid it.
Set everyone to military duty for a second to clear a barring task.
Try to create a completely new zone or use an empty closet for that lancer.
Make sure that it meets 'hitpoint', 'rotting' and any other parameters of said corpse.
You're in RimWorld 1.0?
while forbidding the ones you have already collected.
If you do, it's possible that either:
- mod isn't listed correctly (possibly even in conflict with another)
- mod isn't coded properly (including the above)
Either way, unsubscribing.
I've just encountered the exact same problem you have, exactly with all the details that you have mentioned above
It turned out that the solution to my problem was that the corpse of the monster died right above the "hauling zone" that I had. For anyone who might encounter this problem and find this thread via google, the advice I can give is to make sure the corpse isn't lying on top of your "hauling zone". Double click the spot to make sure!