Jump to content

crash


patryx1337

Recommended Posts

:(

---- Minecraft Crash Report ----

WARNING: coremods are present:
  LabyModCoreMod (LabyMod-3.jar)
Contact their authors BEFORE contacting forge

// There are four lights!

Time: 16.09.20 15:50
Description: Rendering entity in world

java.lang.ClassCastException: java.lang.Byte cannot be cast to java.lang.Short
    at net.minecraft.entity.DataWatcher.func_75693_b(DataWatcher.java:91)
    at net.minecraft.entity.monster.EntityEnderman.func_175489_ck(EntityEnderman.java:312)
    at net.minecraft.client.renderer.entity.RenderEnderman.func_76986_a(SourceFile:28)
    at net.minecraft.client.renderer.entity.RenderEnderman.func_76986_a(SourceFile:12)
    at net.minecraft.client.renderer.entity.RenderManager.func_147939_a(RenderManager.java:402)
    at net.labymod.core_implementation.mc18.render.RenderManagerCustom.func_147939_a(RenderManagerCustom.java:120)
    at net.labymod.core_implementation.mc18.render.RenderManagerCustom.func_147936_a(RenderManagerCustom.java:107)
    at net.labymod.core_implementation.mc18.render.RenderManagerCustom.func_147937_a(RenderManagerCustom.java:82)
    at net.minecraft.client.renderer.RenderGlobal.func_180446_a(RenderGlobal.java:870)
    at net.minecraft.client.renderer.EntityRenderer.func_175068_a(EntityRenderer.java:1763)
    at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1580)
    at net.minecraft.client.renderer.EntityRenderer.func_181560_a(EntityRenderer.java:1372)
    at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1051)
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:349)
    at net.minecraft.client.main.Main.main(SourceFile:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    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 --
Stacktrace:
    at net.minecraft.entity.DataWatcher.func_75693_b(DataWatcher.java:91)
    at net.minecraft.entity.monster.EntityEnderman.func_175489_ck(EntityEnderman.java:312)
    at net.minecraft.client.renderer.entity.RenderEnderman.func_76986_a(SourceFile:28)
    at net.minecraft.client.renderer.entity.RenderEnderman.func_76986_a(SourceFile:12)

-- Entity being rendered --
Details:
    Entity Type: Enderman (net.minecraft.entity.monster.EntityEnderman)
    Entity ID: 505250
    Entity Name: Enderman
    Entity's Exact location: -4876,31, 26,00, -4210,25
    Entity's Block location: -4877,00,26,00,-4211,00 - World: (-4877,26,-4211), Chunk: (at 3,1,13 in -305,-264; contains blocks -4880,0,-4224 to -4865,255,-4209), Region: (-10,-9; contains chunks -320,-288 to -289,-257, blocks -5120,0,-4608 to -4609,255,-4097)
    Entity's Momentum: 0,00, 0,00, 0,00
    Entity's Rider: ~~ERROR~~ NullPointerException: null
    Entity's Vehicle: ~~ERROR~~ NullPointerException: null

-- Renderer details --
Details:
    Assigned renderer: net.minecraft.client.renderer.entity.RenderEnderman@767bb276
    Location: 17,18,-44,00,-0,17 - World: (17,-44,-1), Chunk: (at 1,-3,15 in 1,-1; contains blocks 16,0,-16 to 31,255,-1), Region: (0,-1; contains chunks 0,-32 to 31,-1, blocks 0,0,-512 to 511,255,-1)
    Rotation: 140.625
    Delta: 0.087043524
Stacktrace:
    at net.minecraft.client.renderer.entity.RenderManager.func_147939_a(RenderManager.java:402)
    at net.labymod.core_implementation.mc18.render.RenderManagerCustom.func_147939_a(RenderManagerCustom.java:120)
    at net.labymod.core_implementation.mc18.render.RenderManagerCustom.func_147936_a(RenderManagerCustom.java:107)
    at net.labymod.core_implementation.mc18.render.RenderManagerCustom.func_147937_a(RenderManagerCustom.java:82)
    at net.minecraft.client.renderer.RenderGlobal.func_180446_a(RenderGlobal.java:870)
    at net.minecraft.client.renderer.EntityRenderer.func_175068_a(EntityRenderer.java:1763)
    at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1580)

