Closed James-E-A closed 2 years ago
This issue is a soft-blocker of https://github.com/GeyserMC/Floodgate/issues/261 -- there are, obviously, workarounds that could be applied at the plugin level (such as sending the informative debug info about the problem via sender rather than to the console log), but fixing the upstream problem (that Message.UNEXPECTED_ERROR
isn't working) seems like a better course of action
async, the rcon stuff just executes a command and returns the response, that means that if a command goes off the main thread and tries to send a message, that will be blocked
There is some intent for us to support this (but, plugins will need to explicitly support this) from our side, however last I knew upstream had some talks about it so that kinda stalled us off on that, at this point, not really within our control and there is already stuff tracking this somewhere
Side note: there are also (closed afaik) issues on LuckPerms for this same thing
Expected behavior
Observed/Actual behavior
Steps/models to reproduce
skyridersam
for convenience)fwhitelist add skyridersam
(or your selected gamertag)Plugin and Datapack List
floodgate, Geyser-Spigot
(There are 2 data packs enabled: [vanilla (built-in)], [file/bukkit (world)])
Paper version
git-Paper-177 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT) (Git: 2e99e5e)
Other
Specifically, the issue is that code that calls
sender.sendMessage(Message.UNEXPECTED_ERROR)
, such as this error handler inorg.geysermc.floodgate.command.WhiteListCommand§performCommand
: this error is sent nowhere that I can tell, though the developer of this code seems to believe that the line itself is correct in-context.