You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is part of a series of issues regarding the extension of the Paper documentation regarding Paper's Brigadier API.
In addition to custom argument suggestions, normal custom arguments should also be documented. This would have two parts. For once, the standard CustomArgumentType<T, N> and its methods should be documented and given an example to. Secondly, CustomArgumentTtype.Converted<T, N> should also be documented.
One point to definitely mention is the inability to provide the red client-side text in case the argument is invalid, since for that the client needs to do validation, which custom argument types do not do, since they actually only send their native type (and on tab complete possible suggestions) to the client, not their parser.
For the standard custom argument type, a MiniMessage-string styled Component argument could be created, since the native one expects its input as JSON, which is not very user-friendly.
For the converted one, we can provide a similar setup like the old documentation: using ice cream flavors. Here, we can link to command syntax exceptions. A possible class to showcase and describe could be this one:
Note
This issue is part of a series of issues regarding the extension of the Paper documentation regarding Paper's Brigadier API.
In addition to custom argument suggestions, normal custom arguments should also be documented. This would have two parts. For once, the standard
CustomArgumentType<T, N>
and its methods should be documented and given an example to. Secondly,CustomArgumentTtype.Converted<T, N>
should also be documented.One point to definitely mention is the inability to provide the red client-side text in case the argument is invalid, since for that the client needs to do validation, which custom argument types do not do, since they actually only send their native type (and on tab complete possible suggestions) to the client, not their parser.
For the standard custom argument type, a MiniMessage-string styled
Component
argument could be created, since the native one expects its input as JSON, which is not very user-friendly.For the converted one, we can provide a similar setup like the old documentation: using ice cream flavors. Here, we can link to command syntax exceptions. A possible class to showcase and describe could be this one:
Including its usage:
The text was updated successfully, but these errors were encountered: