Storage Blocks are no longer capable of being linked to Logic blocks. Already existing links also cannot be removed.
Description
Description
Details
Details
- Task Type
- Bug
Testing Results
- Affected Gamemode(s)
- Single and Multi
- Reproducible
- Yes
- Last tested (version)
- 0.198.131
- Category
- Logic Gates
- First occurrence (version)
- 0.197.51#20160424_191721
Hardware/Software/System
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Steps to reproduce
1.Place a storage block as well as an Activator or an OR block.
2.Select Storage block with C and attempt to connect it to the logic with V, no connection is made.
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>
| Status | Assigned | Task | ||
|---|---|---|---|---|
| In Queue | AndyP | T84 Logic blocks next to storages and shipyard computer do not get triggered | ||
| Closed | AndyP | T1382 Storage Blocks Cannot Be Linked To Logic |
Event Timeline
Comment Actions
Linking Storage Computers (Chests) to logic gets output based on if a chest is full or not. When linking to an OR you get a signal when there is anything in the chest and an ACTIVATOR will trigger when the storage is full. These connections can no longer be made.
Comment Actions
That was through linking ?
not only placing it alongside a block?
(like the trigger-activator thing)
Ok ... its a verylong time ago that i did play around with that stuff
Comment Actions
-Validated-
-Confirmed-
Indeed not possible as per authors description
sorry that i couldnt remember how that originaly worked
Comment Actions
Nope.
the system has changed.
It pushes the information on pull cycles to adjacent logic modules.
OR should trigger an "empty" cycle
Activators should turn to false if the cycle was successful.
Going to retest the behaviour ingame first.
I am also sure we have a task about it already, the manual put in does not trigger the "empty state" to be cleared on next cycle.
Comment Actions
-Rejected-
Intended behaviour.
Links to adjacent modules are even shown now.
No way or need to manually link them, they work on adjacent storage chests.
An activator beside the chest will be "set to true" every pull turn that was NOT limited by the capacity. (So nothing to pull, and successful pull = set true), an OR-SIGNAL beside the chest will be set to true, if the storage cycle made the chest become "non-empty", and it will be set to false if another chest pulls out the last item out of it and thus makes it empty.
Same behaviour is intended for the shipyards.
(see T84: Logic blocks next to storages and shipyard computer do not get triggered for reference)
Comment Actions
This feature originally used adjacency to work but then went to linking so Schema decided to go back to adjacency?
Just tested it, adjacent logic blocks do not trigger in any circumstance while logic blocks that were previously linked to the storage computer continue to function and work as expected. I do not believe that the system is intended to work with adjacency.
Comment Actions
It is intended to work that way.
Please read this comment for details on what works and what does not work: T84#34805
Possible link based connections are for now kept for legacy reasons, but cause performance issues with cargo, and can also lead to problems with updating cargo blocks.
Comment Actions
-Reopened-
New behaviour:
No links are made at all.
The storage chest does not get linked to an activator.
Comment Actions
-QA Testing-
Fix confirmed.
Outgoing link by C-V now works again.
No more needing for adjacent activators.