This has its own operation system, which is translated into MC commands when the filter is run. According to the documentation:
The other important thing is that as of now you are not allowed to use the scoreboard players operation command in RPL, because it will confuse the operation signs with its own format. RPL implements all the features of this command, so you probably won't need to use it anyway.
The documentation describes this other system, as well as many other systems to make your code cleaner and easier to write. If you do need to use operation, place a $ as the first character on the line so RPL doesn't try to translate it.
It would be useful if the length of each line were made available as relative coords at compile-time. Then it would be possible to implement recursion by having a copy of a line as each stack frame, stored at an offset corresponding to its return address, and growing the stack perpendicular to the instruction flow. (The offset would thus serve as a return address, and we wouldn't have to worry about having parallel processes collide.) For instance, if all lines ran in +x direction, and the stack was embedded in bedrock to save relighting cycles, then gosub would be accomplished by
Hey!
I tried playing around with your filter and I found that scoreboard operation commands seem to be ignored by it.
I have not used any fancy rpl syntax (I don't even how to yet :D)
Every commandblock got generated as I expected except for the operation one.
Does anyone have an idea? Might this be a bug?
I tried to generate the following:
#new_line z ~ ~1 ~
/scoreboard players set @e[type=Arrow,c=1] ACV_COLOR 0 {inGround:1b,damage:5.5}
/scoreboard players set @e[type=Arrow,c=1] ACV_COLOR 1 {inGround:1b,damage:6.0}
/scoreboard players set @e[type=Arrow,c=1] ACV_COLOR 2 {inGround:1b,damage:6.5}
/scoreboard players set @e[type=Arrow,c=1] ACV_COLOR 3 {inGround:1b,damage:7.0}
/scoreboard players operation Color ACV_Internal = @e[type=Arrow,c=1] ACV_COLOR
/execute @e[type=Arrow,score_ACV_COLOR_min=0,c=1] ~ ~ ~ /summon ArmorStand ~ ~ ~ {CustomName:"ACV_Main",NoGravity:1b,Invisible:1b,Invulnerable:1b,Marker:1b}
/kill @e[type=Arrow,score_ACV_COLOR_min=0]
/execute @e[name=ACV_processMain] ~ ~ ~ /setblock ~ ~ ~ redstone_block // conditional
/execute @e[name=ACV_online] ~ ~ ~ /setblock ~ ~ ~ stone // conditional
Your redstone programming language really helped me a lot. This deserves more popularity!
But recently I'm converting my system to 1.9, and find that a bit troublesome. Do you have a plan to implement the RPL for the 1.9 command blocks?
This has its own operation system, which is translated into MC commands when the filter is run. According to the documentation:
The documentation describes this other system, as well as many other systems to make your code cleaner and easier to write. If you do need to use operation, place a $ as the first character on the line so RPL doesn't try to translate it.
How do you get the command blocks to be 1 block apart? I tried inserting a blank line but it still puts them all together?
Tired of the same old maze maps? Me too! Click here for an endless maze, in which you try to survive and it's randomly generated so it's different every time!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt would be useful if the length of each line were made available as relative coords at compile-time. Then it would be possible to implement recursion by having a copy of a line as each stack frame, stored at an offset corresponding to its return address, and growing the stack perpendicular to the instruction flow. (The offset would thus serve as a return address, and we wouldn't have to worry about having parallel processes collide.) For instance, if all lines ran in +x direction, and the stack was embedded in bedrock to save relighting cycles, then gosub would be accomplished by
clone subX subY subZ subX+sublength subY subZ ~ ~ ~1
setblock ~-2 ~ ~1 redstone_block
$
// The above empty command block will be replaced by a redstone block to indicate that the sub has returned.
fill ~-3 ~ ~1 ~sublength-2 ~ ~1 bedrock
And return would be
setblock ~-sublength ~ ~-1 redstone_block