You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the Splitter in #10, this will inspect a payload and then determine where it should go
Maybe this can be made redundant with some clever use of the logic+splitter.
But for performance reasons, this may still be the better option.
To limit the complexity, it can only inspect a single byte, of the player's choosing.
And only up to 6 routing conditions can be added.
Conditions should be order dependent.
Logical operators are provided.
Use cases
-- For funsies, a pseudo ipv4 routing system
-- R is router, S is splitter
-- The could split a single payload across 6 outputs or 6 blocks
R
|-> I -> R
|-> I -> R
|-> I -> R
|-> I -> R
|-> I -> R
|-> I -> R
-- the first splitters would be used to drop the first byte and route the rest
-- the second set of routers would repeat what the initial did, sending to another set of splitters
-- until 4 bytes have been consumed, by then the payloads will arrive at it's destination
The text was updated successfully, but these errors were encountered:
Similar to the Splitter in #10, this will inspect a payload and then determine where it should go
Maybe this can be made redundant with some clever use of the logic+splitter.
But for performance reasons, this may still be the better option.
To limit the complexity, it can only inspect a single byte, of the player's choosing.
And only up to 6 routing conditions can be added.
Conditions should be order dependent.
Logical operators are provided.
Use cases
The text was updated successfully, but these errors were encountered: