A lore-friendly way to share database contents globally (ie between constructs), allowing users to implement things like star maps or crafting calculators in-game.
One way to do this would be to add some API to the normal databank elements:
publishAs(globalID, mode) -- make the contents available as read-only, or read-write, using a unique id
subscribeTo(globalID) -- replace the local contents with those from a published databank
Alternatively, this functionality could be moved into one or more separate elements, which could cost more or have other requirements.
We could have standalone "Databank Server" and "Databank Client" elements which behave like Databanks, or which have to be linked to real databanks.
These could be protected to be read-only or read-write, based on the existing permissions systems. Lore could explain how the contents are shared, and there could be time delays built in (for example, due to the time taken to send the data between star systems).
samdeane
commented
3 years ago
A lore-friendly way to share database contents globally (ie between constructs), allowing users to implement things like star maps or crafting calculators in-game.
One way to do this would be to add some API to the normal databank elements:
Alternatively, this functionality could be moved into one or more separate elements, which could cost more or have other requirements.
We could have standalone "Databank Server" and "Databank Client" elements which behave like Databanks, or which have to be linked to real databanks.
These could be protected to be read-only or read-write, based on the existing permissions systems. Lore could explain how the contents are shared, and there could be time delays built in (for example, due to the time taken to send the data between star systems).