Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Disabling "Pawn Access" completely disables pawn interaction with a DSU and its IO ports #814

Open
Mysterius opened this issue Sep 12, 2024 · 7 comments · May be fixed by #830
Open

Disabling "Pawn Access" completely disables pawn interaction with a DSU and its IO ports #814

Mysterius opened this issue Sep 12, 2024 · 7 comments · May be fixed by #830
Labels
bug Something isn't working

Comments

@Mysterius
Copy link

Mysterius commented Sep 12, 2024 •
edited
Loading

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:

  1. Enable only Project Rimfactory
  2. Generate a basic map
  3. Build a DSU, an input IO port, optionally an advanced IO port. Link them to the DSU.
  4. Enable everything in the storage settings on the DSU. Pawns should start hauling things to the DSU or the input IO port.
  5. Disable Pawn Access on the DSU.
  6. 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
1 (2)
2 (2)
3 (1)
4

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.
@Mysterius 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
@Sn1p3rr3c0n
Copy link
Collaborator

relates to #566

@Mysterius
Copy link
Author

Do you intend to work on it in the near future? No pressure, it's just that I have to plan my base around it otherwise ;).

@Sn1p3rr3c0n
Copy link
Collaborator

I honestly can't give you a timeline.

@Sn1p3rr3c0n
Copy link
Collaborator

relates to #566

I was wrong.
Or I'm missing something. this is not related in the way i assumed.
I'll need to Investigate further.

@Sn1p3rr3c0n Sn1p3rr3c0n added the bug Something isn't working label Oct 20, 2024
@cvrunmin
Copy link

disabling "Pawn Access" will also disallow machines to output products into IO ports linked with the DSU. assume they're using the same logic? RimWorld 1.5 and RimFactory 2.8.7

@Sn1p3rr3c0n
Copy link
Collaborator

hmm I believe the implementation of #787 is causing this.
I should reevaluate that fix maybe there is a better way to do that

Sn1p3rr3c0n added a commit that referenced this issue Feb 14, 2025
@Sn1p3rr3c0n
experimental fix for #814 by blocking pawn access in a diffrent way
2d7819e
@Sn1p3rr3c0n
Copy link
Collaborator

I might have a fix for this, but I need help testing it.
Especially with modded games.
I fear that there could be some incompatibilities with mods that alter Hauling, that might cause pawns to access the DSU despite it being not allowed.

Compiled dll for the fix is attached
ProjectRimFactory.zip

@Sn1p3rr3c0n Sn1p3rr3c0n linked a pull request Feb 15, 2025 that will close this issue
experimental fix for #814 #830
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

experimental fix for #814 zymex22/Project-RimFactory-Revived
3 participants
@Mysterius @cvrunmin @Sn1p3rr3c0n