[BDS-18725] [Scripting] isOp() returns false when players are operator

-Version is 1.20.30 - Not available to select- ** It is now available so have updated this.

isOp() from the Player class is always returning false, even if the player is operator, except if setOp(true) is called first.

This defeats the purpose of having an isOp() method if you have to manually check player IDs just to see if they should have setOp() called.

Linked issues

is duplicated by 1

MCPE-173980 @minecraft/server (gametest) player.isOp() returns false Resolved

Attachments

Example_Behavior_Pack.zip

level.dat

MinecraftScriptingBug_conv.mp4

world_behavior_packs.json

Comments 15

migrated 2023-09-27T15:13:18Z

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Can you please describe your issue in more detail?

To make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.
Observed Results:
(Briefly describe what happens)
Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

migrated 2023-09-27T20:26:52Z

Really? Marking it resolved without even looking into it. I'm not sure how much clearer I could have been.

Steps to Reproduce:

1. Make a Bedrock Dedicated Server

2. Use the Minecraft Script API

3. Call the function Player.isOp() in the context of a Player who is operator e.g. using the PlayerBreakBlockAfterEvent

4. Observe the result with console.log()

Observed Results:

The function always returns a value of false even when the player is operator

Expected Results:

The function returns true when the player is operator

migrated 2023-09-28T13:58:09Z

Any progress?

migrated 2023-09-29T08:37:52Z

Does it only occur on Linux?

This ticket will automatically reopen when you reply.

migrated 2023-09-29T09:57:25Z

I haven't tested on any other platforms so I don't know. Doesn't seem like something that would be platform specific.

5 more comments

migrated 2023-09-29T10:27:11Z

I need more detailed instructions how to reproduce this issue. If possible with video as well.

This issue will automatically reopen when you reply.

migrated 2023-09-29T12:34:48Z

Ok. Can you stop marking it as resolved then? It's not resolved.

migrated 2023-09-29T13:25:14Z

It is resolved as awaiting response. It automatically reopens when you reply. It is still tracked and open, but we need more detailed information how to reproduce this issue.

migrated 2023-09-30T00:36:37Z

Firstly, I am aware of how JIRA works. I am a .NET Software Engineer and use the same platform. That's very poor workflow management if you're marking them as resolved instead of one more suitable.

FYI this is a regression. It was working fine in 1.20.15 but not in 1.20.30.

Can you tell me what you have tried so far so I can make corrections that will allow you to reproduce the issue?

migrated 2023-09-30T04:02:49Z

I have confirmed that the issue is present on Windows also.

Steps to Reproduce:

Download the [Minecraft Bedrock Server Download | Minecraft|https://www.minecraft.net/en-us/download/server/bedrock] for either Windows or Linux.
Run the server and wait until console is idle and world is running then stop it (this makes sure the world is created)
Stop the server
Extract the contents of attached Example_Behavior_Pack.zip to the directory: ./behavior_packs/Example_Behavior_Pack
Place the world_behavior_packs.json and level.dat files in the ./worlds/Bedrock level/ directory
Open Minecraft for Windows
Join the Server
You will see in the console "Player is not op"
Run the command in the console to give yourself operator permission "op <player_name_here>"
Note the command output says "Opped <player_name_here>"
Leave the server.
Rejoin the server
You will see in the console "Player is not op"
Open the menu
You will see you do have operator permission but the server is not recognizing it.

Here is the code that checks the operator status using the Minecraft Script API specifically, this part: minecraft/server.Player Class

import * as server from "@minecraft/server"
server.world.afterEvents.playerSpawn.subscribe(onAfterPlayerSpawn)
/** 
 *  
 * @param {server.PlayerSpawnAfterEvent} eventData
 */
function onAfterPlayerSpawn(eventData) {    
    console.log(`Player ${eventData.player.isOp() ? "is" : "is not"} op`)
}

Observed Results:

The player is not being recognized as having operator status even though they do.

Expected Results:

When the player with operator status spawns, the message should say "Player is op".

Additonal Info:

Link to Video: MinecraftScriptingBug

Video Also Attached

migrated 2023-10-03T07:47:01Z

Any progress on this?

migrated 2024-03-18T08:43:36Z

isOp() working fine in local world for me. But in realms, it's not.

migrated 2024-04-06T11:32:28Z

I'm seeing exactly the same issue as described. My mod is designed such that it adds additional restrictions to players which aren't operators. This works as expected in a single player game (as I change my account type back and forth between Operator and Member) but in the bedrock server game it always returns false, for all players.

migrated 2024-07-25T14:55:08Z

you have to set op-permission-level in server.properties

migrated 2024-09-08T00:53:25Z

According to this https://minecraft.wiki/w/Server.properties the op-permission-level property is for Java Edition. This issue is for the Bedrock Server.