This is the OLD Rival Rebels forum (Locked). To go to the NEW Forum please click here.
This topic contains 5 replies, has 3 voices, and was last updated by Sour 10 months, 3 weeks ago.
-
strange HBM crash
-
September 30, 2018 at 6:25 am #20082
whenever i try to enter any world in HBM i crash. i tried updating forge and removing all of my mods besides HBM but it still crashes. here is the crash report:
<div>—- Minecraft Crash Report —-</div>
<div>// Sorry :(</div>
<div></div>
<div>Time: 9/30/18 9:25 AM</div>
<div>Description: Exception in server tick loop</div>
<div></div>
<div>java.lang.IllegalArgumentException: bound must be positive</div>
<div>at java.util.Random.nextInt(Random.java:388)</div>
<div>at com.hbm.main.ModEventHandler.worldTick(ModEventHandler.java:98)</div>
<div>at cpw.mods.fml.common.eventhandler.ASMEventHandler_10_ModEventHandler_worldTick_WorldTickEvent.invoke(.dynamic)</div>
<div>at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54)</div>
<div>at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:140)</div>
<div>at cpw.mods.fml.common.FMLCommonHandler.onPreWorldTick(FMLCommonHandler.java:268)</div>
<div>at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:620)</div>
<div>at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)</div>
<div>at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:111)</div>
<div>at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427)</div>
<div>at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)</div>
<div></div>
<div></div>
<div>A detailed walkthrough of the error, its code path and all known details is as follows:</div>
<div>—————————————————————————————</div>
<div></div>
<div>– System Details –</div>
<div>Details:</div>
<div>Minecraft Version: 1.7.10</div>
<div>Operating System: Linux (amd64) version 3.19.0-69-generic</div>
<div>Java Version: 1.8.0_181, Oracle Corporation</div>
<div>Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation</div>
<div>Memory: 111204512 bytes (106 MB) / 315211776 bytes (300 MB) up to 1060372480 bytes (1011 MB)</div>
<div>JVM Flags: 5 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M</div>
<div>AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used</div>
<div>IntCache: cache: 6, tcache: 0, allocated: 12, tallocated: 94</div>
<div>FML: MCP v9.05 FML v7.10.99.99 Minecraft Forge 10.13.4.1614 4 mods loaded, 4 mods active</div>
<div>States: ‘U’ = Unloaded ‘L’ = Loaded ‘C’ = Constructed ‘H’ = Pre-initialized ‘I’ = Initialized ‘J’ = Post-initialized ‘A’ = Available ‘D’ = Disabled ‘E’ = Errored</div>
<div>UCHIJAAAAmcp{9.05} [Minecraft Coder Pack] (minecraft.jar)</div>
<div>UCHIJAAAAFML{7.10.99.99} [Forge Mod Loader] (forge-1.7.10-10.13.4.1614-1.7.10.jar)</div>
<div>UCHIJAAAAForge{10.13.4.1614} [Minecraft Forge] (forge-1.7.10-10.13.4.1614-1.7.10.jar)</div>
<div>UCHIJAAAAhbm{1.0.27 BETA (2904)} [Hbm’s Nuclear Tech] (hbm1.0.27_BETA2904 (2).jar)</div>
<div>GL info: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.</div>
<div>Profiler Position: N/A (disabled)</div>
<div>Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used</div>
<div>Player Count: 0 / 8; []</div>
<div>Type: Integrated Server (map_client.txt)</div>
<div>Is Modded: Definitely; Client brand changed to ‘fml,forge'</div>LÖÖPS
September 30, 2018 at 11:03 am #20089It’s not so strange if you meddle with the config. Let me guess, you set the meteor strike variable to 0?
Sometimes, I dream about cheese.September 30, 2018 at 11:21 am #20092yes i did… should i just delete the config file then?
edit: deleted the config, it works like a charm. thanks!
LÖÖPS
September 30, 2018 at 3:19 pm #20095The config description even says where the problem is
The probability of a meteor spawning (an average of once every nTH ticks)
Every 20 ticks means there’ll be an average of a single meteor per second (since a second is 20 ticks)
Every 2 ticks means there will be on average a meteor every two ticks (or 10 per second)
As you can see, the game basically “rolls dice” to decide whether or not to spawn a meteor. The 1/20 chance is basically “roll a die with 20 faces, if the die lands on 20, spawn a meteor”.
Now try to roll a zero-sided die. I think you know where the problem is.
Sometimes, I dream about cheese.September 30, 2018 at 3:46 pm #20096thanks for the help!
LÖÖPS
September 30, 2018 at 3:55 pm #20097Locked
Because reasons
-
strange HBM crash
The topic ‘strange HBM crash’ is closed to new replies.