Odd Realm Dev Tracker

I mean, that's expected, though. The point of the notification is to tell you they can't reach something, so in this case, that's good to know as the player.

You are correct! That's currently the only way.

You can build cages to capture the wild animals. They can get caught by them when walking over them. You can also bait the cage with their dietary items to lure them. You just need to put a stockpile room on the cage and assign the required items.

Once an animal is in the cage, you can assign the capture job to it. There's a chance they will become hostile when doing this, so fair warning.

I'm going to add a hunting/trapping room soon to automate a lot of this stuff.

I've noticed this for a couple players that had accidentally blocked off items in inaccessible containers. Because props are pathing obstructions now, it's easy to build containers and block off items. Sounds like this isn't the case for you, but worth a check. When you click the notification, where does it take you? Does it take you to an item that's in the same room/pathing area as the entity trying to do the job?

I'd love to take a look at the save to help put out a fix for the issue. You can follow these steps to send me your save:

...

That’s right. However, the summons should automatically join stockpile rooms unless you manually prohibit captured entities from joining the room.

Thank you!

Heyo,

I've uploaded a patch to the beta branch with tons of fixes, especially for eat/drink bugs, and a nasty load issue which kept items from loading properly.

Here are the notes:

-Bug Fix: Entities would get stuck in single open block point. Now, they will snap to the closest entity to get unstuck.
-Bug Fix/Performance Improvement: Where entities were searching additional blocks for a job candidate when they already had one.
-Bug Fix: Certain scenarios weren't activating because they couldn't find the right tag for a previously created entity.
-Bug Fix: Stale room jobs (ones that have been sitting around for a long period of time without starting) were not properly being removed from a room. This would cause multiple jobs to stack forever.
-Bug Fix: A null reference would occur (in the entity WorkState) when an item search processed in the background, then the active job was cleared, then the job finished to reference the cleared ...

I was not aware of this. It sounds like a bug to me. I'm going to investigate to see what might be causing the issue. Thanks for letting me know.

You playing the beta? Should be fixed in beta and will be coming to mainline soon