Now, when you wish to use the operator, select the one that has Source listed as Global. If/when Blizzard fixes the operator, you won't need to update your map, you'll already be using a correct version.
Obviously if you're creating your own library or a mod you'd vary these steps, but probably know what you're doing in that case anyways.
The built-in "within bounds" macro (operator) is bugged. It reads:
((#PARAM(value) <= #PARAM(min)) && (#PARAM(value) >= #PARAM(max)))This is checking X <= minimum, and X >= maximum. The min and max parameters should be reversed.
Workaround
((#PARAM(value) <= #PARAM(max)) && (#PARAM(value) >= #PARAM(min)))
Now, when you wish to use the operator, select the one that has Source listed as Global. If/when Blizzard fixes the operator, you won't need to update your map, you'll already be using a correct version.
Obviously if you're creating your own library or a mod you'd vary these steps, but probably know what you're doing in that case anyways.
Workaround without custom script:
If
And
Conditions
#PARAM(value) >= #PARAM(min)#PARAM(value) <= #PARAM(max)@Thalassicus: Go
Thanks, this bug wasted about 20 minutes of my time. Good to know.
@Hegemuffin:
Sorry to necro bump, but does this bug still exist?