![Stockpile](https://media.forgecdn.net/avatars/thumbnails/164/904/256/256/636689357071663390.png)
One of ten barrels cannot be broken nor filled
Knito58 opened this issue ยท 9 comments
Somehow one of that barrels is desynced. The breaking animation is shown and when the barrel breaks it is placed back immediately - it is undestructable. It is empty and has a clear monitor.
The latest.log has some complaints about a Trashcan which stands nearby.
https://pastebin.com/3vFsJe4C
Thanks for posting your issue. I haven't been able to reproduce this so far after placing and breaking barrels and trash cans in both a dev environment and with the CF release-- what versions of Stockpile and Rift are you using? Can specific steps be used to reproduce the desynced behavior?
I'm using Rift 1.0.3-45 and Stockpile 0.1.1. Sorry for missing this piece of info. I simply stacked a wall of all barrels I could afford and when I wanted to put sand into said barrel it wouldn't work. When trying to replace it that action fails. All the other barrels are fine.
First I tried to put something into the trash bin and went opening and closing the lid. Then I broke it and placed it back. Then the wall of barrels around it. I believe the indestructable barrel is purely random. I even successfully broke a dirt barrel and used some chests in an anvil on it. After replacing it there was a lot of free space in that barrel. Everything else seems to work as expected. There's no obvious reason why that barrel resists. I didn't do anything special with it. The first try to use it after placing it failed.
I was able to reproduce this and (hopefully) solve the issue-- it looks like the trash can wasn't properly cleaning up its tile entity after being broken. A new version should be pushed within a day or so.
Stockpile 0.2.0, Rift 1.0.3-45 (JAR version)
Using the old world with the (un)broken barrel the said issue is not healed. The barrel cannot be broken. In the lastest.log there are less entries complaining about the trash can.
But some are still there:
[11:14:00] [Server thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.ClassCastException: notjoe.stockpile.tile.TileTrashCan cannot be cast to notjoe.stockpile.tile.TileBarrel
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_51]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_51]
at k.a(SourceFile:199) [k.class:?]
at net.minecraft.server.MinecraftServer.w(SourceFile:701) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.v(SourceFile:656) [MinecraftServer.class:?]
at dfx.v(IntegratedServer.java:246) [dfx.class:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:559) [MinecraftServer.class:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
Caused by: java.lang.ClassCastException: notjoe.stockpile.tile.TileTrashCan cannot be cast to notjoe.stockpile.tile.TileBarrel
at notjoe.stockpile.block.BlockBarrel.a(BlockBarrel.kt:68) ~[BlockBarrel.class:?]
at bkt.a(SourceFile:285) ~[bkt.class:?]
at tf.a(SourceFile:146) ~[tf.class:?]
at ub.a(SourceFile:887) ~[ub.class:?]
at na.a(SourceFile:40) ~[na.class:?]
at na.a(SourceFile:10) ~[na.class:?]
at ix.lambda$checkThreadAndEnqueue$0(PacketThreadUtil.java:18) ~[ix.class:?]
at ix$$Lambda$1668/235793410.run(Unknown Source) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_51]
at k.a(SourceFile:198) ~[k.class:?]
... 5 more
^^ sry
It looks like future instances of the issue have been fixed, but not existing ones. Try setting the offending block to air with /setblock
and see if that allows you to place a new one that functions properly. If cheats are off in your world, you can enable them temporarily by opening it to LAN.
/setblock -61 67 -115 minecraft:air replace
"An unexpected error occurred trying to execute that command"
Now /setblock -61 67 -115 minecraft:air destroy
did the job. First the barrel was still there, after moving around and clicking it, it was gone. Yay! Silly me then replaced that empty room with a barrel which suddenly was in the hotbar and the error was there again. Seems I put that old barrel back. After some more trying now there's a barrel in place containing sand. I now seem to have 4 barrels which, when in that place, do not work. Will throw them into lave by time.
Thanks for the hint.
No problem. I'll see if I can add some further verification in the future to prevent residual issues from past versions like this. If that spot continues to make trouble with new barrels, feel free to open another issue if you're up to it-- there might be a different problem at hand.