[1.8][SOLVED] Bow Event error?

[NovaViper]

Hey, I noticed the latest 1.8 forge has a bug in it with the bow events. The forge 11.14.0.1281 build doesn't have this bug but builds after this contain this bug. The bug is that when the I charge up a custom bow I made, the textures doesn't work but in the 11.14.0.1281 build, it does work. I extended the custom bow's class to the vanilla code and did nothing else to it but but in a code like this so my textures can work: http://pastebin.com/642ySU7s

 

I placed a debugger line so I can see what variables I am getting as I either hold the bow or charge it up.

From the latest build, I get this: http://pastebin.com/GEen92qq

 

But with the 11.14.0.1281 build I get this: http://pastebin.com/M03F2KmT

 

See how the numbers are different? Not sure why but it's some kind of internal bug within the code since the 11.14.0.1281 build. If these are needed, here are the client logs from both builds:

Latest Build: http://pastebin.com/MZFJYn7P

11.14.0.1281 Build: http://pastebin.com/jsmh0cnG

[LexManos]

https://github.com/MinecraftForge/MinecraftForge/commit/64bf7bb3bef588d414561b638a945e8653df6dc5

Yes this was actually a bug FIX, the value passed in is meant to be the 'usageRemaing' and I was passing in the current usage.

Sorry for the issue, but this is the fix.

[NovaViper]

Ah, so now how I do I modify my code to adjust to this fix?

[LexManos]

yes, stupid i know, but hey better to get it in early in 1.8 and not have to suffer through it for the rest of the version.

[NovaViper]

Yeah, thats true. But not my textures don't work with the latest. How do I fix it now?

[LexManos]

invert your numbers.

Basically instead of counting 0-X it counts X-0 like vanilla bow's textures do.

[NovaViper]

Thanks! I fixed it, I had to do something like this: http://pastebin.com/agm3kUfL