sciwhiz12

Are you creating your blocks in static fields in your `ModBlocks` class?

I assume you're asking for 1.15.2+ versions, since 1.12 is unsupported. The only installer for Forge now is in Java, so the installer download is a JAR file. If you can't doubleclick to start the installer, install Java (see AdoptOpenJDK), or if you have it already, download and run Jarfix.

I have confirmed this issue, and have filed a bug report on the issues tracker: #7187.

1.13 is no longer supported on this forum. Please update to a modern version of Minecraft (1.15.2 and above) to receive support.

That is referring to the texture under `assets/tutorialmod/textures/item/example_item.png`. Your assets/textures folder has an `s` in `items`, rename it to be just `item`.

What does your model JSON for example_item contain? Post it.

Just adding onto that, if you put your modid into an @ObjectHolder above your class, then any `public static final` fields will be auto-injected with the object according to their fields' name. Again, I refer you to the documentation on this, as it has examples.

Although DCEVM and JRebel do work for most Java applications, there may be difficulties with using them for Minecraft modding development. You are basically on your own when trying to use these, as they may introduce subtle differences which may throw off how Forge and FML works. The only officially supported Java version for Minecraft and Forge is Java 8. Any higher is not officially supported by either Mojang or the Forge team. Though they may run on higher versions, support and help will not be given unless issues can be reproduced with Java 8 (OpenJDK 8 HotSpot, for example, is a supported JVM). I can only suggest that you stick with the built-in and limited hotswapping capabilities of the JVM, since anything else is outside support if they cause issues.

In the future, please use the code blocks (the `<>` in the editor) when pasting code. You are missing the colon between the modid and item name: "tutorialmod:example_item". That isn't true for annotations on fields; you explicitly need to specify the registry path and, as there is no @ObjectHolder annotation on the class, also the modid/namespace has to be specified. It's all written in the documentation. (see the last example in UnannotatedHolder)

All versions below 1.15.2 are not supported on this forum. Please update to a modern version of Minecraft to receive support.

1.12 is not supported on this forum. Please update to a modern version of Minecraft to receive support.

1.8 is not supported on this forum. Please update to a modern version of Minecraft to receive support.

Use `ProjectileEntity#func_234616_v_`; it is nullable, if there's no shooter (`AbstractArrowEntity` extends `ProjectileEntity`).

Does your assets/<modid> folder have the capitalized namespace?

1.12 is not supported on this forum. Please update to a modern version of Minecraft to receive support.

You put a `@ObjectHolder` annotation on `ItemInit.example_item` without specifying a modid in either the annotation on the field or on the class (through @Mod or @ObjectHolder). See the documentation on @ObjectHolder for its rules and examples. (ignore the 1.14.x version, it is the same up to 1.16.+)

First, give us your Minecraft and Forge version. Second, give the debug.log and at least a brief description of the crash. Third, you're passing in a `null` to the `EndermanEntity` constructor. That's probably what's causing the crash, but provide more details. Fourth, your whole spawning code from the EndermanEntity constructor up to the world.addEntity should be surrounded by the !isRemote check.

1.12 is not supported on this forum. Please update to a modern version of Minecraft to receive support.

As in, go to the modpack folder, under the logs folder, there should be a debug.log. Post that file. (Your OS may have the extension hidden; it will look like `debug` without any extension in that case)

Your issue with beacon payments are because the `isBeaconPayment` method was removed. Add your item to the `minecraft:beacon_payment_items` item tag for it to work. (reference: PR that removed the method) I don't know much about Gradle and ForgeGradle to help you, though. Try redowloading the latest MDK, and see if a fresh unmodified environment will cause the issue. If that works, copy over your files and resources, and use that environment.

1.12 is not and will not be supported on this forum. Please update to a modern version of Minecraft to receive support.

1.8 is not supported on this forum. Please update to a modern version of Minecraft to receive support.

The configs for the "Valhelsia Structures" are somehow unreadable, possibly due to corruption. Please delete their config files. (They will normally have the modid in their config name: "valhelsiastructures-<client/server/common>.json")

What mods do you have installed? Did it work correctly in the past? If so, what did you do (added/updated mods, etc.) before it started not responding? Also, please post your debug.log.

This seems like an issue with the modpack, not with Forge. Please bring this issue to the modpack authors.