Hrm. If someone could get me a copy of the error logs from when cockatrices seem to be exploding, that would help tremendously. I might be able to figure it out with the help of such data.
Unfortunately I didn't save it the last time it happened. It doesn't actually crash, so I'm guessing it'd only be saved in the log and not an actual crash report. I'll do some testing though and let you know. But it seems like a rare event that I'll actually get the constant error stream.
A new mob, the hunter, has been introduced. Read about him in the OP.
In the course of coding the hunter, I stumbled across a potential solution to the excessive lag caused by the lizalfos. A fix has been implemented. Let me know if issues persist.
If you're still using 1.5 (or even 1.4.6/1.4.7), you can find the most updated versions of Dungeon Mobs for those versions of MC in the OP, under the "previous versions" header.
Can you like hire the Hunter with Gold ingots? That would be an awesome thing to put in the mod
No. No you cannot, and I will do no such thing.
The only reason the hunter even exists is because I wanted to add a mob that was more than just itself, but brought a group of minions to the fight. Justification for such mobs was difficult, however. I decided that the best implementation would be something related to villages.
I have no interest in making mobs that make your life easier, or that you can hire or train or tame or what-have-you. Their purpose in life is to make yours nasty, brutish, and short. End of story.
The only reason the hunter even exists is because I wanted to add a mob that was more than just itself, but brought a group of minions to the fight. Justification for such mobs was difficult, however. I decided that the best implementation would be something related to villages.
I have no interest in making mobs that make your life easier, or that you can hire or train or tame or what-have-you. Their purpose in life is to make yours nasty, brutish, and short. End of story.
Okay, but what about he betrays you after a while? Or kills you when your health is low and ransacks you of your items?
Have the bugfixes and new monster been added to the 1.4.7 versions too? Also, I havent found a recommended Forge version yet that doesnt throw up more errors than is acceptable.
Not yet. I'll post regarding the update for the 1.4.6/1.4.7 version when it's ready. I didn't want to do anything with it until I figured out the lizalfos and cockatrice problems, so we're half-way there.
The next time a cockatrice explodes I will get you a copy of the forge log. It doesnt crash the game. Its not every cockatrice encounter, say about 40% is about right.
If it's spitting out anything in a log, that means something is going wrong, even if it isn't crashing. But yes, getting me a copy of that information will seriously help - as I said earlier, I'm pretty much at a loss with what information I have available now.
Introducing a new mob, the manticore. Read about it in the OP.
The cave fisher received a few modifications, in particular a potential fix to their web generation. In addition, I found another potential spot for memory leaks in the cave fisher's code, which has been patched.
This update does not have a corresponding update to the MC 1.4.7 version of Dungeon Mobs. At this point, I am waiting on information regarding the "exploding cockatrice" problem so that that issue can be resolved - once I have sufficient data to fix that, the final update for Dungeon Mobs for MC 1.4.7 will be uploaded, and will hopefully address the major problems (lizalfos lag and exploding cockatrice), as well as the bugfixes introduced in Dungeon Mobs v2.0.0.
This is the final release of Dungeon Mobs for Minecraft 1.4.6/1.4.7, and includes all of the bug fixes included in the main release, as well as (hopefully) a fix to the exploding cockatrice problem.
You can find the download in the OP, under "previous versions." Remember that Forge 6.5.0.471 or higher is required for Dungeon Mobs for Minecraft 1.4.6/1.4.7.
The true source of the lizalfos "leaking worlds" problem has been found, and been completely resolved. It was due to a lizalfos holding a hard reference to its twin; going through the code and replacing the hard reference with a weak reference, as well as the checks necessary to make sure the reference was replaced if garbage collection got to it, seems to have completely resolved the problem.
Nice. Thanks GnomeWorks. Shame we didn't get any of the new mobs with the 1.4.7 update, but at least we got the bugfixes.
One minor issue I've noticed, though - The rust monster isn't loading his sounds. They're definitely in the zip, but there's an error about being unable to load them.
One minor issue I've noticed, though - The rust monster isn't loading his sounds. They're definitely in the zip, but there's an error about being unable to load them.
...oh, right. That's what I get for not keeping my change log up to date and synchronized with what I'm doing, I'd fixed that in a later update.
Hotfix has been uploaded, please re-download Dungeon Mobs v1.11.3.Fb for sound fix.
The lizalfos fix implemented for the MC 1.4.7 version of Dungeon Mobs has been implemented. I am roughly 95% certain that the "leaking worlds" problem has been resolved: in a long round of testing, I witnessed no leaking worlds report from Forge. It is possible that I missed some corner cases, but in general, it should work fine.
In addition, the source of the "exploding cockatrice" problem has been narrowed down, and I believe it has been resolved. As always, if issues persist, let me know.
The hunter has been dummied out for the time being. After extensive attempts to resolve its own "leaking worlds" problem, it appears that its own bugs in that regard are more persistent than the lizalfos'. The hunter is also presently suffering from some client/server interaction problems. Given these difficulties, and the importance of fixing the lizalfos, I have decided to temporarily shelve the hunter. It will return in a future update, provided I can figure out a way to resolve its many difficulties.
Dungeon Mobs v2.3.2 (for MC 1.5.1) and v1.11.3.Fc (for MC 1.4.6/1.4.7) are live.
v2.3.2 brings a fix to illithids, apparently the call for armor locations was inaccurate and has been corrected.
v1.11.3.Fc brings yet another fix to cockatrices. Shouldn't be a problem anymore.
Quote from MohawkyMagoo »
On 1.4.7 - Two exploding cockatrices within seconds of each other. Full log exceeds pastebin limits, I have it if you want it by email, but relevenat bit is here::
Hi! I love the new update! Also, in the next update, please bring back hunters! They sound really hilarious (yelling upon death)! Also, are the hunters D&D or LoZ? Can you change the manticore's model (add some wings) and make it capable of saving itself from fall damage? I have 2 mob suggestions for you. Both of them are D&D.
Lich (because it was ignored the first time): Health: 60
Strength: 6
Behaviour: Aggressive, casts spells (which look like villager happy particles).
Drops: Bones and ender pearls.
Violet Fungus (because it was also ignored): Health: Same as a shrieker
Strength: 4
Behaviour: Aggressive, attacks you like a zombie, just as unintelligent as a shrieker. (Obviously) gets attracted to shriekers.
Drops: Red mushroom.
That's it! I hope you do this! You can do it, Mr. GnomeWorks!
Also, in the next update, please bring back hunters!
Maybe! Why are you yelling!
Also, are the hunters D&D or LoZ?
Neither.
Can you change the manticore's model (add some wings) and make it capable of saving itself from fall damage?
No.
I have 2 mob suggestions for you.
I am not taking requests and/or dealing with suggestions at this time. In the far future, when there is only war, I may start doing so. Until that day, not so much.
Huh... Dunno if this is caused by this mod, MCHerds, or just a compatibility issue between them:
t: Ticking entity
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:686)
at ho.r(DedicatedServer.java:269)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
at fy.run(SourceFile:849)
Caused by: java.lang.NullPointerException
at gnomeWorks.dungeonMobs.EntityGhoul.m(EntityGhoul.java:87)
at MCHerds.entity.ai.EntityAIHerdAttackOnCollide.e(EntityAIHerdAttackOnCollide.java:163)
at nd.a(SourceFile:100)
at md.bl(EntityLiving.java:2057)
at md.c(EntityLiving.java:1782)
at qj.c(SourceFile:26)
at qr.c(SourceFile:130)
at md.j_(EntityLiving.java:843)
at qj.j_(SourceFile:31)
at qr.j_(SourceFile:145)
at yc.a(World.java:2293)
at in.a(WorldServer.java:647)
at yc.g(World.java:2255)
at yc.h(World.java:2109)
at in.h(WorldServer.java:516)
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:680)
... 4 more
It'd be a shame to have to lose either mod, but this crashed my server and it wouldn't start up again until I disabled Dungeon Mobs, restarted to let everything despawn, and then re-enabled Dungeon Mobs.
Unfortunately I didn't save it the last time it happened. It doesn't actually crash, so I'm guessing it'd only be saved in the log and not an actual crash report. I'll do some testing though and let you know. But it seems like a rare event that I'll actually get the constant error stream.
Think it's an array out of index error.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumA new mob, the hunter, has been introduced. Read about him in the OP.
In the course of coding the hunter, I stumbled across a potential solution to the excessive lag caused by the lizalfos. A fix has been implemented. Let me know if issues persist.
Ah... okay. That helps. I'll look into it.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumUpdated to Minecraft v1.5.1, and... that's all.
If you're still using 1.5 (or even 1.4.6/1.4.7), you can find the most updated versions of Dungeon Mobs for those versions of MC in the OP, under the "previous versions" header.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo. No you cannot, and I will do no such thing.
The only reason the hunter even exists is because I wanted to add a mob that was more than just itself, but brought a group of minions to the fight. Justification for such mobs was difficult, however. I decided that the best implementation would be something related to villages.
I have no interest in making mobs that make your life easier, or that you can hire or train or tame or what-have-you. Their purpose in life is to make yours nasty, brutish, and short. End of story.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse Premium...what part of "no" do you not get?
Hunters are of one of two dispositions: ignore you, or kill you dead. End of story.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNot yet. I'll post regarding the update for the 1.4.6/1.4.7 version when it's ready. I didn't want to do anything with it until I figured out the lizalfos and cockatrice problems, so we're half-way there.
If it's spitting out anything in a log, that means something is going wrong, even if it isn't crashing. But yes, getting me a copy of that information will seriously help - as I said earlier, I'm pretty much at a loss with what information I have available now.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIntroducing a new mob, the manticore. Read about it in the OP.
The cave fisher received a few modifications, in particular a potential fix to their web generation. In addition, I found another potential spot for memory leaks in the cave fisher's code, which has been patched.
This update does not have a corresponding update to the MC 1.4.7 version of Dungeon Mobs. At this point, I am waiting on information regarding the "exploding cockatrice" problem so that that issue can be resolved - once I have sufficient data to fix that, the final update for Dungeon Mobs for MC 1.4.7 will be uploaded, and will hopefully address the major problems (lizalfos lag and exploding cockatrice), as well as the bugfixes introduced in Dungeon Mobs v2.0.0.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
The fabled cockatrice error:
2013-03-23 20:25:42 [INFO] [STDERR] java.lang.reflect.InvocationTargetException
2013-03-23 20:25:42 [INFO] [STDERR] at sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
2013-03-23 20:25:42 [INFO] [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
2013-03-23 20:25:42 [INFO] [STDERR] at java.lang.reflect.Constructor.newInstance(Unknown Source)
2013-03-23 20:25:42 [INFO] [STDERR] at lv.a(EntityList.java:114)
2013-03-23 20:25:42 [INFO] [STDERR] at ans.c(SourceFile:225)
2013-03-23 20:25:42 [INFO] [STDERR] at bdr.a(SourceFile:17)
2013-03-23 20:25:42 [INFO] [STDERR] at bdr.a(SourceFile:11)
2013-03-23 20:25:42 [INFO] [STDERR] at bdw.a(SourceFile:103)
2013-03-23 20:25:42 [INFO] [STDERR] at bdw.a(SourceFile:96)
2013-03-23 20:25:42 [INFO] [STDERR] at bav.a(RenderGlobal.java:522)
2013-03-23 20:25:42 [INFO] [STDERR] at ban.a(EntityRenderer.java:1585)
2013-03-23 20:25:42 [INFO] [STDERR] at ban.b(EntityRenderer.java:1121)
2013-03-23 20:25:42 [INFO] [STDERR] at net.minecraft.client.Minecraft.J(Minecraft.java:882)
2013-03-23 20:25:42 [INFO] [STDERR] at net.minecraft.client.Minecraft.run(Minecraft.java:771)
2013-03-23 20:25:42 [INFO] [STDERR] at java.lang.Thread.run(Unknown Source)
2013-03-23 20:25:42 [INFO] [STDERR] Caused by: java.lang.NullPointerException
2013-03-23 20:25:42 [INFO] [STDERR] at gnomeWorks.dungeonMobs.EntityCockatrice.<init>(EntityCockatrice.java:32)
2013-03-23 20:25:42 [INFO] [STDERR] ... 15 more
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis is the final release of Dungeon Mobs for Minecraft 1.4.6/1.4.7, and includes all of the bug fixes included in the main release, as well as (hopefully) a fix to the exploding cockatrice problem.
You can find the download in the OP, under "previous versions." Remember that Forge 6.5.0.471 or higher is required for Dungeon Mobs for Minecraft 1.4.6/1.4.7.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe true source of the lizalfos "leaking worlds" problem has been found, and been completely resolved. It was due to a lizalfos holding a hard reference to its twin; going through the code and replacing the hard reference with a weak reference, as well as the checks necessary to make sure the reference was replaced if garbage collection got to it, seems to have completely resolved the problem.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
One minor issue I've noticed, though - The rust monster isn't loading his sounds. They're definitely in the zip, but there's an error about being unable to load them.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium...oh, right. That's what I get for not keeping my change log up to date and synchronized with what I'm doing, I'd fixed that in a later update.
Hotfix has been uploaded, please re-download Dungeon Mobs v1.11.3.Fb for sound fix.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe lizalfos fix implemented for the MC 1.4.7 version of Dungeon Mobs has been implemented. I am roughly 95% certain that the "leaking worlds" problem has been resolved: in a long round of testing, I witnessed no leaking worlds report from Forge. It is possible that I missed some corner cases, but in general, it should work fine.
In addition, the source of the "exploding cockatrice" problem has been narrowed down, and I believe it has been resolved. As always, if issues persist, let me know.
The hunter has been dummied out for the time being. After extensive attempts to resolve its own "leaking worlds" problem, it appears that its own bugs in that regard are more persistent than the lizalfos'. The hunter is also presently suffering from some client/server interaction problems. Given these difficulties, and the importance of fixing the lizalfos, I have decided to temporarily shelve the hunter. It will return in a future update, provided I can figure out a way to resolve its many difficulties.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumv2.3.2 brings a fix to illithids, apparently the call for armor locations was inaccurate and has been corrected.
v1.11.3.Fc brings yet another fix to cockatrices. Shouldn't be a problem anymore.
Nope, that was good enough, danke.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
Lich (because it was ignored the first time): Health: 60
Strength: 6
Behaviour: Aggressive, casts spells (which look like villager happy particles).
Drops: Bones and ender pearls.
Violet Fungus (because it was also ignored): Health: Same as a shrieker
Strength: 4
Behaviour: Aggressive, attacks you like a zombie, just as unintelligent as a shrieker. (Obviously) gets attracted to shriekers.
Drops: Red mushroom.
That's it! I hope you do this! You can do it, Mr. GnomeWorks!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMaybe! Why are you yelling!
Neither.
No.
I am not taking requests and/or dealing with suggestions at this time. In the far future, when there is only war, I may start doing so. Until that day, not so much.
The reverse side also has a reverse side.
My Mods: Dungeon Mobs | (WIP) Blind Mapmaker
So.... in the year 40,000?
t: Ticking entity
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:686)
at ho.r(DedicatedServer.java:269)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
at fy.run(SourceFile:849)
Caused by: java.lang.NullPointerException
at gnomeWorks.dungeonMobs.EntityGhoul.m(EntityGhoul.java:87)
at MCHerds.entity.ai.EntityAIHerdAttackOnCollide.e(EntityAIHerdAttackOnCollide.java:163)
at nd.a(SourceFile:100)
at md.bl(EntityLiving.java:2057)
at md.c(EntityLiving.java:1782)
at qj.c(SourceFile:26)
at qr.c(SourceFile:130)
at md.j_(EntityLiving.java:843)
at qj.j_(SourceFile:31)
at qr.j_(SourceFile:145)
at yc.a(World.java:2293)
at in.a(WorldServer.java:647)
at yc.g(World.java:2255)
at yc.h(World.java:2109)
at in.h(WorldServer.java:516)
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:680)
... 4 more