Posted 10 January 2015 - 07:27 PM
The command block API currently cannot provide the information in the second field of text in the command block. This limits any information output from the the block to binary redstone interaction, reducing the potential of the various world-inspecting commands to near-zero. Considering how these commands would otherwise allow for extremely advanced world interaction, this is an extremely unfortunate limitation. Not to mention an unneeded one, since this function would only be a slight variation of what is already in the game.
Introducing commandBlock.getResult() would solve this, and drastically increase the potential of the cmd block API. I can't think of any technical reasons this shouldn't be possible. Even if the API bypasses the block entirely when executing commands, we would still have the option to trigger them via redstone, sacrificing a tick of time in order to get the information.
Introducing commandBlock.getResult() would solve this, and drastically increase the potential of the cmd block API. I can't think of any technical reasons this shouldn't be possible. Even if the API bypasses the block entirely when executing commands, we would still have the option to trigger them via redstone, sacrificing a tick of time in order to get the information.
Edited on 10 January 2015 - 06:32 PM