Started by
radscientist44
on
Topic category: Help with Minecraft modding (Java Edition)
Hello,
I need help with loot table commands. I've tried YouTube videos and other posts on the forum, but every time I try the command out it is either is invalid or in the chat it says changed block data of cords, but every time the chest is empty.And just to make sure its incorrect ,I press control+mmb and each time get no chest. Maybe I'm doing it wrong, but I need help. I have tried for three days already.
I tried the command and when I put in the mod name or loot table name it turned red, but if I erased the loot table name it gave me a plain chest,. I'll send you a picture of my command, it will be sent in 2 pictures because command does not fit on one screen
/Users/SLF/Desktop/Screenshot 2025-02-07 at 1.33.08 PM.png
sorry, I accidentally sent the file name not the photo.
sorry, I don't know how to import photos from a file to the form, sorry if I'm being annoying.
No, you're not.
Man, I'm really sorry that this isnt working.
press "t" in minecraft as in the "t" button on the keyboard to bring up the chat
The command should not be so long that it doesnt fit on the screen, i think
Hmm...
Let me try it myself and give you the results
Ah, shoot. My MCreator is currently... ah, really glitchy.
Learning moment: dont intall 14 different MCreator plugins at the same time... lol
I'm really sorry, please wait until tomorrow so that i can manually test and figure out your problem.
Sooo sorry for the wait!!!
thanks for being so helpful, ill retry all the commands to make sure I'm really wrong
Yeah, the commands I posted should be correct. I really don’t know what could be the issue, I’m sorry. What Minecraft version are you on? Omg, that could be it! 1.20 up to 1.21 does not work with loot tables, only Neoforge 1.21.1.
That might be the problem.
In between 1.20 and 1.21 the stopped loot tables to make way for the new way for it.
This might be it, and there is no solvable solution, I am so sorry. :(
my mod is Neoforge 1.21 , so I'm probably writing the command wrong