-
Notifications
You must be signed in to change notification settings - Fork 0
[2.2.14.67] Creative Jetpack Continually "Charges" until it overflows and becomes "depleted" #422
Comments
Flux networks wireless inventory charging has unlimited range, so if you have enabled it, it is charging the jetpack. You probably could see it from the controller, where you can see where power comes/goes per connection. |
I didn't know that, but we turned off the wireless charging for armor
slots, because it emptied our power within a couple minutes.
So Flux Networks shouldn't play into it any longer.
…On Sun, Apr 5, 2020, 09:12 ByteTemplar ***@***.***> wrote:
Flux networks wireless charging has unlimited range, so if you have
enabled it, it is charging the jeptpack. You probably see it from the
controller, where you can see where power comes/goes per connection.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#422 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3XPS4GTKMVHFEHB6FDIRDRLCGVFANCNFSM4L74IC4A>
.
|
I did notice, the wireless charging GUI is bit buggy and even if you enable/disable something, it might revert back the settings randomly. So check if its still on again... Is that one bauble (next to magnet) an EnderIO Inventory Charger? Hard to say from the picture... |
Alright, I numbered the items, just so that it's available.
Looking at the items, I'm willing to bet that it's probably from the Solar on the helm. But shouldn't a "Creative" item never accept energy? If you want logs, or a mod list or anything else I would be more than happy to help |
It is a bug that the Creative jetpack accepts energy, it was never meant to be available for normal play, so there are many weird behaviors. |
@adam9899 the mod author has been informed. This issue can be closed. |
The percentage of charge within the jetpack continually goes up. I have no items that should be attempting to charge the jetpack, and I'm not within range of a Flux Networks node.
Currently occurring in MC Eternal 1.3.5b, Minecraft 1.12.2
The text was updated successfully, but these errors were encountered: