Big Reactors

Big Reactors

11M Downloads

Inserting yellorium without shiftclick can cause ghost items

matix931 opened this issue · 20 comments

commented

For example, if you have fresh empty reactor then you insert some of yellorium into, items will be consumed but it will still exists, then you have to close and open gui to refresh.

commented

Which version of Forge and Big Reactors are you using? This sounds like a networking issue.

commented

Also, just an offhand guess - does this happen only in SMP, only in SSP, or in both?

commented

Seems to be only SMP issue, i am using Big reactors 0.4.0 RC8 and forge .1208 / .1217

commented

So, just to clarify, this is what you're doing:
(Precondition: Have a new reactor with empty fuel tanks and some yellorium in your inventory.)
Step 1: Open access port GUI.
Step 2: Click on yellorium in inventory to pick it up.
Step 3: Click on access port intake slot in GUI. Do not have Shift held down.
Step 4: Yellorium drops into the intake slot and does not disappear. Fuel rods visually appear full and, on server, yellorium is actually consumed from the intake slot.
Step 5: Close access port GUI and reopen it. Yellorium in the intake slot has properly disappeared.

Does that sound correct?

Does this happen only if you don't have excess yellorium? If you have excess, does the stack size update properly, or does that also not change?

commented

if you have excess yellorium, proper amount stays in input slot, but whole ghost item stack stays on mouse, you can place it in your inventory, but after closing gui it disappers.

Suming everything, placing items using mouse in input slot don't decrase amount of items holded on cursor.
Items inside intake slot are only refreshing if you have excess amount.

commented

I'm unable to reproduce this on a standard Forge server running MC 1.7.10/Forge 1217 with BR 0.4.0rc8 and CoFHCore 3.0.0B6. I strongly suspect this is a problem involving your specific server and/or network. Does it happen to other players on your server as well?

commented

I don't use much of their code for the reactor; that's almost all stock. Do you know what versions of CoFHCore were being used before and after the update?

commented

It was happening to me with machines from ThermaExpansion. I do not know how much code you use form CoFHCore but it might be sync issue on their part. If you are not using their code you might look into their recent commits because it fixed itself after server update.

commented

I can only ask @marcin212 and will.

commented

I have that problem with thermal expansion machines too and it is not fixed for me in latest versions.

commented

This is almost certainly a problem with your network connection or server, as the slot inventory handling is all stock vanilla code.

Can you reproduce this with furnaces, beacons or other vanilla UIs?

commented

No, i cant

commented

Thanks. I'll look at this tonight. Is there somewhere I can download your clientside modpack as well?

commented

Hmm. Can you reproduce this only on your normal server? Can you try with a different server?

commented

Same on my server and my friend.
I can upload whole server if you want to test it.

@edit
Separated server files and world:
http://www.sendspace.com/filegroup/f9dvhfYliwlXx0OLaAt22w

commented

Nope, there isnt, just copy mods and config from server.

commented

@marcin212 and I found out that it is most probably due to InventoryTweaks.

commented

Interesting. I'll have to consult them. May I ask how you arrived at this
conclusion?
On Sep 27, 2014 4:31 PM, "Kubuxu" [email protected] wrote:

@marcin212 https://github.com/marcin212 and I found out that it is most
probably due to InventoryTweaks.


Reply to this email directly or view it on GitHub
#330 (comment)
.

commented

Sorry for wrong information. Without any change in modpack the bug is back. We have no idea why it fixed it self and no it is back. We removed InvTweaks as there were big issues with ghost items or invisible items and the ghost items when putting into machines were gone but they are back now.

commented

Just spoke to TeamCoFH. Apparently this is the result of a bug in some core OreDict code which will be resolved in the next CoFHCore release. I do use their OreDict optimizer, which is why this appears in BR.

Once CoFHCore 3.0.0B7 comes out, please update. If the problems persists after the update, please reopen this issue.