Hello there,

 

I've been restarting to learn mod development, and after diving into the horrendous forge documentation, I started searching for tutorials and mods hosted on git hosters, to try to create a simple mod.

 

The thing is: I have an Item, a .json model stored under my {modid}/models/item/ and a .png texture file, under {modid}/textures/items/

 

When loading the mod, I get this error.

 

This is my folder structure: folder structure.txt

 

And my sourcecode (including gradle files) is available here

 

Note that due to some weird bug, I can't paste anything on this website. That includes sourcecode, so I must use external code hosting solutions.

I believe item/block model registration needs to be done during preinit, you are doing it during init.

1 hour ago, Leviathan143 said:

I believe item/block model registration needs to be done during preinit, you are doing it during init.

I forgot about that, I changed that, but now I get this item rendering, which I don't understand.

While fixing, I also changed the registerRender class to use the registryName of the item instead of a fixed name (which was for testing).

 

I now get this item rendering:

In-game screenshot of item rendering.

Edited May 1, 20178 yr by Artemix
adding screenshot

 

2 minutes ago, Artemix said:

I forgot about that, I changed that, but now I get this item rendering, which I don't understand.

While fixing, I also changed the registerRender class to use the registryName of the item instead of a fixed name (which was for testing).

 

I now get this item rendering:

In-game screenshot of item rendering.

Post the latest console log, it should give the error.

The error log is here.

 

It says that the path "metricsmod:models/item/tape_meter.json" can't be found, which I don't understand, as that's pretty much the only way to load it. That, or I missed something.

 

The json model file stored under assets/metricsmod/models/item/tape_meter.json contains

Quote

{
    "parent": "item/generated",
    "textures": {
        "layer0": "metricsmod:items/tape_meter"
    }
}

 

Edited May 2, 20178 yr by Artemix
adding json

Would you show a screenshot of the path and file as see in Windows File Explorer?

(or equivalent on your system)

Here's a screenshot from the file explorer/terminal, with full path.

Here's a `tree` view starting from the src/main folder:

Quote

> $ tree                                [±master ●●]
.
├── java
│   └── xyz
│       └── artemix
│           └── mc
│               └── metrics
│                   ├── ClientProxy.java
│                   ├── CommonProxy.java
│                   ├── Constants.java
│                   ├── init
│                   │   └── ItemHandler.java
│                   ├── items
│                   │   └── ItemTapeMeter.java
│                   ├── MetricsMod.java
│                   └── MetricsModTab.java
└── resources
    ├── assets
    │   └── metricsmod
    │       ├── blockstates
    │       ├── lang
    │       │   └── en_US.lang
    │       ├── models
    │       │   ├── block
    │       │   └── item
    │       │       └── tape_meter.json
    │       └── textures
    │           ├── block
    │           └── items
    │               ├── tape_meter.png
    │               └── tape_meter.xcf
    └── mcmod.info

18 directories, 12 files

 

 

Edited May 2, 20178 yr by Artemix
adding screenshot

Any thoughts ?

Some issues I had was that I first created the files with a uppercase name, and windows didn't recognize that there was a change even though it displayed it.
Might be the same issue for you, even though it looks like you are using linux and I am not sure if thats an issue in it too.

Is the file visible in Eclipse's Package Explorer? If it isn't, try refreshing the folder or the project.

 

In my experience, Eclipse seems to cache the project. If you edit a file in Eclipse, the cache is updated and you don't notice anything. If you edit or create a file in the project folder with an external tool, the cache is not updated and the cached version of the file is used when running or debugging, leading to unexpected results.