-
Bug
-
Resolution: Awaiting Response
-
None
-
Minecraft 1.8, Minecraft 1.8.1, Minecraft 1.8.2-pre4, Minecraft 1.8.2-pre5, Minecraft 1.8.2-pre6, Minecraft 16w05b, Minecraft 16w06a, Minecraft 1.9 Pre-Release 1, Minecraft 1.9 Pre-Release 2
-
None
-
Server
java8
win8
-
Unconfirmed
EDIT
- Play on a server (snapshot 16w06a)
- OP player "Anybody"
- Close server and rename "Anybody" to "OtherName" || alternatively rename the player via mojang.com (default way to do it)
- Because the player "Anybody" has the same UUID as "OtherName" (cause they changed their name), "OtherName" will still be able to use commands (ok) but "Anybody" will also be able to.
- Rejoin server, (chat says, Anybody (formerly known as OtherName) joined the game.
- you will be able to use OP-level:4 commands, until you get opped again. Then it will obey the server.properties default (e.g. level:1)
- I suggest changing the /op command to -> /op <player> [level] (no level given: defaults to server.prop, someone from level 3 can't op another to level 4, etc.)
----------
play on a server
/op a player (GarryGoose for example)
(his op level is 4)
change in server.properties -> op-permission-level=1
change GarryGoose's name to something else (Ghast2000 for example)
if you then search in the OP list (ops.json) you will still find the old name even after running the server.
GarryGoose is still OP (Ghast2000 can still use it)
but if you /op Ghast2000 again he will lose his level 4 and turn to level 1 op level.
thus pushing 2 names with same UUID in the ops.json one with lvl:1 and one with lvl:4