Hi there,

I've ran into a bug with the meteor shield. Whenever I open up the meteor shield's GUI and try and pull out any ice that's in there, the client crashes as soon as I left click those ice blocks.

Image:

This produces these error logs (one's from my client, the other is from my server)

Client

Server

Some more info

I'm using the ATLauncher to fire up the Resonant Rise 3 modpack (excessive edition), which currently uses Falling Meteors 2.14.1 along with these other mods.
I'm using this client to connect to my own local server which uses McMyAdmin 2 as control panel.

I'm currently using Java 8 Update 25 (64 bit edition).

These are my system specs:
i7 3770k 4 cores @ 3.50 GHz
16 GB DDR3 RAM
EVGA GeForce GTX 780
512 GB SSD
Windows 7 Home Premium SP 1 (64 bit)

I hope this helps you figure out what's wrong. If you need any more additional info, feel free to contact me.

And thanks for the work you put into your mod!

I'm also getting this issue... and discovered another problem/exploit when I attempted to use Ender IO Item Conduits to get around the problem.

Instead of pulling the items collected by the Meteor Shield, they instead pull out infinite Meteor Chips (This is with the shield on and after inserting a chip and 4 Red Meteor Gems).

Ender IO 2.2.7.331 as part of the same pack as Hirsu.

This does not cause a crash or error message, but on the same map I just tested to see if switching between Creative (plus from NEI) and Survival made any change and can no longer duplicate... And it got the ice out without crashing as originally intended though I did manually remove everything else from the shield before removing the full (IRON CHESTS) Obsidian chest and replacing it.

When I first encountered the problem it was after reloading from the ice crash and placing the conduits on the faces of the shield with the "control panels" and the shield had meteor chips in the uppermost left slot of the storage.

Ah!

I figured out how to reproduce it in Creative.

Have the Ender IO conduit attached to the shield before an impact, set the conduit to always active on extract mode, attach a chest to the other side and set that connect as insert.

Upon blocking an impact the first item to appear (in that uppermost left slot) gets infinitely duplicated.

The problem in Hirsu's post has been resolved and will be released in the next update (2.14.2), but I can't seem to replicate Questiondeca's problem. What version of EnderIO are you running? Is there any other information you can give me to help track down this issue?

Did another test on my end, and the error didn't occur...
I have the suspicion it's not a consistent error now, or is dependent on the Hirsu error.

I'll watch for it further.

Error has re-occurred with Meteor chips in top left slot upon stopping an impact after loading the map.

(Block Comets on)

Replacing the conduit did not fix.

Closing and reopening the map did not fix.

Closing and reopening Minecraft did not fix.

Removing the Meteor Chips did fix.

I'll keep watching, if it's not dependent on the Hirsu error, then perhaps specific items in that specific slot.

Not specific items, another meteor with meteor chips did not cause the error, so at the least I can confirm that it's not a consistent issue.

Haha Inconsistency doesn't really help in finding the issue. If I had to guess, the shield does not sync up correctly and causes the conduit to think that it is still there. I'll investigate it a little further.

Another thing, would you mind checking to see if any other mods do the same thing as the EnderIO conduits? Perhaps try buildcraft pipes and thermal expansion pipes. Looking at previous builds of EnderIO, it may be possible that this was fixed a few updates ago.

Will do.

Just discovered something myself. It only happens when there is more than 1 item in the stack of whatever item it is duplicating.

Oh wait! I found it! facepalm I restricted other blocks from actually setting the inventory contents of the shield. So it could never update the stack size of an item if it wanted to. However, it could set it to null. Wow, I knew my item logic would screw me over somewhere. -_-

Thanks for all the help you guys!

Glad to be OF help.