The Meaning of Life, the Universe, and Everything.
Location:
Toronto
Join Date:
6/11/2012
Posts:
178
Minecraft:
Eunomiac
Xbox:
Eunomiac
Member Details
I've got great respect for all that you're doing, Mithion, but I've got a bone to pick with you, hopefully without being branded a whiny, entitled gamer
Nearly six months ago, I reported bug #393, whereby Hecates would fail to despawn, crowd out the mob cap, and prevent all other hostile mobs from spawning. I realize you have this fixed for 1.2, but this is the sort of bug that really deserves a hotfix before then, because it's a nasty one: It's a silent, insidious killer, with no error messages to inform players what is happening---or, indeed, that anything is happening.
As a result, a significant number of people running AM2 over the past half-year have silently suffered at the mercy of this bug. Their mob spawns die off almost completely, and---once they notice---they have no idea why. I've replied to at least a half-dozen people on the feedthebeast subreddit expressing their bafflement over this issue, and telling them the only known work-around---to disable Hecates using OpenBlock's config.
Is there any way we could implore you to please release a v.1.1.2c hotfix of this issue while we wait (excitedly!) for AM 1.2?
Rollback Post to RevisionRollBack
Amateur dinosaur hunter and extreme weather enthusiast, whose interests include spoken mime, armchair parkour, tactical gaslighting (for fun or for pay), conspicuous ninjutsu and Schröedinger's pentameter—of which this sentence may or may not be an example.
I have never heard of a mod that didn't need changing between any minecraft updates, much less large changes like .6 > .7. But you are welcome to try, if it works let mithion know, I'm sure he will be extatic lol
Why is it "will 1.2 be for 1.7.x?" gets asked on every page when the answer is on the past +20?
Honestly, it's because I didn't want to read through that many pages in hopes that my particular question was asked. On the last page, I saw someone mention their 1.7.2 world and how they were excited to implement AM2 1.2 into that world.
Honestly, it's because I didn't want to read through that many pages in hopes that my particular question was asked. On the last page, I saw someone mention their 1.7.2 world and how they were excited to implement AM2 1.2 into that world.
Ah right, understandable. Sorry mate, wasn't directed at you specifically. A suggestion though, going to a topic and using the search with a key like 1.7.2 might get you an answer on an update before you ask.
I've got great respect for all that you're doing, Mithion, but I've got a bone to pick with you, hopefully without being branded a whiny, entitled gamer
Nearly six months ago, I reported bug #393, whereby Hecates would fail to despawn, crowd out the mob cap, and prevent all other hostile mobs from spawning. I realize you have this fixed for 1.2, but this is the sort of bug that really deserves a hotfix before then, because it's a nasty one: It's a silent, insidious killer, with no error messages to inform players what is happening---or, indeed, that anything is happening.
As a result, a significant number of people running AM2 over the past half-year have silently suffered at the mercy of this bug. Their mob spawns die off almost completely, and---once they notice---they have no idea why. I've replied to at least a half-dozen people on the feedthebeast subreddit expressing their bafflement over this issue, and telling them the only known work-around---to disable Hecates using OpenBlock's config.
Is there any way we could implore you to please release a v.1.1.2c hotfix of this issue while we wait (excitedly!) for AM 1.2?
Well 1.1.2 doesn't have that bug, just b and your not really missing a whole lot by downgrading on that one all things considered.
It's way too long to post on this, it wont allow me to post it, I looked at it for a bit and this part looks important so I'll post that part.
2014-06-24 22:35:23 [FINE] [ForgeModLoader] Examining file AM2_1.1.2b.zip for potential mods
2014-06-24 22:35:23 [WARNING] [ForgeModLoader] Zip file AM2_1.1.2b.zip failed to read properly, it will be ignored
java.util.zip.ZipException: invalid END header (bad central directory offset)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(Unknown Source)
at java.util.zip.ZipFile.(Unknown Source)
at java.util.jar.JarFile.(Unknown Source)
at java.util.jar.JarFile.(Unknown Source)
at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:41)
at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42)
at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71)
at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137)
at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:484)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808)
at net.minecraft.client.main.Main.main(SourceFile: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.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
2014-06-24 22:35:23 [INFO] [ForgeModLoader] Forge Mod Loader has identified 3 mods to load
I've got great respect for all that you're doing, Mithion, but I've got a bone to pick with you, hopefully without being branded a whiny, entitled gamer
Nearly six months ago, I reported bug #393, whereby Hecates would fail to despawn, crowd out the mob cap, and prevent all other hostile mobs from spawning. I realize you have this fixed for 1.2, but this is the sort of bug that really deserves a hotfix before then, because it's a nasty one: It's a silent, insidious killer, with no error messages to inform players what is happening---or, indeed, that anything is happening.
As a result, a significant number of people running AM2 over the past half-year have silently suffered at the mercy of this bug. Their mob spawns die off almost completely, and---once they notice---they have no idea why. I've replied to at least a half-dozen people on the feedthebeast subreddit expressing their bafflement over this issue, and telling them the only known work-around---to disable Hecates using OpenBlock's config.
Is there any way we could implore you to please release a v.1.1.2c hotfix of this issue while we wait (excitedly!) for AM 1.2?
The reason a 1.1.2c was never released was twofold - first, a simple downgrade to 1.1.2 solved that issue, and second, I didn't have proper versioning in place until 1.2. Since I was already well into the code for 1.2 when the bug was reported, I couldn't do a small fix and release without losing all of my progress.
Now I can, as I have proper version control in place.
Because it isn't in the OP and no one "new" reads previous pages.
And I quote the OP under the FAQ section, which was updated over 2 months ago:
When is 1.7.x coming?
1.7.x will happen, but not until after the 1.2 update comes out. A small update will be released afterward with the sole purpose of updating from 1.6.4 to 1.7.x. Note that 1.2 will be the *final* update for 1.6.4, and will not be supported after the 1.7.x update.
It's way too long to post on this, it wont allow me to post it, I looked at it for a bit and this part looks important so I'll post that part.
2014-06-24 22:35:23 [FINE] [ForgeModLoader] Examining file AM2_1.1.2b.zip for potential mods
2014-06-24 22:35:23 [WARNING] [ForgeModLoader] Zip file AM2_1.1.2b.zip failed to read properly, it will be ignored
java.util.zip.ZipException: invalid END header (bad central directory offset)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(Unknown Source)
at java.util.zip.ZipFile.(Unknown Source)
at java.util.jar.JarFile.(Unknown Source)
at java.util.jar.JarFile.(Unknown Source)
at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:41)
at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42)
at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71)
at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137)
at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:484)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808)
at net.minecraft.client.main.Main.main(SourceFile: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.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
2014-06-24 22:35:23 [INFO] [ForgeModLoader] Forge Mod Loader has identified 3 mods to load
Yeah, I knew it would be too long that's why I suggested using Pastebin or a similar web service in one of my earlier posts.
But looking at only this part my first instinct says that you have an incomplete or corrupted download. I would suggest redownloading the Ars Magica 2 zip file. Of course, I can't be certain without seeing the whole log.
Yeah, that really does look like your AM2 zip file didn't download properly. Try redownloading it and giving that a shot. If that doesn't work I'm going to have to defer to the rest of the forum on this one.
I've got great respect for all that you're doing, Mithion, but I've got a bone to pick with you, hopefully without being branded a whiny, entitled gamer
Nearly six months ago, I reported bug #393, whereby Hecates would fail to despawn, crowd out the mob cap, and prevent all other hostile mobs from spawning. I realize you have this fixed for 1.2, but this is the sort of bug that really deserves a hotfix before then, because it's a nasty one: It's a silent, insidious killer, with no error messages to inform players what is happening---or, indeed, that anything is happening.
As a result, a significant number of people running AM2 over the past half-year have silently suffered at the mercy of this bug. Their mob spawns die off almost completely, and---once they notice---they have no idea why. I've replied to at least a half-dozen people on the feedthebeast subreddit expressing their bafflement over this issue, and telling them the only known work-around---to disable Hecates using OpenBlock's config.
Is there any way we could implore you to please release a v.1.1.2c hotfix of this issue while we wait (excitedly!) for AM 1.2?
So that's what's been going wrong in my world! Thanks for that!
Just wondering when the ars magica 2 1.2 and 1.7.2 update is coming out since i cant upgrade to 1.7.2 without having the ars magica 2 mod installed
Anyways good luck with ars magica 2 and the updates
Yay indeed!
Also, for future releases, anyway you could start making use of the AnimationAPI for your mobs in this mod?
http://www.minecraftforum.net/topic/1850860-172spmp-animationapi-animate-your-entities-v121/
How much do you wish to bet that it's exactly two weeks from now?
Pretty sure that might be a thing for some of the bosses in 1.2 but wont know for sure until the release
Ok, then post that please.
Nearly six months ago, I reported bug #393, whereby Hecates would fail to despawn, crowd out the mob cap, and prevent all other hostile mobs from spawning. I realize you have this fixed for 1.2, but this is the sort of bug that really deserves a hotfix before then, because it's a nasty one: It's a silent, insidious killer, with no error messages to inform players what is happening---or, indeed, that anything is happening.
As a result, a significant number of people running AM2 over the past half-year have silently suffered at the mercy of this bug. Their mob spawns die off almost completely, and---once they notice---they have no idea why. I've replied to at least a half-dozen people on the feedthebeast subreddit expressing their bafflement over this issue, and telling them the only known work-around---to disable Hecates using OpenBlock's config.
Is there any way we could implore you to please release a v.1.1.2c hotfix of this issue while we wait (excitedly!) for AM 1.2?
AM2 v1.2 is updated to 1.7.x correct?
Are permissions for this mod still the same?
You are mistaken. It has not updated as of yet. 1.2 will be out soontm for 1.6.4, and then onward to 1.7 land.
Any idea if AM2 1.2 will work in 1.7.2 anyway?
Why is it "will 1.2 be for 1.7.x?" gets asked on every page when the answer is on the past +20?
Ah right, understandable. Sorry mate, wasn't directed at you specifically. A suggestion though, going to a topic and using the search with a key like 1.7.2 might get you an answer on an update before you ask.
Well 1.1.2 doesn't have that bug, just b and your not really missing a whole lot by downgrading on that one all things considered.
Use Pastebin
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe reason a 1.1.2c was never released was twofold - first, a simple downgrade to 1.1.2 solved that issue, and second, I didn't have proper versioning in place until 1.2. Since I was already well into the code for 1.2 when the bug was reported, I couldn't do a small fix and release without losing all of my progress.
Now I can, as I have proper version control in place.
And I quote the OP under the FAQ section, which was updated over 2 months ago:
When is 1.7.x coming?
1.7.x will happen, but not until after the 1.2 update comes out. A small update will be released afterward with the sole purpose of updating from 1.6.4 to 1.7.x. Note that 1.2 will be the *final* update for 1.6.4, and will not be supported after the 1.7.x update.
Yeah, I knew it would be too long that's why I suggested using Pastebin or a similar web service in one of my earlier posts.
But looking at only this part my first instinct says that you have an incomplete or corrupted download. I would suggest redownloading the Ars Magica 2 zip file. Of course, I can't be certain without seeing the whole log.
Yeah, that really does look like your AM2 zip file didn't download properly. Try redownloading it and giving that a shot. If that doesn't work I'm going to have to defer to the rest of the forum on this one.
So that's what's been going wrong in my world! Thanks for that!
Anyways good luck with ars magica 2 and the updates