Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Enhancement] Set result and success of command
See original GitHub issueVanilla commands outputs whether the command has successfully executed or not. It also keeps outputs its result.
Example:
/tp @a[name=Notch] @s
This command will only be successfully run if there is a player named Notch in the world. Otherwise the success score will be 0.
The success is always either 0 or 1. In the picture above it’s 0, as there is no player named Notch online.
Vanilla commands also output their result, which can be more than 0 or 1.
Example:
The success of this command is 1. The result is 35, as there are 35 entities in the world.
Right now, every commandAPI command will always be successfully run, so the success of every command will always be 1. The result is 1 too.
It would be awesome if we could do this with commandAPI commands too 😄
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m hoping to resolve the permissions bug of
minecraft.command.blahbefore the 1.7 release - I’ve finally found a potential fix for this pretty critical bug!Awesome, will test this out! Getting to the point where a 1.7 release would be nice so I can include it with Maven rather than handcompiling my own 😃
Thanks again!