In over 90% of all issues I have encountered on these forums, the relevant information that was needed to solve them, was contained in the Crash Report.
System information? Stacktrace? Java arguments? Minecraft, Forge and Mod versions? Other Installed mods? Core mods? All mentioned in the crash report.
In this case, it is almost certainly a conflict with another mod, though. Either the other mod is using a Vanilla method that Malisis is incorrectly altering, or (some mod, probably) Malisis is using a Vanilla method that another mod is incorrectly altering. I do not believe that these events are logged in the game log, though. If they are, and I reserve my right to be wrong, then in this case, the fml logs may be useful, however in general, crash logs are far from useless.
I don't mean to sound rude, but Ordinastie, you are an authority on knowing how Minecraft works and I want to prevent you from telling the laymen things that, in fact, just aren't true.
Let's say that nine times out of ten, the crash log won't give enough informations about what really happened. Often the crash log actually show the last part of a stack trace and hide the true reason for a crash (which is unintuitively at the bottom of a stacktrace).
Crashes are often a by product of something that happened earlier which was hopefully logged.
Usually, when a crash log is enough, it's because I'm already aware of the problem, or it's just a trivial mistake I shouldn't have made in the first place :).
I found a bug in the Door factory, When you create a double door. Once you open it, it will not let you close the doors. If you make a single door then it works fine.
Are you sure you didn't activate the Auto-open option?
- Fixed an issue that left ghost blocks when destroying Rusty Hatch.
- Fixed player detection for auto opening doors.
- Added sound when opening/closing Hi-tech doors.
- Fixed compatibility issue with Sponge.
- Added option in the door factory to allow doors to automatically open when player is close.
- Fixed bottom texture of the Hi-tech Door.
- Fixed server crash with CraftTweaker
- Fixed vanilla door texture issue with LiteLoader
- Migrated transformers to mixin. (Internal, probably broke many things)
Apparently, there is an issue between Mixin and MultiMC. The issue is currently being investigated.
I guess I releases the Mixin update to soon, not quite as stable as I hoped. I'll remove the download from Curseforge.
- Fixed server crash with CraftTweaker
- Fixed vanilla door texture issue with LiteLoader
- Migrated transformers to Mixin. (Internal, probably broke many things)
Hi, awesome mod. Need a bit a help, my client keeps crashing. (1.11.2) Latest MalisisDoors and MalisisCore for 1.11.2.
I am using forge-1.11.2-13.20.1.2476.
Here's the crash report:
---- Minecraft Crash Report ----
WARNING: coremods are present:
RebornCoreASM (RebornCore-1.11.2-2.13.4.37-universal.jar)
llibrary (llibrary-1.7.7-1.11.2.jar)
BCModPlugin (zz-backpacks 1.11.2 - 3.1.6.jar)
ShetiPhian-ASM (shetiphiancore-1.11.0-3.4.3.jar)
IvToolkit (IvToolkit-1.3.2.1.jar)
MalisisCorePlugin (malisiscore-1.11.2-5.2.5.jar)
Contact their authors BEFORE contacting forge
// Surprise! Haha. Well, this is awkward.
Time: 9/26/17 6:23 PM
Description: There was a severe problem during mod loading that has caused the game to fail
net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from MalisisDoors (malisisdoors)
Caused by: java.lang.ExceptionInInitializerError
at net.malisis.doors.MalisisDoors.postInit(MalisisDoors.java:101)
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.minecraftforge.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:647)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at net.minecraftforge.fml.common.LoadController.sendEventToModContainer(LoadController.java:253)
at net.minecraftforge.fml.common.LoadController.propogateStateMessage(LoadController.java:231)
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 com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at net.minecraftforge.fml.common.LoadController.distributeStateMessage(LoadController.java:148)
at net.minecraftforge.fml.common.Loader.initializeMods(Loader.java:833)
at net.minecraftforge.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:357)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:521)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:352)
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)
Caused by: java.lang.ClassCastException: [F cannot be cast to [I
at net.malisis.core.renderer.font.MinecraftFont.setFields(MinecraftFont.java:94)
at net.malisis.core.renderer.font.MinecraftFont.<init>(MinecraftFont.java:68)
at net.malisis.core.renderer.font.MalisisFont.<clinit>(MalisisFont.java:73)
... 37 more
0
Never download mods from unofficial shady sites. Download latest versions from Curseforge and try again.
0
I was asking because the log doesn't seem to contain everything. Was this the fml-client-latest.log ?
0
I think it should. Did you test it ?
0
Let's say that nine times out of ten, the crash log won't give enough informations about what really happened. Often the crash log actually show the last part of a stack trace and hide the true reason for a crash (which is unintuitively at the bottom of a stacktrace).
Crashes are often a by product of something that happened earlier which was hopefully logged.
Usually, when a crash log is enough, it's because I'm already aware of the problem, or it's just a trivial mistake I shouldn't have made in the first place :).
Looks like server logs. Is this on dedicated servers ? Does it crash for clients too ?
0
I would need full log. Crash logs are rarely useful.
I told you what you need to do... Download the latest version from Curseforge.
0
Can you provide full log ?
Are you sure you didn't activate the Auto-open option?
That's why you don't download mods from bad sites. Download the latest version from Curseforge.
Also, update! 1.7.10 is long dead.
0
New version : MalisisDoors 1.12.2-7.1.1 for Minecraft 1.12.2
Requires MalisisCore 1.12.2-6.1.7
- Fixed an issue that left ghost blocks when destroying Rusty Hatch.
- Fixed player detection for auto opening doors.
- Added sound when opening/closing Hi-tech doors.
- Fixed compatibility issue with Sponge.
0
Just add a timer to auto-close.
0
New version : MalisisDoors 1.12.2-7.1.0 for Minecraft 1.12
Requires MalisisCore 1.12.2-6.1.2
- Added option in the door factory to allow doors to automatically open when player is close.
- Fixed bottom texture of the Hi-tech Door.
- Fixed server crash with CraftTweaker
- Fixed vanilla door texture issue with LiteLoader
- Migrated transformers to mixin. (Internal, probably broke many things)
0
Low chance of that happening, sorry.
Apparently, there is an issue between Mixin and MultiMC. The issue is currently being investigated.
I guess I releases the Mixin update to soon, not quite as stable as I hoped. I'll remove the download from Curseforge.
0
New version for MalisisCore : 1.12-6.1.0
- Fixed server crash with CraftTweaker
- Fixed vanilla door texture issue with LiteLoader
- Migrated transformers to Mixin. (Internal, probably broke many things)
0
It will be fixed in the next update. It should come within a few days.
Update Optifine.
0
Update Optifine.
0
Nope.
0
Yes, it's a know compatibility issue with Crafttweaker. It will be fixed in the next update.