I have some deployers I use for opening special doors in my server (with their interact action), but they don't work in the server claim. They work outside of any claim and also work in a personal player claim, but if placed in a server claim they do nothing. I tried adding their UUID to the openpartiesandclaims-server config, but that didn't change anything. I also tried adding their class, but that didn't change anything either.

Is there a way to allow them to work that I missed? I'm using OPAC Forge 1.20.1-0.25.3

Right, my bad. Are you 100% certain it's the deployer not being able to interact? Does the deployer's hand itself move? If not, then it must be something else on the way to the deployer. In fact, when deployers get protected against, they get stuck until you replace them (because of code on create's end), so this doesn't sound like deployer interaction protection, the way you're describing it.

I'm pretty certain. I can see the deployer hand is moving, its just not interacting with the door within the server claim. It interacts fine when the claim is removed or swapped out for a player claim.

That is really strange. I'll investigate soon when I'm less busy.
Can you send me your default player config and server claim config?

Thank you, I really appreciate the help

The server claim config is: https://gist.github.com/Maltshakes/65250011146e1fd638d289725c0a93a1
The default player config is: https://gist.github.com/Maltshakes/8a12adb3af99a664c429436ff5d56154

I did remove those settings before the final test and posting here, sorry for not making that clear. The server claim is very large as well, so the deployers are definitely in it. They're around the center of the chunk.

I would guess they're simply on the very edge of the claim but should be at least 1 block inside the claim to safely work.
Remove anything you added for them in the config file, because it's not necessary and the class option does the opposite of what you want to achieve. It excludes entities from being considered stationary. It's meant for stuff that inherits the UUID from whoever places it, such as computercraft turtles. If a turtle is placed by a stationary fake player, then the mod should still protect from the turtle despite it having the same UUID as the fake player.
Deployers should work by default.

Here is a copy of my server config in case it helps: https://gist.github.com/Maltshakes/65250011146e1fd638d289725c0a93a1

Are you sure this isn't just vanilla spawn protection, unrelated to OPAC? Please test by unclaiming the chunk.

I unclaimed the chunk and it works fine. Reclaim the server claim and it no longer works.

Interesting. And if you claim with a personal claim, not server claim, it works? Because that doesn't really make much sense to me.
Please give me more details about the "special doors", maybe send some screenshots.

Yes exactly, that's the part that has me scratching my head. The deployers + these doors work fine if they are outside of a claim, or within a player claim. They just don't work in a server claim. I tested on both on the server and in a singleplayer instance and the behavior was the same.

The door in question is the Portcullis from Macaw's Doors. It can only be opened with a hand interaction so redstone won't work here - which is why I need a deployer to automate it.

Here is a screenshot, the deployer is immediately below it, hidden underground.

And with the chunk borders visible

Do they open if you right click them in admin mode?

I think the difference between server and player claims might just come from them being configured differently. The default player config probably has "Blocks From Other" protection disabled. It's not supposed to matter though. What Create version are you using?

Yes, with admin mode enabled I can open and close the doors fine.

I'm using Create version 1.20,1-6.0.6

Alright, please try updating OPAC to the latest version, in case that makes a difference. Doubt it though.

I'm only seeing forge-1.20.1-0.25.3 on Curseforge as the latest for Forge 1.20.1, which is what I am using.