Minecraft Forums

Quote from begothprincess

Any time I try to chop a tree (with treecapitator installed), my axe switches out to any other object on my bar. I cant use axe's at all. I havent tried with pickaxe's yet on stone and such but yeah... I dont know what could be going on. Its turned on I pressed F10 and it said it was working, but it keeps swapping from my Axe when i wanna chop wood.

I know you just started using my mods (you said so), so read the bottom of this post.

Quote from Asaru_Darkrose

This has just started to happen with me as well.

If anyone can help out, as I'm sure the mod creators/updaters are very busy, I'd be very grateful, but in the meantime I shall attempt to invoke the help of the mighty thebombzen by sending a debug report as he ask in the FAQs.

HERE IS WHAT I SENT THEBOMBZEN -



"I know you're incredibly busy with mod updates and real life so first I'd like to thank you for building and updating your mods.
Recently - the past week I guess - AS has decided to stop working when it comes to chopping down trees. It works on everything else that I've tested: stone, coal, sand, mobs etc. I also have the Treecapitator mod installed but the two mods have never conflicted for me until now.

I did try looking through the config file to see if I could work out how to fix it myself but I know nothing about programming. I also reinstalled MC and all my mods which I shall list here, but it didn't help.

Forge 1.7.2


Too Many Items 1.7.2


Thebombzen API v2.4.1 for MC 1.7.2


AutoSwitch v5.0.2 for MC 1.7.2



• bspkrsCore Universal 6.11
• Treecapitator Universal 2.0.3 (I think this might be where the problem lies)

I uploaded a debug report on Pastebin just as you said to do: http://pastebin.com/MwgpYJVY"

This problem has been resolved already, earlier in the thread. Also, that is not the most recent version of AutoSwitch. In this case, it shouldn't matter because 5.0.3 only changed keybindings. Read the bottom of this post. If you refuse to update then I'll eventually refuse to help you.
Also, "Forge 1.7.2" is so vague it's practically meaningless. Give the forge version number.

Quote from iiTzTiGeR

Same here.

http://pastebin.com/gbBGdkfV

This problem has been resolved already, earlier in the thread. See the bottom of this post.

Quote from Nirealto

Need some help, is it possible to disable AS just for wooden axe?

No, AutoSwitch cannot temporarily disable itself based on your current item, because that would defeat the entire idea of picking the best tool independent of your current item. See the bottom of this post.

Quote from iiTzTiGeR

When chopping trees just hit F10 to disable it temporarily. When finish chopping your tree hit F10 again to turn AS back on.

This problem has been resolved already, earlier in the thread. See the bottom of this post.

Quote from Nirealto

I know about this function, but i need to disable only wood axe, forever.

This problem has been resolved already, earlier in the thread. See the bottom of this post.

Quote from Coolrivenjosh_25

Hey mine can't change!!! when i pick the axe the it change too hand (when i'm Chopping wood) any kind?????pls help me!!!!!!!! message back pls!!! fast Auto Switch mod

Using more punctuation marks will not make me want to help you any more.

Quote from Coolrivenjosh_25

Like mine too i have treecapitator installed it switch too any object

This problem has been resolved already, earlier in the thread. See the bottom of this post.

=========================================================================================

Here is a complete, verbose, full, entire explanation of why this problem exists and how to fix it.

1. TreeCapacitator changes your axe's digging speed on logs. TreeCapacitator has an anti-feature where it tries to "balance" itself by making axes chop wood just as slowly as any generic item. This is an anti-feature because TreeCapacitator is so monstrously fast at gathering wood when compared to normal woodcutting that changing the dig speed won't balance it significantly. Try multiplying your wood-gathering ability by 30, and then making it a little slower. This is exactly what this anti-feature does.

2. AutoSwitch uses the actual digging speed in its calculation, not any preprogrammed notion of "proper tool." One of the fundamental principles of the way AS is programmed is that it's designed to work as well as possible with any modded-in tools or blocks, out of the box. One of the ways it does this is that it doesn't store any precalculated values of what the proper tool is for a block. AutoSwitch calculates this all on-the-fly, with every new block, because this way it never runs into the issue that two compatible mods are incompatible with respect to AutoSwitch. This also means that when mods change a tool's or block's behavior, AutoSwitch notices and uses the new values, not the old values.

