[Bug] Possible bug with datapack
Avventis90005 opened this issue ยท 5 comments
Good time of day.
To begin with, I would like to apologize for my not the best knowledge of english, but I will still try to explain everything in a way that is clear.
There was a need to change some parameters of the weapon so that it would correspond to the current modpack.
In the Crayfish Gun Mod there was a possibility to change weapons stats through a datapack and it worked.
I assumed that it should work with nzgmaddon through the same way, but I was faced with the fact that the data from the datapack does not affect anything.
The datapack itself is located at: datapacks<datapack_name>\data\nzgmaddon\guns.
Inside this datapack there is already a segment for CGM, which works (and that means, that datapack is read by minecraft).
There is also a part for nzgmaddon. And it doesn't work. Perhaps I'm doing something wrong?
If everything works the same as in CGM, it means that the datapack is unreadable for some reason? Perhaps there is a mistake in the location address or something else? Is it bug?
I'm using minecraft 1.19.2 and this version of nzgmaddon: nzgExpansion-1.3.1-1.19.2
Forge 43.2.13
The datapack location and folder structure look fine to me, as does the sniper_rifle.json file. This might be a datapack priority issue. Basically, if a datapack is added before another mod is installed, the mod's own data will load after the datapack and take higher priority. Disabling and re-enabling the datapack again usually fixes this, as it moves the datapack back to the bottom of the load order. (Hence, it loads last)
Let me know if this helped any!
- You need to run
/datapack disable <name>
, followed by/datapack enable <name>
to move the datapack to the bottom of the load order. Try running those and see if anything changes. - Those are the correct .json files, so you're good on that end.