on a copy of my map I loaded in 17w45b I have this in a command block
/scoreboard players set @a[score_wet=1..] iswet 1
Apparently [score_wet] is an unknown option. Do any of these commands besides execute like not support selector arguments? or perhaps did scoreboard target selector arguments move to being an nbt tag?
Edit: Just tried to put the whole command in /execute as @a[score_wet=1..] run scoreboard players set @s iswet 1 with no luck. Looks like the scoreboard objectives selector arguments changed entirely.. Hmm..
And what exactly could I use to replace /scoreboard players test or /testfor if I had an entire command block devoted just to detect the condition to further run more commands in order to save fps for players. It feels like I would have to combine it with the next conditional command or could I run an empty execute command to detect if a player is in a certain area for example.
Either way, This is going to take me MONTHS to convert my map. I do see much more potential with the new commands, but since the map is already programmed in a giant undergound computer room, it'll be tough. It feels like having to relearn commands again
I'm using the following with a trigger value. comparing it to a scoreboard value i set to 'one' with 1 as a value.
This is on 17w49b
execute as @a run execute if score @s spawn >= @s one run tp @s -167 72 256
execute as @a run execute if score @s spawn >= @s one run scoreboard players set @s spawn 0
scoreboard players enable @a spawn
on a copy of my map I loaded in 17w45b I have this in a command block
Apparently [score_wet] is an unknown option. Do any of these commands besides execute like not support selector arguments? or perhaps did scoreboard target selector arguments move to being an nbt tag?
Edit: Just tried to put the whole command in /execute as @a[score_wet=1..] run scoreboard players set @s iswet 1 with no luck. Looks like the scoreboard objectives selector arguments changed entirely.. Hmm..
And what exactly could I use to replace /scoreboard players test or /testfor if I had an entire command block devoted just to detect the condition to further run more commands in order to save fps for players. It feels like I would have to combine it with the next conditional command or could I run an empty execute command to detect if a player is in a certain area for example.
Either way, This is going to take me MONTHS to convert my map. I do see much more potential with the new commands, but since the map is already programmed in a giant undergound computer room, it'll be tough. It feels like having to relearn commands again
I'm using the following with a trigger value. comparing it to a scoreboard value i set to 'one' with 1 as a value.
This is on 17w49b
While the way I was doing it yesterday works, this way is better. (17w50a)
In your case the line would be