While adding API for dialogs in BungeeCord i encountered the problem that the client will throw an exception everytime it receives a ShowDialog packet in configuration state. As the packet is specificly registered for this state, i think thats not how it should be.
Sending the packet in game state works fine
I think the registry is not established to that point that it works.
Environment
BungeeCord -> Vanilla Server 1.21.6 pre4 on windows
Client 1.21.6 pre4 on the same machine
Attachments
Comments 5
Dialogs are supported in configuration phase, but from the log (Expected non-null compound tag) it looks like some malformed data is included in that packet. 🙂
In configuration phase it is not possible to send a dialog by id as registries are not yet initialised, they must all be sent inline.
i am not sure how they can be malformed as the same packet works perfectly fine in play state, to dialogs work differntly in game state and config state?
Cause in bungeecord we encode the packet the same in play state as in config state, but in config state it just doesn’t work and in game state it does.
And of cause i sent them inlined
Dialog notice = new NoticeDialog( new DialogBase( new ComponentBuilder( "Hello" ).color( ChatColor.RED ).build() ) );
player.showDialog( notice );
Thank you for your report!
After consideration, the issue is being closed as Invalid.
This report does not describe a bug.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki