Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chest Terminal duplication bug #879

Closed
bverhoeven opened this issue Apr 2, 2019 · 4 comments
Closed

Chest Terminal duplication bug #879

bverhoeven opened this issue Apr 2, 2019 · 4 comments
Labels
🐞 Bug Report A bug that needs to be fixed.

Comments

@bverhoeven
Copy link
Contributor

Description (Required)

The ChestTerminal plugin for Slimefun has an item duplication bug that can be exploited by dragging an item into the cyan/blue bordered item slot and then dragging it out fast enough for it to still be "sucked into" the cargo system but not be removed from the item slot.

The item will then be added to the terminal and attached cargo nodes but will also still be in the player's possession, allowing them to repeat the same procedure over and over.

Reproducing this is easier than it sounds, as can be seen in the video below.

This issue looks very similiar to the one reported in ChestTerminal itself- TheBusyBiscuit/ChestTerminal#4.

It seems that the issue is not in ChestTerminal (that plugin actually does very little with the actual terminal management and item transport), but it seems to be related to the way the "Cargo Network" within Slimefun handles terminals.

Server Log

n/a

Evidence / Proof (Required)

Here's a small video (click to open) that shows me obtaining 64 diamond blocks and then exploiting the duplication bug to gain more and more:

Watch the video

Environment (Required)

Paper v1_13_R2
CS-CoreLib vDEV - 36
Slimefun vDEV - 87
ChestTerminal (master)

bverhoeven added a commit to bverhoeven/Slimefun4 that referenced this issue Apr 2, 2019
This is an attempt to fix the chest terminal duplication issue that seems to
mainly be caused by the fact that the cargo network sees the item in the
"out slot", registers it but doesn't move it to the network yet until the next
call to the scheduled task. This allows the player to take the item before the
task is executed, but will still execute the task and thus insert the item if
there is enough space.

Now, before we attempt any storage operations we first check if there's an item
in the "outgoing slot", if there is, we'll try to send it instead of waiting
for the next call to Cargo Network's scheduled task.

This doesn't seem to impact the system in a negative way and seems to be an
appropriate fix for the issue reported here:

Slimefun#879
@EnderSlime123
Copy link

Are you using the latest ChestTerminal build, cause the one I used has a lot of non-colored names on its items, and the Wireless terminal items don't work.

@mrcoffee1026
Copy link
Contributor

The later build fixes the icons but a couple of the slots in the "inventory" of the CT Access terminal... if you put the item in that slot (or even a stack of that item)... and then remove it... it is replenished each time you remove it, regardless of how many items are actually in the network... creating an infinite supply of that item. I tried the latest builds:

CS-CoreLib vDEV - 36 (git 2e140f82)
Slimefun vDEV - 92 (git 4f05f80)
ChestTerminal v1.0 (this one: #4 - 15 Apr 2019 (14:50:25))

@EnderSlime123
Copy link

The later build fixes the icons but a couple of the slots in the "inventory" of the CT Access terminal... if you put the item in that slot (or even a stack of that item)... and then remove it... it is replenished each time you remove it, regardless of how many items are actually in the network... creating an infinite supply of that item. I tried the latest builds:

CS-CoreLib vDEV - 36 (git 2e140f82)

Slimefun vDEV - 92 (git 4f05f80)
ChestTerminal v1.0 (this one: #4 - 15 Apr 2019 (14:50:25))

So ChestTerminal is unuseable basically?

@mrcoffee1026
Copy link
Contributor

mrcoffee1026 commented Apr 19, 2019

At least until that glaring duplication glitch is removed? Well I won't be running it. But give them time it's only just been brought to their attention and the addon has only been viable for a little while now since they started working on it again. Not certain but it seemed to me that most of the addons had been relatively untouched since MC 1.8 or so, this is the most action I've seen on them since finding Slimefun in the first place so just keep an eye on the repo server for new developments.

@TheBusyBiscuit TheBusyBiscuit added the 🐞 Bug Report A bug that needs to be fixed. label May 11, 2019
TheBusyBiscuit added a commit that referenced this issue Jun 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Bug Report A bug that needs to be fixed.
Projects
None yet
Development

No branches or pull requests

4 participants