-- Affected level --
Details:
    Level name: MpServer
    All players: 1 total; [EntityPlayerSP['777UZI'/3099, l='MpServer', x=-4893,49, y=70,00, z=-4210,08]]
    Chunk stats: MultiplayerChunkCache: 81, 81
    Level seed: 0
    Level generator: ID 00 - default, ver 1. Features enabled: false
    Level generator options: 
    Level spawn location: -4157,00,66,00,5480,00 - World: (-4157,66,5480), Chunk: (at 3,4,8 in -260,342; contains blocks -4160,0,5472 to -4145,255,5487), Region: (-9,10; contains chunks -288,320 to -257,351, blocks -4608,0,5120 to -4097,255,5631)
    Level time: 168641 game time, 64868898 day time
    Level dimension: 0
    Level storage version: 0x00000 - Unknown?
    Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
    Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
    Forced entities: 7 total; [EntitySkeleton['Skeleton'/505253, l='MpServer', x=-4877,50, y=40,00, z=-4187,50], EntitySkeleton['Skeleton'/505252, l='MpServer', x=-4877,28, y=40,00, z=-4177,47], EntityZombie['Zombie'/505251, l='MpServer', x=-4873,50, y=12,00, z=-4240,50], EntityEnderman['Enderman'/505250, l='MpServer', x=-4876,31, y=26,00, z=-4210,25], EntitySkeleton['Skeleton'/505246, l='MpServer', x=-4873,50, y=26,00, z=-4206,50], EntityCreeper['Creeper'/505245, l='MpServer', x=-4880,50, y=8,00, z=-4193,50], EntityPlayerSP['777UZI'/3099, l='MpServer', x=-4893,49, y=70,00, z=-4210,08]]
    Retry entities: 0 total; []
    Server brand: BungeeCord (git:BungeeCord-Bootstrap:1.16-R0.4-SNAPSHOT:2366173:1534) <- Paper
    Server type: Non-integrated multiplayer server
Stacktrace:
    at net.minecraft.client.multiplayer.WorldClient.func_72914_a(WorldClient.java:402)
    at net.minecraft.client.Minecraft.func_71396_d(Minecraft.java:2536)
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:370)
    at net.minecraft.client.main.Main.main(SourceFile:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
    at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

-- System Details --
Details:
    Minecraft Version: 1.8.9
    Operating System: Windows 8 (amd64) version 6.2
    Java Version: 1.8.0_261, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 175354392 bytes (167 MB) / 558108672 bytes (532 MB) up to 1060372480 bytes (1011 MB)
    JVM Flags: 6 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump
    IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
    FML: MCP 9.19 Powered by Forge 11.15.1.1855 Optifine OptiFine_1.8.9_HD_U_L5 4 mods loaded, 4 mods active
    States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
    UCHIJA    mcp{9.19} [Minecraft Coder Pack] (minecraft.jar) 
    UCHIJA    FML{8.0.99.99} [Forge Mod Loader] (forge-1.8.9-11.15.1.1855.jar) 
    UCHIJA    Forge{11.15.1.1855} [Minecraft Forge] (forge-1.8.9-11.15.1.1855.jar) 
    UCHIJA    labymod{3.6.13} [LabyMod] (LabyMod-3.jar) 
    Loaded coremods (and transformers): 
LabyModCoreMod (LabyMod-3.jar)
  net.labymod.core.asm.LabyModTransformer
  net.labymod.addons.itemphysic.asm.ItemPhysicTransformer
  net.labymod.addons.moreparticle.asm.MoreParticleTranformer
    GL info: ' Vendor: 'Intel' Version: '4.0.0 - Build 9.17.10.2849' Renderer: 'Intel(R) HD Graphics 4000'
    Launched Version: 1.8.9-forge1.8.9-11.15.1.1855
    LWJGL: 2.9.4
    OpenGL: Intel(R) HD Graphics 4000 GL version 4.0.0 - Build 9.17.10.2849, Intel
    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: No
    Is Modded: Definitely; Client brand changed to 'fml,forge'
    Type: Client (map_client.txt)
    Resource Packs: !     §eZYAK RUSH PACK V2.zip (incompatible)
    Current Language: English (US)
    Profiler Position: N/A (disabled)
    CPU: 4x Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz
    OptiFine Version: OptiFine_1.8.9_HD_U_L5
    OptiFine Build: 20191204-143016
    Render Distance Chunks: 8
    Mipmaps: 4
    Anisotropic Filtering: 1
    Antialiasing: 0
    Multitexture: false
    Shaders: null
    OpenGlVersion: 4.0.0 - Build 9.17.10.2849
    OpenGlRenderer: Intel(R) HD Graphics 4000
    OpenGlVendor: Intel
    CpuCount: 4

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
    • When I came across the 'Exit Code: I got a 1 error in my Minecraft mods, so I decided to figure out what was wrong. First, I took a look at the logs. In the mods folder (usually where you'd find logs or crash reports), I found the latest.log file or the corresponding crash report. I read it through carefully, looking for any lines with errors or warnings. Then I checked the Minecraft Forge support site, where you can often find info on what causes errors and how to fix them. I then disabled half of my mods and tried running the game. If the error disappeared, it meant that the problem was with the disabled mod. I repeated this several times to find the problem mod.
    • I have no idea - switch to a pre-configured modpack and use it as working base    
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.