Slimefun

Slimefun

3M Downloads

Miner Androids cause block errors while mining

NCBPFluffyBear opened this issue ยท 4 comments

commented

๐Ÿ“ Description (REQUIRED)

When using Dig and Move Forward, androids sometimes create a block type disagreement. Here's an error:
https://pastebin.com/iNgjXg58
Once this block is corrupt, any kind of interaction produces console errors, including right clicking, left click, and breaking the block with an android. It does not behave like a ghost block, and players can place blocks inside it perfectly fine. It does not have any BlockStorage either.

In addition, I noticed that when a block is placed in a spot right after the android moves away from it, that block is broken and a Cs CoreLib head (android) appears in the android's inventory.

In addition to that addition, this also appeared and may help diagnose the problem: https://pastebin.com/fAcF5rCz

I have grouped all these issues together because they may be caused by the same source.

This issue may be related to #2408 and #2111 .

๐Ÿ“‘ Steps to reproduce the Issue (REQUIRED)

  1. Place an android
  2. Create a script that uses a combination of Move and Dig Forwards and Turn Right to create a loop that moves back and forth
  3. After some time, errors may start to appear in console
  4. Attempting to quickly place a block where the android used to be right after it moves will cause that block to be broken.

๐Ÿ’ก Expected behavior (REQUIRED)

Androids should not bug out, and the tasks it performs should be executed in order.

๐Ÿ“œ Server Log

https://pastebin.com/iNgjXg58

๐Ÿ“‚ /error-reports/ Folder

https://pastebin.com/fAcF5rCz

๐Ÿงญ Environment (REQUIRED)

  • Server Software (Spigot/Paper): Paper
  • Minecraft Version: 1.16.3
  • Slimefun Version: DEV 709 (git 4c47a)
  • CS-CoreLib Version: DEV 91 (git e42a0)
commented

@NCBPFluffyBear when exactly does this occur?

commented

The two issues you referenced are completely different.

commented

@NCBPFluffyBear when exactly does this occur?

Randomly, hard to get a video of it. Only the breaking behind bug is really testable

commented

The two issues you referenced are completely different.

Sorry, I just included both to be on the safe side