(1) & (2) => 3. AutoSwitch treats axes as if they dig equally fast as any generic item. This is because with TreeCapacitator installed, they actually do dig equally fast as any generic item.

4. AutoSwitch takes other factors into account, not just digging speed. Notably, it takes damageability into account. In fact, the chief way that AutoSwitch distinguishes an improper tool from a generic item is whether the item is damageable. If the item is not damageable, then to AutoSwitch's algorithm, it's effectively a generic item.

5. "Improper tools" are generic items that are damageable. This is a definition that's used in AutoSwitch's algorithm.

(4) & (5) => 6. Improper tools are strictly worse than generic items that are not other improper tools. (This is the way I've implemented the algorithm using my priorities.)

7. Axes take damage when they cut wood. (Self-explanatory.)

(3) & (5) & (7) => 8. Axes are improper tools. (3) states that axes are generic items. (7) states that axes are damageable. (5) states that improper tools are generic items that are damageable. Therefore, axes are improper tools, at least on logs.

(6) & (8) => 9. Axes are strictly worse than generic items that are not other improper tools.

(9) => 10. AutoSwitch will switch away from axes (on logs) toward any generic item which is not an improper tool.



=========================================================================================

How To Fix It

Notice that everything we did relied on statement (1), that TreeCapacitator changes your axe's digging speed. This proof breaks down if TreeCapacitator does not change your axe's digging speed. In fact, a necessary condition for AS to not switch away from your axes on logs is for TreeCapacitator to not change your digging speed.

Final Solution: Configure TreeCapacitator so it doesn't change your axe's digging speed. Q.E.D.

Quote from thebombzen

Don't use it. EnchantView v4.0.3 was not designed to work in 1.7.10. Because of the way I programmed EnchantView, I have to update it for every minor update.

In the meantime I was able to compile a 1.7.10 version by myself. The fix was really simple and you will find that information also on GitHub.
Should I generate a pull request to document my changes?
I assume your changes will be slightly different while adapting the version numbers.

Quote from Mc_Etlam

In the meantime I was able to compile a 1.7.10 version by myself. The fix was really simple and you will find that information also on GitHub.
Should I generate a pull request to document my changes?
I assume your changes will be slightly different while adapting the version numbers.

If anyone wants to work on EnchantView or AutoSwitch or something else, feel free to work on it using Github's features. I reserve the right to accept or reject anything but if people have a quick fix for a small thing feel free. I'm a nice person; I'll probably accept it. (After all, that's what Open-Source Software is about! :D)

Quote from Gregrs

1. Yes, it most definitely should. This was my favorite mod pack in 1.0.0/1.1. It was really useful because if you were going to spend say 50 levels on a picaxe, you might as well get something that is decent.

2. tbh, I wouldn't use this if I ever made a server. Seems a bit to overpowered.

3. Not really a suggestions, but please try and make it exactly like the version in 1.0.0. How you saw every enchantment.

Server-side only just means it can work out-of-the box as a server mod just as if it were a client mod. Remember, SSP is a local server so it would work there too.

Quote from crunkazcanbe

Could you be as so kind to please fix the ol versions link for World And Generation Tweaks mod. Please! Lookig for the 1.6.4 version

It's fixed now

I moved it internally from something/WorldAndGenerationTweaks to something/mods/WorldAndGenerationTweaks to reduce clutter. I accidentally broke the link. Oops.

Hey guys! I just added an update to AutoSwitch that specifically adds compatibility with Tinkers Construct weapons. Have fun tinkering!

Quote from Demikun

However, u forgot to change the Download link i guess, i still can only download the old 5.0.2 Version

Oops! Fixed now.

AutoSwitch and EnchantView are both for 1.7.10 yet the API they require to run is still 1.7.2, is this a lack of link update or are you actually behind on updating ThebombzenAPI.....?

Quote from KuramaKyuubi

AutoSwitch and EnchantView are both for 1.7.10 yet the API they require to run is still 1.7.2, is this a lack of link update or are you actually behind on updating ThebombzenAPI.....?

All the mods work on both 1.7.2 and 1.7.10, except EnchantView, which requires the specific version. I'll add some text below each mod that says "works in both"

Wha... when did EnchantView update?! I've been checking (new posts) for ages!

Just to be sure, the Bukkit plugin is compatible through versions up to / including 1.7.10...?

