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.
Continuing with the advanced topics, there should also be a page noting the usage of .fork, .forward, and .redirect. Thanks to PaperMC/Paper#11868, this can now be achieved without the usage of internals or userdev.
Basically, the difference between these "flow controlling" methods should be noted and an example should be given. Furthermore, a reference to the CommandSourceStack#withExecutor/Location should be included. The fact that this is only available since the middle of version 1.21.4 could also be helpful.
Note
This issue is part of a series of issues regarding the extension of the Paper documentation regarding Paper's Brigadier API.
Continuing with the advanced topics, there should also be a page noting the usage of
.fork
,.forward
, and.redirect
. Thanks to PaperMC/Paper#11868, this can now be achieved without the usage of internals or userdev.Basically, the difference between these "flow controlling" methods should be noted and an example should be given. Furthermore, a reference to the
CommandSourceStack#withExecutor/Location
should be included. The fact that this is only available since the middle of version1.21.4
could also be helpful.A possible example could look like this:
The text was updated successfully, but these errors were encountered: