There needs to be some kind of in-game communication possible within Telem for coordinating systems across dimensions. Each computer attached to a peripheral can directly output its metrics to whatever local display it wants to, but having a home base that collects everything in one place is going to be important.
The input adapter would be a very specialized design as it needs to listen to events in order to collect them. The output would work like a normal output adapter, just screaming metrics into the void.
The input adapter sends requests to output adapters. The output adapters listen for requests.
Design notes:
Should modem inputs overwrite adapter? Strictly speaking it should, but I think it makes more sense if it preserves the remote adapter and source names. Maybe prefix adapter? If remote input adapter is chest_1 and modem input adapter is storage_terminal, the final adapter is storage_terminal:chest_1This has been implemented at the Backplane layer. For every input adapter that passes through cycle(), every metric will have <adapter>: prefixed to its adapter property.
Secure Modem has been implemented with ECNet 1.x for the time being. I am planning on releasing a beta version of this adapter while I work up updating to ECNet 2.
There needs to be some kind of in-game communication possible within Telem for coordinating systems across dimensions. Each computer attached to a peripheral can directly output its metrics to whatever local display it wants to, but having a home base that collects everything in one place is going to be important.
The input adapter would be a very specialized design as it needs to listen to events in order to collect them. The output would work like a normal output adapter, just screaming metrics into the void.The input adapter sends requests to output adapters. The output adapters listen for requests.
Design notes:
adapter
?Strictly speaking it should, but I think it makes more sense if it preserves the remote adapter and source names. Maybe prefix adapter? If remote input adapter isThis has been implemented at the Backplane layer. For every input adapter that passes throughchest_1
and modem input adapter isstorage_terminal
, the final adapter isstorage_terminal:chest_1
cycle()
, every metric will have<adapter>:
prefixed to itsadapter
property.