Now, to address everyone who wants a forge version.
1. The problem with forge is that it's not compatible with optifine. Why? Well because optifine will screw up the textures of blocks/items in a forge mod, but that doesn't happen to modloader.
2. For some people modloader is easier, since forge gets a new build every day/week, so you often have to download the most recent build, which can sometimes be the only compatible version for whatever mod you want. (The portalgun mod goes along the lines of that, requiring build 255 or higher)
3. Even if the developer decides to make two versions, it will be very taxing and people will have to wait longer for the mod to be updated every update.
So yeah. Just wait for the mod API in 1.4, it isn't a long time. Have some patience.
Oh, and I found a funny seed that might be caused by this mod. Seed is:
BLAGH
The seed spawns you in an ocean biome, but underwater D=
1. Forge and Optifine are compatible, you just lack the ability to read. Both threads tell you to install Forge first, then Optifine. That's causing your issues.
2. A non-issue, for the most part. This is, again, part of why the only modloader most people recognize is Forge Modloader.
3. The mod API isn't in 1.4, Jeb announced that a few weeks back. It's not even planned for 1.5.
I'd doubt a 1.2.5 version exists since this mod is new. If there was, though, Redpower 2 required Forge back when it was alive, which this doesn't exactly play nice with yet.
It seems i got the bad hat from minecraft then :-(
Over the last week i created more than 40 worlds. And 80% of them had large snow biomes.
Maybe i should try disabling some of the vanilla biomes? Reducing the size of the hat pool and increasing the chance of getting some of the beautiful EBXL biomes?
This is pretty much how Minecraft has been for me since 1.2.5, even without EBXL. It completely turned me away from large biomes because, due to the already gigantic size of snow biomes, it basically meant that within a 6,000x6,000 block map, I either had too much of it covered by snow, or no snow at all.
I think this is because, by default, snow biomes seem to be considerably larger than base game biomes, like how swamps were when they were first introduced, and like oceans have been since 1.8.
I -kinda- understand why, if that is the case. Think about it, of all the biomes, snow biomes probably have the ugliest biome transitions. Snow on desert, snow on jungle trees, snow on the swamp... so maybe they were made bigger so you had more spots to build in where you wouldn't have to see the tacky transition.
It's not a matter of being selfish. Unless I've misread, Forge and Biomes 'O Plenty are incompatible.
Also, it's not the only mod with this problem. I know that at least Minecraft Comes Alive won't be using Forge, and I think TMI and Timber are like that.
They aren't incompatible, in fact with a bit of jury rigging others have gotten it to work with Forge without removing any content. The decision to not support Forge is entirely due to TDWP's opinion on Forge, and not due to compatability issues.
Also TMI and most other major mods do support Forge. The only mods I know off the top of my head that don't are mods that, for the most part, aren't compatible with anything anyway. Better Than Wolves (which proudly boasts that it's incompatible with everything), Evil Minecraft (not even compatible with Optifine last I checked), and Minecraft Comes Alive (but hey, we've got Millenaire instead, which is, in my opinion, far better.)
If your using Optifine, it is actually an easy fix for the zombies. Just cropthe zombie immage files in the pack to be 128 pixels tall, and everything works just fine.
With how easy this fix is to make the pack compatable with optifine, I don't know why the author refuses to do it. ¬_¬
Other than that, this is a visually spectacular pack, and one of my favorites.
It's because, despite the wall of text between our posts, Misa's been a vocal hater of Optifine. Shame, it's a nice texture pack, but it gets bugs now and then that don't get fixed because someone still clings to MCPatcher and refuses to accept that Optifine does everything MCPatcher does, only more, and better.
Some people are just stubborn and refuse to move onto new and better things, like people that stick to an old version of a browser and refuse to ever update it.
screenshots look really nice. but not being compatible with forge and multiplayer? on 1.3.x where even singleplayer is running internally as multiplayer? ...
I think TheGoldenWarrior is right, either you update to forge or the mod will die (or the Mojang team release API, but since it's been postponed like 3 times I don't see it well).
Mod API's been postponed more than that. I remember back during either late, late alpha or early beta when Notch threatened to charge for the license for it, then took it back. The API is just something that gets promised each version, kinda like how Herobrine gets "removed" each version.
At least we have flower pots now! They're so much more important than the long delayed API and lighting fixes.
It states in the OP what version of forge is required for the mod.
I think the confusion comes from the newest BWG3 saying "modloader users". It's easy to forget that there's a modloader that isn't Forge's, since pretty much everything is Forge compatible now.
Well, I must say, that's the entire point of forge. To make base edits on behalf of modders. But there's no point trying to convince you if you don't want to.
This is why most mods use Forge nowadays. Sadly this is one of the only two mods I know without support for it (the other being Evil Minecraft I think? I remember it doesn't even support Optifine, which is a shame since performance with that was awful), so I've gotta keep a separate jar for it. There's literally no reason to not use Forge anymore.
Still, just means that I can't use things like Millenaire in conjunction with this. Saddens me a bit because it'd be neat to have a Japanese village in the cherry blossom biome, something I haven't been able to do since back before YogBox removed EBXL for performance issues.
Ever considered a sort of Peruvian biome? Very green, all valleys and peaks that reach beyond the clouds. The kind of biome you could build a lot of Incan-themed buildings on.
Kinda like the Extreme Hills biome, just a lot taller, and with valleys and a lot of bushes and small trees.
I like to build a lot of Mayan, Aztec, and Incan inspired structures (well, not as much as I do Arab/Egyptian style, but still), but the extreme hills biome just never seemed like the right home for the Incans.
Can we get a way to disable the parasite biome? That's... honestly a really, really awful thing, imo, and kind of a deal breaker for me. I don't want a biome that griefs the land around it.
I'll try moving back, then. I guess the newest BWG3 is broken?
Tested with the previous version of BWG3, works fine now, so it's just some bug with the latest version I guess, either not compatible with either major release of Forge or not compatible with Optifine.
I keep crashing when attempting to make a new world, this is the message I get:
--- BEGIN ERROR REPORT 16be504 --------
Generated 9/29/12 4:51 PM
- Minecraft Version: 1.3.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0, Oracle Corporation
- Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 418540000 bytes (399 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- FML: FML v3.0.196.366 Minecraft Forge 4.1.1.251 Optifine OptiFine_1.3.2_HD_U_B3 5 mods loaded, 5 mods active
FML [Forge Mod Loader] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
Forge [Minecraft Forge] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
mod_TooManyItems [mod_TooManyItems] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
mod_ReiMinimap [mod_ReiMinimap] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
LoginMessage [LoginMessage] ([forge_universal][1.3.2]LoginMessage_v0.4_mpgh.net.zip) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
- LWJGL: 2.4.2
- OpenGL: ATI Mobility Radeon HD 4200 Series GL version 3.2.9704 Compatibility Profile Context, ATI Technologies Inc.
- Is Modded: Definitely; 'forge,fml'
- Type: Client
- Texture Pack: DokuLight.zip
- Profiler Position: N/A (disabled)
java.lang.NoSuchMethodError: va.onGUICreateWorldPress()V
at aoo.a(GuiCreateWorld.java:244)
at apn.a(SourceFile:64)
at aoo.a(GuiCreateWorld.java:397)
at apn.d(SourceFile:112)
at apn.m(SourceFile:100)
at net.minecraft.client.Minecraft.l(Minecraft.java:1482)
at net.minecraft.client.Minecraft.J(Minecraft.java:834)
at net.minecraft.client.Minecraft.run(Minecraft.java:764)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 721ee712 ----------
Tried both the latest Forge and the previous release. Not sure what's causing this. The crash only happens when I go to start a world.
0
1. Forge and Optifine are compatible, you just lack the ability to read. Both threads tell you to install Forge first, then Optifine. That's causing your issues.
2. A non-issue, for the most part. This is, again, part of why the only modloader most people recognize is Forge Modloader.
3. The mod API isn't in 1.4, Jeb announced that a few weeks back. It's not even planned for 1.5.
0
I'd doubt a 1.2.5 version exists since this mod is new. If there was, though, Redpower 2 required Forge back when it was alive, which this doesn't exactly play nice with yet.
0
This is pretty much how Minecraft has been for me since 1.2.5, even without EBXL. It completely turned me away from large biomes because, due to the already gigantic size of snow biomes, it basically meant that within a 6,000x6,000 block map, I either had too much of it covered by snow, or no snow at all.
I think this is because, by default, snow biomes seem to be considerably larger than base game biomes, like how swamps were when they were first introduced, and like oceans have been since 1.8.
I -kinda- understand why, if that is the case. Think about it, of all the biomes, snow biomes probably have the ugliest biome transitions. Snow on desert, snow on jungle trees, snow on the swamp... so maybe they were made bigger so you had more spots to build in where you wouldn't have to see the tacky transition.
0
They aren't incompatible, in fact with a bit of jury rigging others have gotten it to work with Forge without removing any content. The decision to not support Forge is entirely due to TDWP's opinion on Forge, and not due to compatability issues.
Also TMI and most other major mods do support Forge. The only mods I know off the top of my head that don't are mods that, for the most part, aren't compatible with anything anyway. Better Than Wolves (which proudly boasts that it's incompatible with everything), Evil Minecraft (not even compatible with Optifine last I checked), and Minecraft Comes Alive (but hey, we've got Millenaire instead, which is, in my opinion, far better.)
0
Better Skies support is being added, and there's nothing wrong with Optifine's CTM.
0
It's because, despite the wall of text between our posts, Misa's been a vocal hater of Optifine. Shame, it's a nice texture pack, but it gets bugs now and then that don't get fixed because someone still clings to MCPatcher and refuses to accept that Optifine does everything MCPatcher does, only more, and better.
Some people are just stubborn and refuse to move onto new and better things, like people that stick to an old version of a browser and refuse to ever update it.
0
Mod API's been postponed more than that. I remember back during either late, late alpha or early beta when Notch threatened to charge for the license for it, then took it back. The API is just something that gets promised each version, kinda like how Herobrine gets "removed" each version.
At least we have flower pots now! They're so much more important than the long delayed API and lighting fixes.
0
I think the confusion comes from the newest BWG3 saying "modloader users". It's easy to forget that there's a modloader that isn't Forge's, since pretty much everything is Forge compatible now.
0
This is why most mods use Forge nowadays. Sadly this is one of the only two mods I know without support for it (the other being Evil Minecraft I think? I remember it doesn't even support Optifine, which is a shame since performance with that was awful), so I've gotta keep a separate jar for it. There's literally no reason to not use Forge anymore.
Still, just means that I can't use things like Millenaire in conjunction with this. Saddens me a bit because it'd be neat to have a Japanese village in the cherry blossom biome, something I haven't been able to do since back before YogBox removed EBXL for performance issues.
0
Your anti-virus sucks. Switch to Microsoft Security Essentials. It's free, and is the best anti-virus program that isn't called Kaspersky.
0
Kinda like the Extreme Hills biome, just a lot taller, and with valleys and a lot of bushes and small trees.
I like to build a lot of Mayan, Aztec, and Incan inspired structures (well, not as much as I do Arab/Egyptian style, but still), but the extreme hills biome just never seemed like the right home for the Incans.
0
0
Tested with the previous version of BWG3, works fine now, so it's just some bug with the latest version I guess, either not compatible with either major release of Forge or not compatible with Optifine.
0
I'll try moving back, then. I guess the newest BWG3 is broken?
0
It does not or it does work?
I keep crashing when attempting to make a new world, this is the message I get:
Generated 9/29/12 4:51 PM
- Minecraft Version: 1.3.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0, Oracle Corporation
- Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 418540000 bytes (399 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- FML: FML v3.0.196.366 Minecraft Forge 4.1.1.251 Optifine OptiFine_1.3.2_HD_U_B3 5 mods loaded, 5 mods active
FML [Forge Mod Loader] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
Forge [Minecraft Forge] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
mod_TooManyItems [mod_TooManyItems] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
mod_ReiMinimap [mod_ReiMinimap] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
LoginMessage [LoginMessage] ([forge_universal][1.3.2]LoginMessage_v0.4_mpgh.net.zip) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available
- LWJGL: 2.4.2
- OpenGL: ATI Mobility Radeon HD 4200 Series GL version 3.2.9704 Compatibility Profile Context, ATI Technologies Inc.
- Is Modded: Definitely; 'forge,fml'
- Type: Client
- Texture Pack: DokuLight.zip
- Profiler Position: N/A (disabled)
java.lang.NoSuchMethodError: va.onGUICreateWorldPress()V
at aoo.a(GuiCreateWorld.java:244)
at apn.a(SourceFile:64)
at aoo.a(GuiCreateWorld.java:397)
at apn.d(SourceFile:112)
at apn.m(SourceFile:100)
at net.minecraft.client.Minecraft.l(Minecraft.java:1482)
at net.minecraft.client.Minecraft.J(Minecraft.java:834)
at net.minecraft.client.Minecraft.run(Minecraft.java:764)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 721ee712 ----------
Tried both the latest Forge and the previous release. Not sure what's causing this. The crash only happens when I go to start a world.