%d on a line by it self will send the result to the server, this is by design, you could do something like this
However I have discovered an a logic flow problem with the order of commands when mixing commands inside and outside of a command block
Code:
TEST 1
{
TEST 2 - %f
TEST 3 - %f
}
TEST 4
The commands are executed in the wrong order.. as seen below
TEST 2 - zz
TEST 3 - zz
TEST 1
TEST 4
Testing with /echo prefix like this and the result is
Code:
/echo TEST 1
{
/echo TEST 2 - %f
/echo TEST 3 - %f
}
/echo TEST 4
TEST 1
TEST 2 - zz
TEST 3 - zz
TEST 4
The problem is with the way "/prefixed" commands vs direct commands are executed when the command contains command blocks.
And if you use multiple command blocks the blocks execute in reverse order. Its a bit of a mess and it will take me some time to hammer out these problems.
It appears that my token parser fails to check for multiple identical modifiers within the same command line, I will have to re-work this.
I could add variables that can be set and then replaced later but the format will need to be unique so that it doesn't conflict with existing token elements I think I'd need to do something like this /set @<name>@ <value> where the name is encased with @'s I can't use $, %, #, !
Threaded Mode