Pretty sutre the katana image belongs in textures/items not models/items

Currently it's not possible to craft items with NBT in a regular crafting table, so we have a few workarounds.

The easiest (and most common) method is by using a knowledge book as the output item - you might've seen it in a lot of packs, when you have recipes that require you to click on the knowledge book to get the item.
For that you need:
- an advancement to detect when the recipe is unlocked
- a function that resets the advancement and recipe
- a loot table to give the item (can also be a simple /give in the previous function)
Then, just put the function and loot table as rewards for the achievement.
The pros - you can craft the item directly in the regular crafting table, it works seamlessly and is quite easy to implement. The cons though - you can't see the item you're crafting, the recipe will never be in the recipe book, and a popup will appear every time.

The oldest method is floor crafting, but it's really not recommended as it can get very laggy if not implemented properly.

The most advanced method is making a custom crafter. It's very technical so I won't go in the details, but it's by far the most flexible method since you can make custom UIs, new types of crafting - nearly anything you want. Thankfully there are initiatives to make the creation of a custom crafter easier - I'd recommend checking out SmithedCrafter, a datapack that adds a fully functionnal crafter to which you can add your own recipes very easily !

If you need help with any of these - here are the Minecraft Commands and the Datapack Center discord server, they have a lot of great datapackers that will be able to help you !

By custom crafting recipes do you mean using the official ones (for the vanilla crafting table)?
If you want to rename and change the custommodeldata of your output items, you cannot do so without a custom crafter or floor crafting

Well, if I understood your comment properly you're only half-right.
Datapacks need a custom namespace and resourcepacks don't, but it's true organizing them in the same way as datapack can be cleaner.

There is an effort to avoid CMD ID collision and general datapack compatibility, thanks to a website created by Boomber, where each datapacker can give themselves a 4-digits ID to use in front of all their models. It allows manual merging of packs (creating a single resourcepack with all the overrides) without CMD ID collisions.

But about compatibility, the problem has already been studied and what you propose doesn't work. From what I gather, either you suggest putting things in namespaces so they can merge easily, either you suggest we use a toplevel pack with all possible overrides ?
Well, for the first solution, model overrides don't merge. If you have one pack that has overrides in the stick model, other packs that also have overrides in the stick model will take priority in the vertical order.
For the second idea, it's not bad but you still need to specify a path to the custom model in the override. So, it's just pushing the problem back.
... if your idea was something else, sorry but it wouldn't work either. It's been bugging the entire datapack community for a long time, and it's not easy to solve.

Try raising the second value in each "translation" field !
The 3 numbers are an array for 3D translation, so changing the 2nd value will change the Y position of the model.

Nope, this is only for Java Edition resource packs (1.14+)

Did you put both "hammer.json" and "iron_axe.json" under /assets/minecraft/models/item/ ?

Update I have done something that has now made it a black & purple box



Please help me whoever is reading this asap



{
"parent": "item/generated",
"textures": {
"layer0": "item/iron_sword"
},

"overrides": [
{"predicate": {"custom_model_data":1}, "model": "item/excalibur"}
]
}

Nvm, figured it out from looking at the vanilla data.

{
"parent": "item/generated",
"textures": {
"layer0": "block/sunflower_front"
},
"overrides": [
{ "predicate": { "custom_model_data": 220}, "model":"item/coin/coin-bronze"},
{ "predicate": { "custom_model_data": 222}, "model":"item/coin/coin-gold"},
{ "predicate": { "custom_model_data": 224}, "model":"item/coin/goin-platinum"},
{ "predicate": { "custom_model_data": 226}, "model":"item/coin/coin-silver"}
]
}

What's the code in custom_sword.json?

Hello there! I've been playing around with custom models and all that, and from what I can tell, you need to have any custom models in a subfolder of the models folder like this:
assets/minecraft/models/item/customHope this helped!

I think you can do it in few command blocks:

give yourself a disc with CustomModelData tag linked to the texture you want, but also an Array tag or a custom name

I think jukebox is like a container (like a chest), so in its data you should find the item it contains, precisely in its tag RecordItem.

You just have to make an execute command to test if jukebox contains your specific disc. Stopsound for the music the disc will start automatically when u put it in the jukebox and then playsound of the music u want. You can add some custom sounds in your resourcepack.
I didnt test yet, i m pretty sure it will work

No, it's not possible. You would need the help of a datapack for that, detecting when a disc with a custom model is used (in minecraft, the music that discs play is hardcoded).

But you can still add custom models for music discs though, even if it's not gonna change the music they play.

Did you pass it through a json validator to see if there are any json mistakes ? I use this one (link).

Be careful though, you can't craft items with nbt. That's a big limitations datapacks have to get around. So in short, no you can't combine it with regular crafting. You can add custom recipes but you'll have to use workarounds to add nbt to these items.

to use "item/generated", you souldn't have any model data, just textures. They should be named layer0 (and layer1 in the case of some items like leather armor, eggs and potions). So in the end, a model using "item/generated" should look like this:
{
"parent": "item/generated",
"textures": {
"layer0": "path/to/texture",
"layer1": "path/to/other/texture"
}
}

Note that usually, in the few models that need 2 layers, layer1 displays on top of layer0.

It's not possible, you would have to use Custom Model Data for that.