4
Help pls
Im new to mc coding and coding overall and im following a tutroial for data packs, for the first example he does in the tutorial its a tell raw command i write it exacly how it is there and it wont work the line is tellraw @a {"text": "my code is load", "color": "0000FF"} in the tutorial the curly bracket highlights and mine doesnt yes i have extentions for data packs installed in my visual studio code but it still doesnt workpls help
5
If it doesnt highlight in code, that might mean your extension is old or not properly installed.
The command seems to work. What tutorial are you using?
In addition to what packdotmcmeta has already suggested, in what ways are you attempting to run the function? Are you sure that the functions are located in:
What command are you using to run the function if any at all?
If you are trying to run them via a tick/load tag, are you sure those tags are set up correctly and located in:
One last useful tip that can help with debugging: In the minecraft launchers settings tab, you can enable the option "Open output log when Minecraft: Java Edition starts".
The reason the output log is useful is that it will tell you in red if one of your functions(or anything else) aren't loading, and tell you exactly where the problem is. I recommend unchecking the option that says "info" to reduce spam. It's ok if your output log has differing warnings/errors, although it's ideal to have as few as possible. I'm playing on the latest snapshot, so that's why so many have appeared.
Also if you do get a red warning for your datapack, don't be intimidated by it as most of the information is essentially useless for our purposes.
Notice how I only focused on the top part of the error and nothing else. That is because that's where the useful information is. Because of what I gathered from that error, I can see that the problem is inside my main.mcfunction file, on line 23, at position 0. When looking at pretty much that exact spot, I could see that the problem is nothing more but an extra "a" character.
However, this doesn't mean you shouldn't check to see if there are more errors, as there very well could be more that need to be tackled. Just make sure to scroll through each error given, make sure it relates to your datapack, and use the button on the top right "Clear all logs" if your output logs are getting too cluttered. One last thing worth mentioning is that the /reload command will make any datapack errors appear if there are any left.
I hope this information is helpful! :)
"PACKNAME"/data/"NAMESPACE"/functionsWhat command are you using to run the function if any at all?
If you are trying to run them via a tick/load tag, are you sure those tags are set up correctly and located in:
"PACKNAME"/data/minecraft/tags/functionsOne last useful tip that can help with debugging: In the minecraft launchers settings tab, you can enable the option "Open output log when Minecraft: Java Edition starts".
Picture showing the process of enabling the output log.
The reason the output log is useful is that it will tell you in red if one of your functions(or anything else) aren't loading, and tell you exactly where the problem is. I recommend unchecking the option that says "info" to reduce spam. It's ok if your output log has differing warnings/errors, although it's ideal to have as few as possible. I'm playing on the latest snapshot, so that's why so many have appeared.
Picture showcasing the minecraft output log, and info toggle location.
Also if you do get a red warning for your datapack, don't be intimidated by it as most of the information is essentially useless for our purposes.
One more picture highlighting the important parts of an example error.
Notice how I only focused on the top part of the error and nothing else. That is because that's where the useful information is. Because of what I gathered from that error, I can see that the problem is inside my main.mcfunction file, on line 23, at position 0. When looking at pretty much that exact spot, I could see that the problem is nothing more but an extra "a" character.
My "main.mcfunction"
However, this doesn't mean you shouldn't check to see if there are more errors, as there very well could be more that need to be tackled. Just make sure to scroll through each error given, make sure it relates to your datapack, and use the button on the top right "Clear all logs" if your output logs are getting too cluttered. One last thing worth mentioning is that the /reload command will make any datapack errors appear if there are any left.
I hope this information is helpful! :)
Try typing /reload and /datapack list to see if you data pack shows up. The pinned comment on the tutorial seems to have some useful debugging information.
