An issue has been noticed with how Smelt changes the direction of command blocks. When a command block is conditional, this breaks the conditional logic.
Example: http://i.imgur.com/PjQLZT7.png
Workaround: Users can insert their own blank commands to push the chain of blocks 'around the corner' before the conditional chain is placed. I would prefer it if Smelt could do something to 'fix' this scenario.
There is one known solution that I've tested, which involves inserting generated command blocks when the direction is changed, and the one before the conditional block then uses /blockdata to try and reset the SuccessCount of the previous command. This will fail if the previous command failed (is already 0) and will succeed if the previous command succeeded (it was 1, so we could reset to 0).
Example: http://imgur.com/a/0EqFk
There may be issues with this that need considering. Could this affect other commands or use cases?
It might be possible to also solve this using /stats block but that would require a custom entity and scoreboard objective as well. Which means that the map maker would HAVE to install a module into their world to allow for this type of fix (or the generated code would have to EACH TIME).
I'm going to think about this some more.
An issue has been noticed with how Smelt changes the direction of command blocks. When a command block is conditional, this breaks the conditional logic.
Example: http://i.imgur.com/PjQLZT7.png
Workaround: Users can insert their own blank commands to push the chain of blocks 'around the corner' before the conditional chain is placed. I would prefer it if Smelt could do something to 'fix' this scenario.
There is one known solution that I've tested, which involves inserting generated command blocks when the direction is changed, and the one before the conditional block then uses /blockdata to try and reset the SuccessCount of the previous command. This will fail if the previous command failed (is already 0) and will succeed if the previous command succeeded (it was 1, so we could reset to 0).
Example: http://imgur.com/a/0EqFk
There may be issues with this that need considering. Could this affect other commands or use cases?
It might be possible to also solve this using
/stats blockbut that would require a custom entity and scoreboard objective as well. Which means that the map maker would HAVE to install a module into their world to allow for this type of fix (or the generated code would have to EACH TIME).I'm going to think about this some more.