You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disabling "Pawn Access" completely disable pawn interaction with a DSU and its IO ports
To Reproduce
Reproducibility: ?
Steps to reproduce the behavior:
Enable only Project Rimfactory
Generate a basic map
Build a DSU, an input IO port, optionally an advanced IO port. Link them to the DSU.
Enable everything in the storage settings on the DSU. Pawns should start hauling things to the DSU or the input IO port.
Disable Pawn Access on the DSU.
Pawns can no longer haul anything. When right clicking a stack, it says "no empty accessible spot configured to store it.
Expected behavior
Pawns should still be able to use the IO ports to access the DSU when pawn access is disabled.
Actual Behavior
Well, they can't.
Screens following these steps and showing the configuration of the DSU and IO ports
Rimworld (please complete the following information):
RimWorld Version: 1.5
PRF Version: 2.8.7
Modlist (please complete the following information):
Just Harmony and PRR installed.
The text was updated successfully, but these errors were encountered:
Mysterius
changed the title
Disabling "Pawn Access" completely disable pawn interaction with a DSU and its IO ports
Disabling "Pawn Access" completely disables pawn interaction with a DSU and its IO ports
Sep 12, 2024
Describe the bug
Disabling "Pawn Access" completely disable pawn interaction with a DSU and its IO ports
To Reproduce
Reproducibility: ?
Steps to reproduce the behavior:
Expected behavior
Pawns should still be able to use the IO ports to access the DSU when pawn access is disabled.
Actual Behavior
Well, they can't.
Screens following these steps and showing the configuration of the DSU and IO ports
Rimworld (please complete the following information):
Modlist (please complete the following information):
Just Harmony and PRR installed.
The text was updated successfully, but these errors were encountered: