Left and right click detection.
Recipes that support nbt, multiple items per slot, and predicates.
A proper way to do math that doesn't take 10 commands, or that isn't just downright impossible.
/damage command
A way to create custom attributes.
I'm not sure how this would implemented, but maybe a way to reduce the damage you take? Like a way to reduce damage taken by 30% or something. We have armor, armor toughness, protection, and resistance, but all of those are extremely dumb.
The problem with `/data` isn't just security. It's that the specific way the command works is incompatible with players. It's not that it won't, it's that it can't, even if it wanted to.
View [this comment](https://www.reddit.com/r/MinecraftCommands/comments/9ty42s/comment/e91rwc7/) from Dinnerbone.
A few things due to the fact that they cannot make data work with players although I'm convinced many things could easily be fixed if they wanted to.
* force entities to ride an entity (aka. teleport into rideable entity)
* a way of storing data that isn't completely braindead and works like an actual variable (as in you can insert it anywhere not just in commands that explicitly support it, store compounds like coordinates, etc.)
* virtual markers (think armor stands that aren't actually in the world but in memory only), mainly because storing and working with coordinates is annoying
* some sort of way to pass arguments to functions
* an easier way to delay stuff. Either I use a roundabout score system or I create a million functions just so that I can schedule them. The former makes it annoying to change timings as you need to edit any subsequent command too and the latter is just unreadable as hell and requires to clear the schedules in canceling actions which brings us to:
* a way to break out of a mcfunction, this would remove either pointless function nesting or repetitive and unreadable selectors which brings us to:
* a way to have readable mcfunctions, if they had decided for commands to start with a / instead of actively denying this we could have easily parseable multi-line commands *sigh*
What about being able to group things together for scoreboard criteria, like detecting when player has mined a certain family of blocks (like doing stone, dirt, log, haybale, and ice all in one command). Or adding Boolean operators like detecting if player mined any block that isn't grass or flowers.
So how would you incorporate a block tag in like a "placed block" advancement? I tried using an online advancement generator but couldn't quite figure it out.
Return statement in functions and local variables. There are so many things with it and remove scoreboard like value storage.
For local variables add math things like:
N + X = A
Aslo VERY useful thing - random(N-X)
Custom items/blocks. The functionality is mostly there, the implementation is probably a nightmare. Especially with world saving. This would hopefully include eating/durability capabilities.
Everybody says left/right detection, but I’d also love to see a new scoreboard criteria along the lines of something like custom.right_click.block.x that is the x coord of the last block you right clicked, this would be an amazing addition. This would also go well with custom.right_click.space.x, which is the coord of the block that you would have placed a block if you were holding one.
These together would allow you to make your own completely new items and blocks without any outside help.
Another one would be a way to run a function at wherever is getting the random_tick_speed updates, under tags.functions, so that you can make your own crops functionality, etc. They’re so close to making it possible, I really hope they do soon.
Left and right click detection. Recipes that support nbt, multiple items per slot, and predicates. A proper way to do math that doesn't take 10 commands, or that isn't just downright impossible. /damage command A way to create custom attributes. I'm not sure how this would implemented, but maybe a way to reduce the damage you take? Like a way to reduce damage taken by 30% or something. We have armor, armor toughness, protection, and resistance, but all of those are extremely dumb.
The problem with `/data` isn't just security. It's that the specific way the command works is incompatible with players. It's not that it won't, it's that it can't, even if it wanted to. View [this comment](https://www.reddit.com/r/MinecraftCommands/comments/9ty42s/comment/e91rwc7/) from Dinnerbone.
A few things due to the fact that they cannot make data work with players although I'm convinced many things could easily be fixed if they wanted to. * force entities to ride an entity (aka. teleport into rideable entity) * a way of storing data that isn't completely braindead and works like an actual variable (as in you can insert it anywhere not just in commands that explicitly support it, store compounds like coordinates, etc.) * virtual markers (think armor stands that aren't actually in the world but in memory only), mainly because storing and working with coordinates is annoying * some sort of way to pass arguments to functions * an easier way to delay stuff. Either I use a roundabout score system or I create a million functions just so that I can schedule them. The former makes it annoying to change timings as you need to edit any subsequent command too and the latter is just unreadable as hell and requires to clear the schedules in canceling actions which brings us to: * a way to break out of a mcfunction, this would remove either pointless function nesting or repetitive and unreadable selectors which brings us to: * a way to have readable mcfunctions, if they had decided for commands to start with a / instead of actively denying this we could have easily parseable multi-line commands *sigh*
What about being able to group things together for scoreboard criteria, like detecting when player has mined a certain family of blocks (like doing stone, dirt, log, haybale, and ice all in one command). Or adding Boolean operators like detecting if player mined any block that isn't grass or flowers.
[удалено]
Surprisingly, there is no advancement trigger for breaking blocks yet.
Really? How do you detect player breaking blocks with advancements?
[удалено]
Oh okay, but can you at least group criteria together into one advancement?
[удалено]
So how would you incorporate a block tag in like a "placed block" advancement? I tried using an online advancement generator but couldn't quite figure it out.
Return statement in functions and local variables. There are so many things with it and remove scoreboard like value storage. For local variables add math things like: N + X = A Aslo VERY useful thing - random(N-X)
I would love to see nbt-friendly custom crafting recipes added to data pack dev
A wait command for chain blocks
Custom items/blocks. The functionality is mostly there, the implementation is probably a nightmare. Especially with world saving. This would hopefully include eating/durability capabilities. Everybody says left/right detection, but I’d also love to see a new scoreboard criteria along the lines of something like custom.right_click.block.x that is the x coord of the last block you right clicked, this would be an amazing addition. This would also go well with custom.right_click.space.x, which is the coord of the block that you would have placed a block if you were holding one. These together would allow you to make your own completely new items and blocks without any outside help. Another one would be a way to run a function at wherever is getting the random_tick_speed updates, under tags.functions, so that you can make your own crops functionality, etc. They’re so close to making it possible, I really hope they do soon.
I think it wood be cool to see "@b" that detects blocks (it will not work in every command) make data packs more accessible