[1.14.4] displayGuiScreen() doesn't seem to work

[mohkamfer]

I made a screen extending Screen, and am trying to show it when a certain [client-side] event occurs. I do Minecraft.getInstance().displayGuiScreen(new ...) but nothing shows. I made sure the code actually reaches that line, but then it goes absolutely silent.

 

I'm trying to call it in a ClientChatEvent listener.

 

Backstory I'm trying to listen for a /commandString message sent by the player, show my screen then cancel the event. I had to use this dirty workaround since commands worked on single player only. Not sure if mentioning this could provide better support, but here we go.

 

EDIT: The Screen has nothing to do with the server. I listen for client events only. Not sure what's happening. I've seen some other threads, but they all 'suggest' that it should work on client just fine if it doesn't communicate with the server. If looking at vanilla code could help me, all I am seeing is Minecraft#displayGuiScreen() calls just like what I'm trying to do. Not sure why it isn't considered as a client-side call to it -- if this is even the problem.

 

ANOTHER EDIT: Yes, it worked with commands registered on server starting event. If anybody would wonder.

Edited January 23, 2020 by mohkamfer
More information again!

[Cadiboo]

Client side only commands have always been a forge addition. Since mojang switched to their new command system in 1.13+, Forge hasn’t re-implemented client side commands. I hope this helps.

[mohkamfer]

11 hours ago, Cadiboo said:

Client side only commands have always been a forge addition. Since mojang switched to their new command system in 1.13+, Forge hasn’t re-implemented client side commands. I hope this helps.

Well aside from commands, what about the guiScreen not showing up? I already match a command string and what's missing is showing it

[mohkamfer]

23 minutes ago, diesieben07 said:

You have to wait one tick to open your GUI.

Well I could do that, however I'm concerned that running a check every tick could harm performance. Could there possibly be a better way to schedule a task to run once, and then not to bother every single tick after? Just like we can post a Runnable using a Handler.