I have an error at an area of my code that I can't figure out at all. I've been looking at this guide (http://mcforge.readthedocs.io/en/latest/concepts/registries/) and read it a few times over but can't wrap my head over how to fix this code problem in ModItems.java

Code:https://pastebin.com/YRDDxP4v

When hovering over text: The method register(K) from the type GameRegistry is not visible

 

 

MC version modding to:1.12

Edited June 28, 20178 yr by Dr_Blockenstein
Need to show I'm new to modding.

You should use events to register instead of GameRegistry.register(...).

Don't use the ModelMesher, use the ModelLoader in PreInit instead. 

Also stop with the substring nonsense. Unlocalized names have nothing to do with resources. You should be using getRegistryName instead. 

Edited June 28, 20178 yr by Draco18s

@Draco18s it is best to use ModelRegistryEvent for it because in 1.12 the RegistryEvent is now fired after preinit

1 hour ago, loordgek said:

@Draco18s it is best to use ModelRegistryEvent for it because in 1.12 the RegistryEvent is now fired after preinit

Yes, but using the ModelMesher is still the worst option.

Have the same problem how do I go about fixing this?

In code preferably

Edited July 1, 20178 yr by Kitsune_Ultima

30 minutes ago, Kitsune_Ultima said:

Have the same problem how do I go about fixing this?

In code preferably

 

Did you read the thread?

 

You need to use registry events.

Quote

Did you read the thread?

 

You need to use registry events.

 

I did, but the docs don't tell me where to put the code (or at least is very vague about it) as in which file to put it in and where to put it in said file

Edited July 1, 20178 yr by Kitsune_Ultima

Create a new class.

Annotate this new class with @EventBusSubscriber

Create two public static void methods with Register<Block> and Register<Item> parameters respectively.

Either manually call event.registry::registerAll(), adding all blocks inside of the method call, or if you have a collection of blocks/items, for that collection call forEach(event.registry::register)

 

Under Init?

Edited July 2, 20178 yr by Kitsune_Ultima

Package is irrelevant and only for your own convenience.

On 7/1/2017 at 9:37 AM, Matryoshika said:

Create a new class.

Annotate this new class with @EventBusSubscriber

Create two public static void methods with Register<Block> and Register<Item> parameters respectively.

Either manually call event.registry::registerAll(), adding all blocks inside of the method call, or if you have a collection of blocks/items, for that collection call forEach(event.registry::register)

 

Like This? vvvvvvvvvvvvvvvv

1. You need to put @EventBusSubscriber above the public class Register
2. The methods (registerBlocks & registerItems) need to be static
3. You still need to have reference points for your blocks and items
   1. Create a static field in the Register class called OBSIDIAN_INGOT or similar.
   2. Inside the registerAll method, make OBSIDIAN_INGOT = new ItemObsidianIngot(). This way you can use your items in code by calling Register.OBSIDIAN_INGOT.

The @EventBusSubscriber annotation makes sure that Forge knows that this class contains methods that rely on events. You have to use the annotation because these events are fired before preInit.

 

Edited July 2, 20178 yr by Matryoshika

1 hour ago, Matryoshika said:

1. Create a static field in the Register class called OBSIDIAN_INGOT or similar.

Or somewhere, at least.

1 hour ago, Matryoshika said:

1. You need to put @EventBusSubscriber above the public class Register
2. The methods (registerBlocks & registerItems) need to be static
3. You still need to have reference points for your blocks and items
   1. Create a static field in the Register class called OBSIDIAN_INGOT or similar.
   2. Inside the registerAll method, make OBSIDIAN_INGOT = new ItemObsidianIngot(). This way you can use your items in code by calling Register.OBSIDIAN_INGOT.

The @EventBusSubscriber annotation makes sure that Forge knows that this class contains methods that rely on events. You have to use the annotation because these events are fired before preInit.

 

 

33 minutes ago, Draco18s said:

Or somewhere, at least.

Thank you both, this makes so much more sense then what the docs say.