New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signed commands support #381
Comments
Care to elaborate a bit more about signed commands? This is really vague.
|
I did as you ask, but I think there is some space for exploration and it may not end up looking like this. |
@demkom58 Thanks very much! This is actually really helpful. I think making something like this will be pretty possible. Scheduling for 9.0.0. |
Currently implemented on the This is only compatible with Paper 1.19.3 onwards (Paper 1.19.2 and below doesn't have Adventure 4.12.0). Adventure API's support for signed arguments is really not that well fleshed out (yet?) and has a lot of limitations other than providing an API for inspection purposes for command arguments. Apparently, player chat has a very strict lifecycle which may not be able to persist long enough to send signed player messages (but this is just conjecture). After briefly browsing the Adventure Discord Server, the API can only create system signed messages. Based on current developments in Paper, it seems that sending The CommandAPI will need an example to demonstrate how to use signed messages. I'm sure that in time, Adventure and Paper will figure out how to make a useful API for SignedMessages, but at the moment I can't recommend the above example:
At the time of writing, the |
Unscheduling this request for the next release. This functionality seems to be still very early in development and doesn't have any meaningful use cases yet. |
Description
It would be nice to see an API for working with signed commands.
It also looks like Adventure in version 4.12 has the required API for this. FYI: SignedMessage.java
Motivation
In Minecraft, there are commands that allow you to write in private messages, as far as I understand, the command arguments are signed (FYI: Protocol#Chat_Command). For any use case that accepts player input and outputs, this would be a useful feature.
The first use case that comes to mind is message channels: global, local, etc.
Expected code
Extra details
No response
The text was updated successfully, but these errors were encountered: