opac version: 1.20.1-0.22.2
create version: 1.20.1-0.5.1f
I made a tree farm using mechanical bearing and only the deployers on it dont work in the claim, but it works just fine outside the claim.

Please make sure the contraption is comfortably within the claims, not touching the very edge.

Thanks! Do deployers on a mechanical bearing not work for all action types like placing blocks, breaking blocks or other item use? Please figure out if a specific type of action isn't working, not deployers in general.

Its not touching any edges. Its in the very middle of a huge claim.

Can you send me screenshots showing that?

And is it a minecart or train contraption you rolled into the claim?

Its not a train or minecart contraption, its a mechanical bearing contraption.

Can you send a better screenshot of the map?

and here is the claim settings
openpartiesandclaims-server.zip

It looks like its deployers on mechanical bearing and windmill bearing in general. I tried everything that a deployer can do and nothing worked. Deployers on trains work just fine.

It seems to be just happening in my claim for some reason

I've encountered a similar issue before and solved it. The deployers are doing the action with the permissions of whoever placed them at first, and their permissions do not update when the builder's permissions update. If the claim was created after the deployers were placed or they were placed by someone who is not a member of the claim, they will not work until they are destroyed and replaced. A member of my party placed deployers on a server, we added a claim there later, and they stopped working. I had to add that member to my party and then destroy and replace all the deployers for them to start working again. Have you tried this?

@ratemisia Last time I looked at how deployers worked, they were always using the same UUID, not the UUID of the player who placed them. Protection from actions like this works based on the anchor position of the whole contraption. Static deployers work similarly, based on the deployer block's position. It does not look at who placed them. Obviously, this could be caused by some Create addon that makes deployers use the UUID of the player who places them. Are you using anything like that?

[snip] Static deployers work similarly, based on the deployer block's position. It does not look at who placed them. Obviously, this could be caused by some Create addon that makes deployers use the UUID of the player who places them. Are you using anything like that?

Hmm. That's odd. I'm not aware of an addon that would have altered this behavior. I'm not familiar with the underlying code, so I'll have to defer to your knowledge, but the behavior in my game did seem to line up with my suggestion above: Claiming a chunk made the deployers stop working, and then replacing them (which must be done by a party member, as doing so requires build permissions) made them work again without incident. I could likely have conflated the build permission with the issue of the deployers not working in the first place, but it seems odd that replacing the block after a claim change would fix it if the claim change wasn't adversely affecting the block somehow. It seems the truth in my case is more complicated.. I would offer to troubleshoot further, but I may have been experiencing a completely different issue that has no place in this thread. I suppose it depends on if @Janko1902 had built the contraption before claiming the chunks and had it stop working on or near the claim change, as I did.

@ratemisia I think the deployers just "break" in some cases if they are prevented from doing their thing. You do have to replace them when that happens. But then again, why would they be prevented from working anyway, unless their behavior is modified by an addon?

I did replace them to see if that fixes t but nothing changed. If any addon is modifying deployers here is the modpack im using: https://www.curseforge.com/minecraft/modpacks/farwater/files/5725041