Skip to content
This repository has been archived by the owner on Mar 10, 2022. It is now read-only.

CT Network Priorities #42

Open
D1yt opened this issue Dec 17, 2020 · 1 comment
Open

CT Network Priorities #42

D1yt opened this issue Dec 17, 2020 · 1 comment
Labels
Bug Report A bug that needs to be fixed.

Comments

@D1yt
Copy link

D1yt commented Dec 17, 2020

Description (Required)

When setting up a cargo network (CT channel) with whitelists for certain items and wildcard chests (blacklist with no filters) in output cargo nodes, they sometimes prefer a node/inventory for no clear reason (except if you whitelist it to one chest, and blacklist it from ALL other chests). After some detailed testing, the priority it chooses, seems to be decided by the placement in the world.

Steps to reproduce the Issue (Required)

Setup a CT cargo network with 1 CT inport bus and at least 2 output cargo nodes. Put a whitelist with set item into one output node and an empty blacklist into the other. Observe their behavior and switch the set whitelist and emtpy blacklist nodes.

Expected behavior (Required)

Items should look for whitelists before anything else.
Also, maybe priorities should follow something more reasonable and be changable.

Server Log / Error Report

Environment (Required)

image
image
image

  • Minecraft Version: 1.16.4 / Paper
  • CS-CoreLib Version: DEV 92 (e9150d72)
  • Slimefun Version: DEV 766 (5aa5ca1a)
  • ChestTerminal Version: DEV 38 (c024be5)
@D1yt D1yt added the Bug Report A bug that needs to be fixed. label Dec 17, 2020
@TheBusyBiscuit
Copy link
Owner

That's not really a bug, that's just how CT works. There is no "prioritization", it picks the locations arbitrarily.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Report A bug that needs to be fixed.
Projects
None yet
Development

No branches or pull requests

2 participants