Exactly as the title states, causing bugs like MC-121629. Will continually update with consequences of all server commands. Commands of note are listed:
/kick
: Exits the world and returns the player to the multiplayer menu./ban
: Exits the world and returns the player to the multiplayer menu. Does not prevent future access to the world./deop
: Appears to deop the player and restricts access toF3+N
, but the player can still run commands. Running/op
yields that the player is "already an operator." Access toF3+N
is regranted upon a reload Thanks to @unknown./list
: Prints the player alone as expected. (this may be WAI, as it has no reason to be limited to multiplayer)/save-all
: Saves the game as expected./setidletimeout
: Doesn't appear to do anything (I don't think ops get kicked anyway)./stop
: Exits the world and returns the player to the multiplayer menu (a la MC-45602).
Linked issues
is duplicated by 28
Comments 9
/pardon
:
1.13-snapshot: Console outputs "Nothing changed, the player isn't banned" when trying to unban a user that was /ban
ned.
1.12: Console outputs "Unknown command".
@James Mills Of course it outputs "Unknown command" in 1.12, this bug says that these command become available in 1.13. Also, pretty sure /broadcast isn't a command.*
*I checked, and it was in Classic, but it was replaced with /say.
I tried /ban on me and it said banned off singleplayer world and server quits and i came back to my world none banned,
But i try on /ban on sp lan player now another player cant join
and i /pardon that player banned and player join again!
/kick
on a lan server should probably be enabled (probably). However the issues with freezing are supposed to be fixed; at least, they were when I tested MC-92255... hm.
Phoenix SC made a video about this with some other facts as well: What Happens if You /ban Yourself in Single Player