Edit: Nope, errors for days. Awww...

http://pastebin.com/2LxizZch
Minecraft 1.7.10 stucked while "Downloading terrain" with ThebombzenAPI v2.4.1 and DamageIndicatorsMod 3.2.0 and OpenEye 0.6 and Forge 10.13.0.1180.
Then game crashed.
EDIT: Crash Report: http://pastebin.com/bGbP3v4c

Server Crash on Mob Aura. I am loading The Bombzen Mods for the first time, so all downloads are fresh. I have searched the crash report, per the FAQ. I have also looked at all entries for "TheBombzenAPI" and found not other class errors. Tried both the execute jar installation process and drop in with the BombzenAPI methods referenced in the Installation instructions.

Loaded components:

Minecraft 1.7.10
Forge 1.7.10-10.13.0.1205 (This is NOT the recommended version. Recommended is 10.13.0.1188, latest is 10.13.0.1207. I have a mod requiring 10.13.0.1199, so I am updating incrementally based on the specific bug fixes post 1199 in the forge changelog.)
ThebombzenAPI-v2.4.1-mc1.7.2.jar
MobAura-v2.7.1-mc1.7.2.jar

Crash report: http://pastebin.com/p7WVib11

Any help is greatly appreciated!

Quote from Slaymeister

Minecraft 1.7.10
Forge 1.7.10-10.13.0.1205
ThebombzenAPI-v2.4.1-mc1.7.2.jar
MobAura-v2.7.1-mc1.7.2.jar

Might be from using 1.7.2 mods with 1.7.10 Forge.

Quote from yhylord

http://pastebin.com/2LxizZch
Minecraft 1.7.10 stucked while "Downloading terrain" with ThebombzenAPI v2.4.1 and DamageIndicatorsMod 3.2.0 and OpenEye 0.6 and Forge 10.13.0.1180.
Then game crashed.
EDIT: Crash Report: http://pastebin.com/bGbP3v4c

That's not a problem with anything that I wrote. (None of my things are mentioned in the crash log other than "this thing was loaded.")

I recommend updating forge to the Latest version, then trying again.

Quote from Slaymeister

Server Crash on Mob Aura. I am loading The Bombzen Mods for the first time, so all downloads are fresh. I have searched the crash report, per the FAQ. I have also looked at all entries for "TheBombzenAPI" and found not other class errors. Tried both the execute jar installation process and drop in with the BombzenAPI methods referenced in the Installation instructions.

Loaded components:

Minecraft 1.7.10
Forge 1.7.10-10.13.0.1205 (This is NOT the recommended version. Recommended is 10.13.0.1188, latest is 10.13.0.1207. I have a mod requiring 10.13.0.1199, so I am updating incrementally based on the specific bug fixes post 1199 in the forge changelog.)
ThebombzenAPI-v2.4.1-mc1.7.2.jar
MobAura-v2.7.1-mc1.7.2.jar

Crash report: http://pastebin.com/p7WVib11

Any help is greatly appreciated!

Well, what did you expect to happen when you installed a client-side only mod on the server?

I mean, it says so right there in the crash log:

Attempted to load class thebombzen/mods/mobaura/MobAura for invalid side SERVER

Using Minecraft Forge 13.10.0.1280, still stucked: http://pastebin.com/mHaLuuPt

But after removing Thebombzen API, everything is fine.

Quote from yhylord

Using Minecraft Forge 13.10.0.1280, still stucked: http://pastebin.com/mHaLuuPt

But after removing Thebombzen API, everything is fine.

There must be something wrong on your end. I can use Forge 1205, ThebombzenAPI 2.4.1, DamageIndicators 3.2.0, and OpenEye 0.6 all together without crashing. I just can't reproduce the crash you're experiencing. I also tried forcing them to load in exactly the same order as you did, but no luck.

It appears that something is causing your Minecraft to lag heavily when you load a world (8 seconds for 1 tick) before it finally crashes. The world does load and it does add your player entity, but something's wrong with the ticking.

I would do more diagnostics, such try it with all 2^3 subsets of the 3 mods, and see which ones work and which ones don't. Maybe then I can get a handle on this.

I know it's annoying to ask... but now we have 1.7.10 EnchantView client, is a Bukkit update possible too?

(feel free to remove this if unwanted)