There is a singular portal in my world that ceases to function whenever a server operator exists regardless of permissions set. This occurs if ANY op is set regardless of who & whether or not they are online.

Disabling op immediately fixes the gate for everyone. Granting stargate.* to everyone does nothing.

Nothing in the server logs with both debug options enabled indicates anything is wrong, has normal outputs saying user's have the permissions needed. Nothing denies it functioning

Things tried:

• I've tried replacing the gate with default layout nether.gate & issue persists.
• Different names do nothing.
• Moving the gate back 3 blocks doesn't work.

Original layout of the problem gate:

This is the config I have that exhibits this issue:

There is kind of already an solution for this server-side and it also seems tricky to implement; so I'm going to close this, for now

Edit: added a message to account for this in d107656

We found a problem with commit d107656
Reopening this issue to fix it.

Also, it looks like you are importing from another stargate fork.
That fork may have made some database formatting changes that are incompatible with SG10.

Did the problematic portal exist before you imported? Were there any other portals in the area?

I believe I started without any DBs from older forks as they didn't import properly anyway. This is an old server from 1.10 that I'm resurrecting so it's been a slow process & I can't say for sure. This is the only piece that seems to still cause issues

However, I can say for sure no gates imported properly and all of them had to be remade by hand
There is another gate one chunk away that works properly

I'll try changing my config over to the newer format & see if that helps

I've attached the current Stargate folder as a zip
Stargate.zip

Problem gate is 'Spawn' in world.db:

This is certainly an odd issue… off-hand, I can’t think of anything that might explain the observed behavior.

From what I can tell, vanilla operator statuses (including NOT_OP, OP, isOP, and getOperators) are not called, checked, or used anywhere in the plugin.

Unfortunately, we will probably need some more information to successfully reproduce the problem:

There is a singular portal in my world that ceases to function whenever a server operator exists regardless of permissions set.

• What is unique about this portal in particular? What distinguishes it from other (working) portals?
  • What is the portal's name, destination, flags, network, and owner/creator?
    • Can an identical portal be recreated elsewhere?
  • Are there any notable properties about this portal's location?
    • Is the area within your spawn chunks? Do any plugins impact this area in particular?
    • Does moving the portal elsewhere (i.e. to another chunk or elsewhere on the map) change anything?

Disabling op immediately fixes the gate for everyone. Granting stargate.* to everyone does nothing.

• Given that OP isn't checked, and that the issue persists, this might signify a compatibility issue.
  • Was an OP'd user the one who made the portal? What permissions did they have?
    • Can that same user make an identical portal elsewhere?
• What key (i.e. permission and/or block-impacting) plugins do you use with your server?
  • (If it is not too much effort), can the issue be replicated with stargate alone (i.e. disable everything else)?
    • If stargate works alone, slowly re-enable plugins until you find the conflict.

Nothing in the server logs with both debug options enabled indicates anything is wrong, has normal outputs saying user's have the permissions needed. Nothing denies it functioning

• If possible, can you please provide a copy of the relevant logs
  • If you have an advanced permission plugin, try a verbose trace when creating and/or using the portal.
• How precisely does it fail to function?
  • What happens once a portal is activated? Is the portal-open material placed?
  • What happens if a player attempts to enter the portal?
  • Does the portal work if it is created with the A flag?

Here's a video replicating the problem:
https://www.youtube.com/watch?v=b9X0Kg9SvOY

0:00​ - gate working before OP
0:18​ - make someone else OP
0:32​ - original gate not working
0:52​ - alternate gate still functioning
1:08​ - de-oping other player, so there are NO server OPs
1:18​ - gate working again

If the portal is close to the spawn-point, then this might be related to spawn protection.

Spawn prot is a vanilla feature that works as follows:

• If an op'd player exists, an area surrounding the spawn-point is protected from non-op'd players.
  • The size of this protected area is defined in server.properties
  • This protection includes restrictions on block-placement and interactions.
• If the operators list is empty, the protection for that area does not apply.

You can test if your portal was made in a spawn area by trying to place a block besides the portal as a non-op'd player.

If this issue is caused by spawn prot, some possible solutions might include:

• Disabling and/or reducing the spawn protection via the server.properties file
• Moving the portal outside of the spawn-protected area.

We will also look into other solutions to fix this.
That said, plugins are not allowed to mess with spawn prot, so it might be impossible to fix on our end.