bigbang
-
Posts
8 -
Joined
-
Last visited
Posts posted by bigbang
-
-
genEclipseRuns didn't helped, still having the same error. What else can I check?
I launched this command, there's output:
PS D:\Test> .\gradlew genEclipseRuns Picked up _JAVA_OPTIONS: -Xmx8G To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/4.9/userguide/gradle_daemon.html. Daemon will be stopped at the end of the build stopping after processing > Configure project : New Dep: net.minecraftforge:forge:1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3 Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/4.9/userguide/command_line_interface.html#sec:command_line_warnings BUILD SUCCESSFUL in 25s 5 actionable tasks: 3 executed, 2 up-to-date PS D:\Test>
And after that I reopened Eclipse, clicked Run Start (Start - mcp.client configuration) and have the same result:
2019-09-24 12:24:02,106 main WARN Advanced terminal features are not available in this environment [12:24:02] [Client thread/INFO] [minecraft/Minecraft]: Setting user: Player639 [12:24:05] [Client thread/INFO] [minecraft/Minecraft]: LWJGL Version: 3.2.2 build 10 ---- Minecraft Crash Report ---- // Everything's going to plan. No, really, that was supposed to happen. Time: 24.09.19 12:24 Description: Initializing game java.lang.NullPointerException: Initializing game at net.minecraftforge.fml.ModLoader.<init>(ModLoader.java:114) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.ModLoader.get(ModLoader.java:143) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.client.ClientModLoader.lambda$begin$2(ClientModLoader.java:79) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:95) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:79) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraft.client.Minecraft.init(Minecraft.java:453) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraft.client.Minecraft.run(Minecraft.java:365) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraft.client.main.Main.main(SourceFile:155) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at mcp.client.Start.main(Start.java:17) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Client thread Stacktrace: at net.minecraftforge.fml.ModLoader.<init>(ModLoader.java:114) at net.minecraftforge.fml.ModLoader.get(ModLoader.java:143) at net.minecraftforge.fml.client.ClientModLoader.lambda$begin$2(ClientModLoader.java:79) at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:95) at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:79) at net.minecraft.client.Minecraft.init(Minecraft.java:453) -- Initialization -- Details: Stacktrace: at net.minecraft.client.Minecraft.run(Minecraft.java:365) at net.minecraft.client.main.Main.main(SourceFile:155) at mcp.client.Start.main(Start.java:17) -- System Details -- Details: Minecraft Version: 1.14.4 Minecraft Version ID: 1.14.4 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_221, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1116458744 bytes (1064 MB) / 2134376448 bytes (2035 MB) up to 7635730432 bytes (7282 MB) CPUs: 12 JVM Flags: 1 total; -Xmx8G Launched Version: mcp LWJGL: 3.2.2 build 10 OpenGL: GeForce RTX 2060/PCIe/SSE2 GL version 4.6.0 NVIDIA 417.71, NVIDIA Corporation GL Caps: Using GL 1.3 multitexturing. Using GL 1.3 texture combiners. Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported. Shaders are available because OpenGL 2.1 is supported. VBOs are available because OpenGL 1.5 is supported. Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'forge' Type: Client (map_client.txt) Resource Packs: Current Language: ~~ERROR~~ NullPointerException: null CPU: 12x Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz #@!@# Game crashed! Crash report saved to: #@!@# D:\Test\.\crash-reports\crash-2019-09-24_12.24.07-client.txt Picked up _JAVA_OPTIONS: -Xmx8G -
***
SOLVED! Look at posts below to find a quick tutorial how o fix this issue.
***
1. Problem
Starting the project using Run Start crashes the game. When I start the project by using gradlew runClient it works. Another problem is that I need to set an additional enviro variable named "assetDirectory", as a value I used "C:\Users\MyUserName\AppData\Roaming\.minecraft\assets". I did this because it couldn't find asset path under this enviro variable in Start.class:
String assets = System.getenv().containsKey("assetDirectory") ? System.getenv("assetDirectory") : "assets";
2. Repro
Tried on 2 different machines, result is the same. Im using Eclipse. Here's my repro:
- downloaded the most recent Recommended Forge (forge-1.14.4-28.1.0)
- installed Java 8
- gradlew eclipse
- gradlew build
- open eclipse and load project with default Example Mod
- changed nothing in project files, just want a sanity check launch
3. Output
2019-09-24 10:43:43,665 main WARN Advanced terminal features are not available in this environment [10:43:44] [Client thread/INFO] [minecraft/Minecraft]: Setting user: Player825 [10:43:45] [Client thread/INFO] [minecraft/Minecraft]: LWJGL Version: 3.2.2 build 10 ---- Minecraft Crash Report ---- // This doesn't make any sense! Time: 24.09.19 10:43 Description: Initializing game java.lang.NullPointerException: Initializing game at net.minecraftforge.fml.ModLoader.<init>(ModLoader.java:114) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.ModLoader.get(ModLoader.java:143) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.client.ClientModLoader.lambda$begin$2(ClientModLoader.java:79) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:95) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:79) ~[forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraft.client.Minecraft.init(Minecraft.java:453) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraft.client.Minecraft.run(Minecraft.java:365) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at net.minecraft.client.main.Main.main(SourceFile:155) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} at mcp.client.Start.main(Start.java:17) [forge-1.14.4-28.1.0_mapped_snapshot_20190719-1.14.3.jar:?] {} A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Client thread Stacktrace: at net.minecraftforge.fml.ModLoader.<init>(ModLoader.java:114) at net.minecraftforge.fml.ModLoader.get(ModLoader.java:143) at net.minecraftforge.fml.client.ClientModLoader.lambda$begin$2(ClientModLoader.java:79) at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$5(ClientModLoader.java:95) at net.minecraftforge.fml.client.ClientModLoader.begin(ClientModLoader.java:79) at net.minecraft.client.Minecraft.init(Minecraft.java:453) -- Initialization -- Details: Stacktrace: at net.minecraft.client.Minecraft.run(Minecraft.java:365) at net.minecraft.client.main.Main.main(SourceFile:155) at mcp.client.Start.main(Start.java:17) -- System Details -- Details: Minecraft Version: 1.14.4 Minecraft Version ID: 1.14.4 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_221, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 608595104 bytes (580 MB) / 2247098368 bytes (2143 MB) up to 7635730432 bytes (7282 MB) CPUs: 12 JVM Flags: 1 total; -Xmx8G Launched Version: mcp LWJGL: 3.2.2 build 10 OpenGL: GeForce RTX 2060/PCIe/SSE2 GL version 4.6.0 NVIDIA 417.71, NVIDIA Corporation GL Caps: Using GL 1.3 multitexturing. Using GL 1.3 texture combiners. Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported. Shaders are available because OpenGL 2.1 is supported. VBOs are available because OpenGL 1.5 is supported. Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'forge' Type: Client (map_client.txt) Resource Packs: Current Language: ~~ERROR~~ NullPointerException: null CPU: 12x Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz #@!@# Game crashed! Crash report saved to: #@!@# D:\Test\.\crash-reports\crash-2019-09-24_10.43.47-client.txt Picked up _JAVA_OPTIONS: -Xmx8G3. Additional info
I attached debugger file, nulls everywhere in this.
-
Hi
I have a question how can I spawn mobs in all biomes of other dimensions? The only idea that comes to mind is subscribing event hook to InitMapGenEvent and then add my mobs to it's SpawnListEntry for every EventType. Maybe there is a better way of doing this?
-
I found the best solution which is SpecialSpawn event, problem was solved.
-
So LivingSpawnEvent.CheckSpawn, LivingSpawnEvent.SpecialSpawn and EntityJoinWorldEvent should be called only once? I assume that the only exception may be EntityJoinWorldEvent, it seems like this event should be fired also on level load for already extisting entities.
-
************SOLUTION************
The solution is LivingSpawnEvent.SpecialSpawn instead of EntityEvent, so proper event hook for animals spawn should look like this:
@SubscribeEvent(priority = EventPriority.NORMAL) public void onEntitySpawn(SpecialSpawn e) { Entity squid = e.getEntity(); if (squid instanceof EntitySquid) { //do stuff } }
************QUESTION************
public class EventHandler { + + @SubscribeEvent(priority = EventPriority.NORMAL) + public void EntityJoinWorldEvent(EntityEvent e) { + Entity spawnedEntity = e.getEntity(); + if (spawnedEntity instanceof EntitySquid) { + System.out.println(spawnedEntity.getUniqueID()); + } + } }
Hi,
What I want to achieve is replace half of Squids on my custom mob. So everytime Squid is spawned I want to replace it with a chance of 50%. When I subscribed to EntityJoinWorldEvent I noticed that this event is fired multiple times for the same entity. My code is above, nothing too fancy, very simple handler. Here is console output, you can see the same UUID repeat over and over again (i colorcoded the same UUIDs). I expect EntityJoinWorldEvent should be fired once per entity.
Edit:
Maybe I should try onJoinWorldEvent(EntityJoinWorldEvent e) instead of EntityJoinWorldEvent(EntityEvent e), this could be my problem?
Quote[00:41:53] [Server thread/INFO]: [STDOUT]: 2f0b34e7-f396-4ff4-b986-bfb65217d06a - Squid A
[00:41:53] [Server thread/INFO]: [STDOUT]: f9b18086-201d-4986-a342-f356f403eba3 - Squid B
[00:41:53] [Server thread/INFO]: [STDOUT]: 5baaec49-4bf2-4052-99a7-6e087d2eb15a - Squid C
[00:41:53] [Server thread/INFO]: [STDOUT]: e5287093-dbdb-4286-bd5b-e9ab09ff7298 - Squid D
[00:41:53] [Server thread/INFO]: [STDOUT]: 5dca64e1-557a-4860-ad3d-b34d72ad6412 - Squid E
[00:41:53] [Server thread/INFO]: [STDOUT]: 4fc4b076-a626-41d2-9e96-8a88c9fc4796 - Squid F
[00:41:53] [Server thread/INFO]: [STDOUT]: 2f0b34e7-f396-4ff4-b986-bfb65217d06a - Squid A
[00:41:53] [Server thread/INFO]: [STDOUT]: f9b18086-201d-4986-a342-f356f403eba3 - Squid B
[00:41:53] [Server thread/INFO]: [STDOUT]: 5baaec49-4bf2-4052-99a7-6e087d2eb15a - Squid C
[00:41:53] [Server thread/INFO]: [STDOUT]: e5287093-dbdb-4286-bd5b-e9ab09ff7298 - Squid D
[00:41:53] [Server thread/INFO]: [STDOUT]: 5dca64e1-557a-4860-ad3d-b34d72ad6412 - Squid E
[00:41:53] [Server thread/INFO]: [STDOUT]: 4fc4b076-a626-41d2-9e96-8a88c9fc4796 - Squid F
[00:41:53] [Server thread/INFO]: [STDOUT]: 2f0b34e7-f396-4ff4-b986-bfb65217d06a - Squid A
[00:41:53] [Server thread/INFO]: [STDOUT]: f9b18086-201d-4986-a342-f356f403eba3 - Squid B
[00:41:53] [Server thread/INFO]: [STDOUT]: 5baaec49-4bf2-4052-99a7-6e087d2eb15a - Squid C
[00:41:53] [Server thread/INFO]: [STDOUT]: e5287093-dbdb-4286-bd5b-e9ab09ff7298 - Squid D
[00:41:53] [Server thread/INFO]: [STDOUT]: 5dca64e1-557a-4860-ad3d-b34d72ad6412 - Squid E
[00:41:53] [Server thread/INFO]: [STDOUT]: 4fc4b076-a626-41d2-9e96-8a88c9fc4796 - Squid F -
Hi.
I have a problem with loading resources. I defined some resources in my mod *.json files (like a models in blockstates, textures in models and sounds in sounds.json), and during client launch, Forge Loader is looking for these files and cannot find them. Just opened the console output and Forge Loader seems to look for lowercase resource names. For example (pseudocode):
sounds.json { sound [ modID:funnySteveSound ] }Forge Loader is looking for funnystevesound.ogg instead of funnySteveSound.ogg. So if I change the file name to lowercase, then it works just fine. Maybe this is problem on my side (eclipse project config?) but on the same project configs (Java 1.
for Minecraft version 1.10.2 this problem does not exist and Forge Loader is working with cammelcase resource names. I just did copy paste from 1.10.2 project with only minor fixes due to changed variables visibility and changed method parameters.
[SOLVED] Crash at launch ModLoader.java:114 (NullPointerException: Initializing game)
in Modder Support
Posted
@diesieben07
Thanks! That solved my issue. I checked configurations once again and found generated by the task. For some reason this run configuration was not set by default in my case
Here is how to solve this problem if you found this topic with similar issue:
Open Run Configurations
From the Run Configurations expand Java Application and choose your config (runClient for example) and press Run.
After that just by pressing Run it will automatically start the game with selected configuration every time until you change it on something else (like a runServer).