Hello! I'm asking about an issue that I have on my server where any command to change a players claim config is overwritten by the server config forcing it to . I've looked all over for the fix in config and even reloaded the config but I cant seem to find a fix. (See Image 1)

I'm only using server side mods with geyser bedrock - java crossplay support.

Version is 1.21.8, loader is fabric (api 132), can provide any other information if needed.

Additional issues I've found is that doors dont seem to open for users in server claimed chunks even when permissions are set to <3> (exception for everyone).

This refers to the "playerConfigurablePlayerConfigOptions" option in the main server config. By default, it contains this doors option, so you or somebody else removed it manually.
Also, there's no way to reload the config, you need to restart the server for that. And only change the config files when the server isn't running, to make sure they're not overwritten. Only openpartiesandclaims-server.toml should be edited as a file though, everything else can be edited in game.
As for server claim doors, I don't think you changed the right config, unless you can provide more details.

I don't have any log of "playerConfigurablePlayerConfigOptions" in the server files at all. Here are some more screenshots, let me know if you need any more information.

Let me know if theres anything specific that you need in order to help with this, or if I should just reinstall the entire server (oops).

I'm not looking for any logs. It's an option in openpartiesandclaims-server.toml

The issue is that within this, I'm pretty sure any config is force set to the server.
Either that or I'm just going insane

UNLESS I NEED TO ADD THE "hand$" IN THIS CONFIG TOO

just added "claims.protection.exceptionGroups.block.handInteract" to this list and it didn't work. Gave same "server config forces it to " prompt

Did you change anything about this option or is this exactly how it has been this whole time?

This is how it has been the entire time. The only thing I changed was adding "claims.protection.exceptionGroups.block.handInteract" and now "claims.protection.exceptionGroups.block.handInteract.Doors" to the list at the bottom to check if that worked.

I also found out that it's only the "Doors" command that is forced to the server config value

It should be "claims.protection.exceptionGroups.block.interact.Doors" as is by default.

hmm
When typing the command into minecraft as a user, it's changed to "claims.protection.exceptionGroups.block.handInteract.doors" in the command list. Like so:

I'll try with just "interact.doors"

Ok, I just realized you added hand$ to the group definition of Doors, so it creates a different player config option, which is claims.protection.exceptionGroups.block.handInteract.Doors.

You should probably just remove hand$ because I have no idea why you even added that.

I added "hand$" in front of the "Doors" group here, which was probably the issue.

I'll try without!

Alright. Make sure the list still contains the default claims.protection.exceptionGroups.block.interact.Doors then.

That fixed the forced config issue!!

there's another issue that I have with server-claimed doors not opening for non-op players

How are you setting the config option for that?

through the minecraft commands of "/openpac server-claims-config set claims.protection.exceptionGroups.block.interact.Doors 3"

That looks like it should work. Try again.

it still doesn't let default players from opening doors in the server claimed chunks. I have a video of what I'm talking about but I think the file size is too big

Then maybe the chunks you are testing are claimed with a sub-config with a different value.

ran this command and it should still work? let me check something else as well.

Is "main" the only sub-config suggested there?

Yes. I also just tried admin mode and it didn't seem to change anything

What does it say when you try to open the door?

There isn't anything said when opening the door, which is the strange part. It just forces itself closed.
Maybe its spawn chunk protection?

Oh my god it was spawn chunk protection

Okay, that makes sense. You can disable that in the vanilla config.

Everything seems to be fixed now thank you for your help!!
Sorry about my stupidity lol

Glad I could help!

Tbh, I should probably add a warning about spawn protection being enabled.