Jeebus Flowerchild. There were two polite, calmly worded bug reports. The only one "freaking the out " is you.
No one is making farms out of it, because the behavior is also that it doesn't give seeds. You were able to make a very slow pulsing signal out of a wheat and a bud before this change.
If your intended behavior is that it harvest each crop in a uniquely quirky way, that's cool. But there's no need to be snarky when I was just clairifying that it is quirky in the way it harvests wheat vs. hemp. The only reason I posted it is that you dismissed out of hand the first bug report.
If all you have installed is ModLoader and BTW, there's very little that can go wrong.
I'd advise downloading a fresh install of MC and start installation over from scratch. Plenty of people are obviously using it without issue, but every once and awhile, installs go wonky and starting fresh is the way out of that.
As I noted in the first post I installed with a fresh copy of MC, installed mcpatcher first then mod loader and after that installed BTW, I also tested the game after each install and all was working until BTW was installed.
--- BEGIN ERROR REPORT d36f2c98 --------
Generated 11/12/12 11:35 AM - Minecraft Version: 1.4.2
- Operating System: Windows XP (x86) version 5.1
- Java Version: 1.7.0_09, Oracle Corporation
- Java VM Version: Java HotSpot™ Client VM (mixed mode), Oracle Corporation
- Memory: 486702232 bytes (464 MB) / 519110656 bytes (495 MB) up to 1037959168 bytes (989 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- ModLoader: Mods loaded: 2
ModLoader 1.4.2
mod_FCBetterThanWolves 4.33 - LWJGL: 2.4.2
- OpenGL: ATI Radeon HD 5450 GL version 4.1.11005 Compatibility Profile Context, ATI Technologies Inc.
- Is Modded: Very likely
- Type: Client
- Texture Pack: Default
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: ~ERROR~ NullPointerException: null java.lang.IllegalAccessError: tried to access field axx.a from class net.minecraft.client.Minecraft
at net.minecraft.client.Minecraft.getWorld(SourceFile)
at net.minecraft.client.Minecraft.J(SourceFile:558)
at net.minecraft.client.Minecraft.run(SourceFile:534)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 19f44ce9 ----------
how does one "install" mcpatcher? do you mean you used the features such as HD font and such? If so, uncheck all MCpatcher's features except HD fonts and HD textures, as those are the only 2 i know for sure play nicely with BTW, and the others (like connected textures) can cause it to break.
As for the load order, make sure modloader is on top (make sure it's latest version), then BTW right below it (latest version), and then HD textures and fonts below that, then hit patch. That has never given me install issues.
Obviously you should start with a clean install of minecraft, preferably deleting the entire .minecraft folder (but back up your world saves first!), then installing using MCpatcher from there.
Also, make sure the directory for BTW using mcpatcher is set to the minecraft jar folder, not the entire thing. Forge source and minecraft server jar aren't things you want to install, just the minecraft jar folder.
Jeebus Flowerchild. There were two polite, calmly worded bug reports. The only one "freaking the out " is you.
The reason I'm "freaking out" about it is that I take bug reports seriously, and it seriously gets under my skin when people report frivolous or erroneous ones as a result.
In this particular case, not only was the behavior reported desirable, but there was the distinct impression that people had been using the previous behavior as an exploit without ever reporting it as such, then when it went away due to a change on Mojang's part they decided that they wanted me to "fix" that.
That's just not cool man. I obviously put a lot of work into the mod and keeping it balanced, and when I get the impression parts of the community are working against me by keeping these kinds of issues hidden so that they can continue to abuse them, or sneak a bug-report in like this while trying not to give away why it's important to them to begin with, it's a rather frustrating experience.
Nobody would have ever reported this if they weren't using it to begin with. Given that I can't think of a single legitimate use for it, I think that their motives then become rather clear.
EDIT: Nm, this just got cleared up in the thread I created about it, and it was my mistake. Turns out there was a legitimate use for it that I hadn't considered.
As I noted in the first post I installed with a fresh copy of MC, installed mcpatcher first then mod loader and after that installed BTW, I also tested the game after each install and all was working until BTW was installed.
When installing via MCPatcher does it look like this?
and did it give you this message when you pressed patch?
Rollback Post to RevisionRollBack
"Not everyone who has a built a nice chair owes money to the guy that invented chairs"
OK, now that I am loading it via MCpatcher which I suspect is the way it should be done. Rather than manually putting the files in the .jar file with 7-zip.
I am now getting this conflict.
ModLoader1.4
BetterThanWolves
awr.class
Only the files from BetterThanWolves will be used.
OK, now that I am loading it via MCpatcher which I suspect is the way it should be done. Rather than manually putting the files in the .jar file with 7-zip.
I am now getting this conflict.
ModLoader1.4
BetterThanWolves
awr.class
Only the files from BetterThanWolves will be used.
CRAP.... Still no joy :/
That's supposed to happen as BTW overwrites several ModLoader classes (while still maintaining ModLoader functionality). Just press Yes and it *should* work.
Just deleted my .minecraft folder and downloaded new MC, patched with mcpatcher making sure modloader is first then BTW, again I have the conflict error and have the black screen of death. :/ What the heck am I doing wrong!?!?!?
That's supposed to happen as BTW overwrites several ModLoader classes (while still maintaining ModLoader functionality). Just press Yes and it *should* work.
"should" being the operative word here.. LOL. I'm really normaly pretty good at this kind of stuff. :/
Just deleted my .minecraft folder and downloaded new MC, patched with mcpatcher making sure modloader is first then BTW, again I have the conflict error and have the black screen of death. :/ What the heck am I doing wrong!?!?!?
make sure mcpatcher is the newest version, I use mcpatcher-2.4.3_03 without any issues. The latest mcpatcher is 2.4.3_04 but _03 works fine.
Hilarious, he ports to modloader, and now everybody uses forge. Oh the irony.
I "ported" to Modloader around a year and a half ago. I left Forge because I no longer wanted to use it, not because I was trying to convince others to do the same.
I suppose the irony could be that people are still responding to posts on the first page of a 1500 page thread as though they were posted this morning...
Hey Flower Child, I love your mod so much! I even got everyone in my friend's (small) SMP server to download it for Lan Servers!
I was wondering something though...
I'm making a mod that lets you have skeleton guards by necromancy...and I am having the hardest time with the Altar, it is similar to your anvil in that it is purely for crafting with a larger Slot GUI (3x4) but it is 2 blocks long and I can't figure out a way to have it generate when placed...or rather, I may not know what such an item would be called to search up a tutorial for it.
Any help what so ever would be very appreciated...
I'm making a mod that lets you have skeleton guards by necromancy...and I am having the hardest time with the Altar, it is similar to your anvil in that it is purely for crafting with a larger Slot GUI (3x4) but it is 2 blocks long and I can't figure out a way to have it generate when placed...or rather, I may not know what such an item would be called to search up a tutorial for it.
Sorry man, getting into something like that would be rather involved and beyond what I am willing to do.
I also don't have a tutorial I can point you to as I haven't looked at one since the first "how to make a basic MC block" one I skimmed over a year and a half ago. I generally figure out everything on my own.
I will say though that creating custom GUIs is a rather advanced modding topic, and if this is your first mod, you're probably better off starting with something much simpler.
No one is making farms out of it, because the behavior is also that it doesn't give seeds. You were able to make a very slow pulsing signal out of a wheat and a bud before this change.
If your intended behavior is that it harvest each crop in a uniquely quirky way, that's cool. But there's no need to be snarky when I was just clairifying that it is quirky in the way it harvests wheat vs. hemp. The only reason I posted it is that you dismissed out of hand the first bug report.
As I noted in the first post I installed with a fresh copy of MC, installed mcpatcher first then mod loader and after that installed BTW, I also tested the game after each install and all was working until BTW was installed.
--- BEGIN ERROR REPORT d36f2c98 --------
Generated 11/12/12 11:35 AM
- Minecraft Version: 1.4.2
- Operating System: Windows XP (x86) version 5.1
- Java Version: 1.7.0_09, Oracle Corporation
- Java VM Version: Java HotSpot™ Client VM (mixed mode), Oracle Corporation
- Memory: 486702232 bytes (464 MB) / 519110656 bytes (495 MB) up to 1037959168 bytes (989 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- ModLoader: Mods loaded: 2
ModLoader 1.4.2
mod_FCBetterThanWolves 4.33
- LWJGL: 2.4.2
- OpenGL: ATI Radeon HD 5450 GL version 4.1.11005 Compatibility Profile Context, ATI Technologies Inc.
- Is Modded: Very likely
- Type: Client
- Texture Pack: Default
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: ~ERROR~ NullPointerException: null
java.lang.IllegalAccessError: tried to access field axx.a from class net.minecraft.client.Minecraft
at net.minecraft.client.Minecraft.getWorld(SourceFile)
at net.minecraft.client.Minecraft.J(SourceFile:558)
at net.minecraft.client.Minecraft.run(SourceFile:534)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 19f44ce9 ----------
As for the load order, make sure modloader is on top (make sure it's latest version), then BTW right below it (latest version), and then HD textures and fonts below that, then hit patch. That has never given me install issues.
Obviously you should start with a clean install of minecraft, preferably deleting the entire .minecraft folder (but back up your world saves first!), then installing using MCpatcher from there.
Also, make sure the directory for BTW using mcpatcher is set to the minecraft jar folder, not the entire thing. Forge source and minecraft server jar aren't things you want to install, just the minecraft jar folder.
The reason I'm "freaking out" about it is that I take bug reports seriously, and it seriously gets under my skin when people report frivolous or erroneous ones as a result.
In this particular case, not only was the behavior reported desirable, but there was the distinct impression that people had been using the previous behavior as an exploit without ever reporting it as such, then when it went away due to a change on Mojang's part they decided that they wanted me to "fix" that.
That's just not cool man. I obviously put a lot of work into the mod and keeping it balanced, and when I get the impression parts of the community are working against me by keeping these kinds of issues hidden so that they can continue to abuse them, or sneak a bug-report in like this while trying not to give away why it's important to them to begin with, it's a rather frustrating experience.
Nobody would have ever reported this if they weren't using it to begin with. Given that I can't think of a single legitimate use for it, I think that their motives then become rather clear.
EDIT: Nm, this just got cleared up in the thread I created about it, and it was my mistake. Turns out there was a legitimate use for it that I hadn't considered.
When installing via MCPatcher does it look like this?
and did it give you this message when you pressed patch?
Yes that was what I meant by "install". I guess patch would have been better.
No I did not give me any conflict screens.
The only way that would happen is if you didn't select the MINECRAFT-JAR folder when you added the BTWMod4-33 file to the initial mod list.
You need that conflict window to confirm you're overwriting some of the Modloader files with the versions that BTW expects and uses.
I am now getting this conflict.
ModLoader1.4
BetterThanWolves
awr.class
Only the files from BetterThanWolves will be used.
CRAP.... Still no joy :/
That's supposed to happen as BTW overwrites several ModLoader classes (while still maintaining ModLoader functionality). Just press Yes and it *should* work.
"should" being the operative word here.. LOL. I'm really normaly pretty good at this kind of stuff. :/
make sure mcpatcher is the newest version, I use mcpatcher-2.4.3_03 without any issues. The latest mcpatcher is 2.4.3_04 but _03 works fine.
I was using "03" so I download the latest and started all over.... STILL NO JOY!! Still have the black screen of death.
I "ported" to Modloader around a year and a half ago. I left Forge because I no longer wanted to use it, not because I was trying to convince others to do the same.
I fail to see the irony you're speaking of.
Yeah, I have to agree that part is pretty ironic
No.
I was wondering something though...
I'm making a mod that lets you have skeleton guards by necromancy...and I am having the hardest time with the Altar, it is similar to your anvil in that it is purely for crafting with a larger Slot GUI (3x4) but it is 2 blocks long and I can't figure out a way to have it generate when placed...or rather, I may not know what such an item would be called to search up a tutorial for it.
Any help what so ever would be very appreciated...
Sorry man, getting into something like that would be rather involved and beyond what I am willing to do.
I also don't have a tutorial I can point you to as I haven't looked at one since the first "how to make a basic MC block" one I skimmed over a year and a half ago. I generally figure out everything on my own.
I will say though that creating custom GUIs is a rather advanced modding topic, and if this is your first mod, you're probably better off starting with something much simpler.