I'd absolutely LOVE a simple little addition for commands to really refine how datapacks work. Currently we have "and" for selectors, and "not" in the form of "!" in selectors and "unless" in the execute subcommands, we even have a form of "then/else" (if x, then y, else z) in datapacks which are triggered as a separate mcfunction if the conditions are met. It'd be a ground-breaking development in how datapacks work if we had "or" as a kind of "competing logic"; "or" would be used for when you want to apply the same changes to "and/or" scenarios, and "xor" would be possible like in the following:
AND function: execute as @e[scores={a=1,b=1}] run...
OR function: execute as @e[scores={a=1},scores={b=1}] run...
XOR function: execute as @e[scores={a=1,b=!1},scores={a=!1,b=1}] run...
The OR function would target entity A or entity B or an entity with both (entity AB), and the XOR function would target *only* entity A and *only* entity B, but never entity AB. The changes necessary wouldn't even be that much, it'd simply be a matter of Minecraft having two options to choose from within one selector argument, and that would only require allowing contradictory arguments to resolve.
Please sign in to leave a comment.
0 Comments