-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can't fill the jetpack tank #132
Comments
Does that also happen when breaking it using right-click? |
Oh, I hadn't thought of doing it with a wrench. |
No I meant without a wrench, simply by right-clicking it with an empty hand to pick it up. But wrenching it does work? |
Aaah, I actually grabbed it with the wrench because it wouldn't let me grab it with my hand, or crouching, or without anything. And yes, grabbing it with the wrench seems to work correctly, it doesn't lose air in it. |
I'm experiencing something similar. |
I eventually have recreated it, and it ONLY seems to be filled when you right-click the block with an empty hand and no chestplate armor. |
this would theoretically probably fix an issue where it doesn't properly drop its filled self, the only way to break it filled seems to have been to have it already filled or to use a custom mechanic to break and equip it when right clicked with an empty hand and no back armor on.
I'm not sure and I don't have a testing rig set up, but data merging has never seemed to work well for me and I think it refuses to replace things that are already there if they have certain type differences or something. |
if it is a "merge refuses to replace float with int" issue then the proper action could be to switch the float to an int everywhere, but then keeping track of multiple uses per air value gets complex, and if this does fix the problem then its good enough for me. |
very weird, I just copied what the normal backtank has going on as a loot table, I might have to check again if I made a mistake there |
Ok truly very weird, I can pick it up using a wrench by shift-right-clicking, an empty hand or simply a pickaxe and all of them give me a jetpack with air. |
Yup, all updated. I also noticed a couple more things. -I got netherite jetpacks from the creative, it seems that they only charge correctly the first time, the second time for some reason they don't refill correctly if you break them with the pickaxe. |
my guess is it is because of failure to over-write the float value that the jetpack stores for air (so that you can get multiple uses per air-unit) with the integer value that the backtank fill mechanism uses. |
yes, that is the precise version number I have. |
perhaps it is an incompatibility with another mod I have? |
it is not the jetpack curio mod. just checked |
attempting to test with the changes, but I can't compile presumably because I'm using the wrong java version somewhere. |
attatched is the full gradle init fail debug log... I just pulled up the project in intellij and it had that error right off the bat trying with java 22 as the project java and java 17 as the java that I have on my normal $PATH... |
architectury-9.2.14-forge.jar is my normal full mod list if it helps with figuring out the source of this issue... |
Ok I figured it out, it actually does not have to do anything with floats or integers, both would work fine. It's only caused because the two NBT functions in the loot tables are applied in the incorrect order, they are the other way around for the backtank. |
... so my patch would theoretically work, despite being a bit excessive... |
Anyway, yay!!! |
@j-romchain yep it would also have worked, thank you very much for your investigation and effort |
You are very welcome. Thank you for being an active and freindly open source dev! |
What happened?
Since the last update 4.3.1 it seems that the jetpack filling doesn't work, or at least, when you break it after marking that it's full, when you break it it becomes empty again.
Curiously, with Jade it shows that the tank is full before breaking it.
Loader
forge
Mod Version
4.3.1
Minecraft Version
1.20
Relevant log output
No response
The text was updated successfully, but these errors were encountered: