#Help. please
1 messages · Page 1 of 1 (latest)
<@&1201956957406109788>
💬 While you wait, take this time to provide more context and details.
🙇 After a while, hit the Summon Helpers button to ping the helper team. They'll be happy to help you
✅ Once your question has been resolved (or you no longer need it), please click Resolve Question or run /resolve
Don't forget to close or resolve your old questions once you're done with them. It makes our lives much easier! :D
Open question: #1247810403434758194
All item syntax was recently changed (1.20.5 and newer) that’s why your commands don’t work
Also, 2 things
The logs are where Minecraft displays errors when something goes wrong and can thus help you gain information about why something isn't working for you!
To open the logs:
- Enable logs in the Minecraft Launcher
- Start your game (or restart it if you already have an open instance)
- Enjoy spotting errors getting much easier!
Have the logs open and keep and eye on it, it will show you where you’ve messed up
The exact file and line where the error is, it’s very powerful and often times it will exactly tell you where the error is
- check all your commands ingame, the game syntax highlighting and everything is the only thing 100% guaranteed to be correct for your specific version and it is very good
Also, if you do anything with nbt, you can use /data get … to check the exact structure of your nbt, no need to copy it from somewhere online, you can check these thing in the game itself
And again, you know it’s 100% accurate then
If you want to see how stuffs done before you can/want to replicate it yourself, you can also just download a data pack for that specific version you are in and look through the files, data packs are inherently open source
First of all there shouldn't be a space. The VSCode extension hadn't been updated yet so it doesn't know about the new syntax
Secondly, custom_data={1} is not valid syntax. It's a compound which means it needs to have key-value pairs
Why did you revert all the changes?
As has been said, that won't work because the syntax has been updated
Try copying and pasting the command into the chat, and see what happens