• Recently Browsing

    No registered users viewing this page.

  • Posts

    • In fact I do have a backup of my items I will uncorrupt the word 
    • I'm on mac and when i install forge 1.12.2 and run the game it crashes and says the following:  The game crashed whilst initializing game Error: java.lang.VerifyError: Bad type on operand stack   I havent put any mods yet, but here's the log:    ---- Minecraft Crash Report ---- WARNING: coremods are present: Contact their authors BEFORE contacting forge // Quite honestly, I wouldn't worry myself about that. Time: 12/9/19 2:37 AM Description: Initializing game java.lang.VerifyError: Bad type on operand stack Exception Details:   Location:     Config.checkGlError(Ljava/lang/String;)V @109: invokevirtual   Reason:     Type 'net/minecraft/network/play/server/SPacketResourcePackSend' (current frame, stack[1]) is not assignable to 'net/minecraft/network/play/server/SPacketPlaceGhostRecipe'   Current Frame:     bci: @109     flags: { }     locals: { 'java/lang/String', integer, 'java/lang/String', 'java/lang/String', 'java/lang/String' }     stack: { 'cwr', 'net/minecraft/network/play/server/SPacketResourcePackSend' }   Bytecode:     0x0000000: b804 6e3c 1b99 006b 1bb8 0474 9900 641b     0x0000010: b804 774d 1304 7906 bd00 0459 031b b804     0x0000020: 7c53 5904 2c53 5905 2a53 b804 804e 2db8     0x0000030: 0481 b804 8499 003b 1304 8614 0487 b804     0x0000040: 8e99 002f 1304 9005 bd00 0459 031b b804     0x0000050: 7c53 5904 2c53 b804 943a 04b2 02d3 b404     0x0000060: 97b6 049c bb04 9e59 1904 b704 9fb6 04a4     0x0000070: b1                                        Stackmap Table:     append_frame(@112,Integer)     at java.lang.Class.getDeclaredFields0(Native Method)     at java.lang.Class.privateGetDeclaredFields(Class.java:2583)     at java.lang.Class.getField0(Class.java:2975)     at java.lang.Class.getField(Class.java:1701)     at net.minecraftforge.fml.client.FMLClientHandler.detectOptifine(FMLClientHandler.java:293)     at net.minecraftforge.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:216)     at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:467)     at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:378)     at net.minecraft.client.main.Main.main(SourceFile:123)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke(Method.java:498)     at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)     at net.minecraft.launchwrapper.Launch.main(Launch.java:28) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Client thread Stacktrace:     at java.lang.Class.getDeclaredFields0(Native Method)     at java.lang.Class.privateGetDeclaredFields(Class.java:2583)     at java.lang.Class.getField0(Class.java:2975)     at java.lang.Class.getField(Class.java:1701)     at net.minecraftforge.fml.client.FMLClientHandler.detectOptifine(FMLClientHandler.java:293)     at net.minecraftforge.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:216)     at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:467) -- Initialization -- Details: Stacktrace:     at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:378)     at net.minecraft.client.main.Main.main(SourceFile:123)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke(Method.java:498)     at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)     at net.minecraft.launchwrapper.Launch.main(Launch.java:28) -- System Details -- Details:     Minecraft Version: 1.12.2     Operating System: Mac OS X (x86_64) version 10.15.1     Java Version: 1.8.0_74, Oracle Corporation     Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation     Memory: 532798200 bytes (508 MB) / 872415232 bytes (832 MB) up to 2147483648 bytes (2048 MB)     JVM Flags: 7 total; -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M     IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0     FML:      Loaded coremods (and transformers):      Launched Version: 1.12.2-forge1.12.2-14.23.5.2847     LWJGL: 2.9.2     OpenGL: Intel HD Graphics 4000 OpenGL Engine GL version 2.1 INTEL-14.2.16, Intel Inc.     GL Caps: Using GL 1.3 multitexturing. Using GL 1.3 texture combiners. Using framebuffer objects because ARB_framebuffer_object 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 'fml,forge'     Type: Client (map_client.txt)     Resource Packs: vanilla, programer_art, file/QualityArmoryV2.0.0.zip     Current Language: ~~ERROR~~ NullPointerException: null     Profiler Position: N/A (disabled)     CPU: 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
    • Based on knowing for sure it was a ForgeGradle bug, I was able to binary-search for a working version.   Changing the ForgeGrade version in the classpath dependencies at the top of the build.gradle file from '3.+' to '3.0.145' makes it work again, in 1.13.2 and 1.14.3 (and presumably 1.14.2). This is the last version that works, 3.0.146 is the Maven version that first includes the bug.
    • You could probably just remove your render() override entirely and the problem may fix itself; you don't seem to be doing anything special and you properly set your model objects as children of the parent's objects, so the parent model can just handle everything on its own. If you don't want to get rid of it, just remove your individual render calls for your objects and call the method's super. Admittedly though, it's been a while since I've worked with entity models.
  • Topics

  • Who's Online (See full list)