Ititializing Crash
MikeArclight opened this issue · 6 comments
Same issue as before; would have posted there, but the thread was closed. Anyway, got the core mod to work, by itself, once and only once. earlier this week, I had to uninstall/reinstall all mods, and a few had updated, so I figured to try an install mekanism; came up with the posted crash report. Figured I would try something new, and moved the mods folder to the desktop and made a new mods folder in the .minecraft directory. It worked, once.
As per your advice I have FMP 1.7.10-1.1.0.300 (both dev and universal; unsure as to which one was needed (tried them both alone and the result is the same: crash).
Checked my earlier post and to my untrained eye this seems to be a different kind of crash; or at least something different is setting it off (the electric bow).
Any help would be appreciated given how great i found the core mod (didn't get to the supplemental mods this time) the one instant I got it up and running.
ok so sorry i have to go through this but do you have all of the mekanism mods installed, all 4 of them?
if so delete your configs all of them, if it still persists idk what is happening but im not getting this. i have version .95
Only installed the core; thought of the corrupt download, so deleted core mod and redownloaded from proper site
You need to install the ic2 api (even though you're not using ic2, yes). So many other mods ship parts or all of their api that we're unable to depend on all of them. Installing the api itself will make it load up before any mods so we don't crash when we try to use their classes.
Apologies for the late reply, but I had no idea that these were also sent to my email. I would have thanked you on GitHub, but the second thread also closed before I had a chance. Yes, the installation of the IC2 API worked like a charm; of course, IC2 exp is an unstable beast; but since it really doesn't add anything that I want or don't already have, so I just took it out. The API remains (I was curious as to what IC2 exp had to offer: instability, that's what).
Right now, my Minecraft is highly unstable. I think it has to do with the 50 some odd mods I have installed (of which, a third are API's, cores, and other dependencies). Just this morning, the whole reason I fought so hard to get your mod installed was voided. You see, I have a mod called Advanced Genetics; a fun a well thought out mod. Unfortunately, the mod author decided to utilize a strange and non-intuitive power system. It's not RF, and it's not mJ; it's something else entirely (or if not, the fact certainly escapes me). In one of his earlier versions (MC 7.2 I believe), it was stated that your mod was power compatible with his, and since his singular power generation block ate coal like it was going out of style (about a 5 coal to 1 cycle ratio) and the fact that he included no wiring system (meaning that any block that required power from his mod had to be placed directly adjacent to his and only his generator). Imagine my joy once I was able
to run Mekanism, and imagine my frustration once it turned out that in his updated version, he had removed that in favor of IC2 exp (which, in turn, turned out to be false as well - believe me, i tried hooking up AG's blocks to every IC2 exp generator and every IC2 exp pipe in every conceivable fashion. I checked the forums and wikis - nothing worked).
Now, the base block of AG, the DNA Analyzer, is causing a ticking block error. Without the use of that block, AG is useless, since all other AG block functions stem from that one. I am going to try emailing the mod author with a crash report since he hasn't supplied a forum or GitHub address. I do not have high hopes for a response, though.
Anyway, none of this is your problem; I'm just venting in frustration. What I really wanted to say is thank you for your attention, your prompt responses, and your attention to detail. Without it, I would never have gotten your mod up and running.
Sincerely
Mike W.
On Thursday, September 4, 2014 7:43 PM, Ben Spiers [email protected] wrote:
Closed #1796.
—
Reply to this email directly or view it on GitHub.