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
In order to build UIs that allow players to cooperate or exchange information, we need a way to share data.
One way to do this would be to add some API to the normal databank elements, which allowed their contents to be published to a fictional in-game "cloud":
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
This could have some cost associated with it, to avoid excessive real-world storage requirements.
Alternatively, we could have some new "Databank Server" and "Databank Client" elements which behave like Databanks, or which have to be linked to real databanks, and provide shared access to them.
Again these could be very expensive to make/buy, and/or could have usage costs.
However the databanks are shared, they could be protected to be read-only or read-write, based on the existing permissions systems.
For the sake of realism, lore could explain how the contents are shared, and there could be time delays built in to simulate the time taken to send the data between planets / systems.
The text was updated successfully, but these errors were encountered:
We would like to change the databank system. There are a lot of problems with the way it is done, the most visible for you is the performance, and for us the server bandwidth load.
In this aspect, yes we're already considering to have a part of local storage / synchronized storage and fast update storage. With data size limit per type obviously. And smaller for faster update.
Obviously it's still in consideration, no promise :)
(originally posted here)
In order to build UIs that allow players to cooperate or exchange information, we need a way to share data.
One way to do this would be to add some API to the normal databank elements, which allowed their contents to be published to a fictional in-game "cloud":
publishAs(globalID, mode)
-- make the contents available as read-only, or read-write, using a unique idsubscribeTo(globalID)
-- replace the local contents with those from a published databankThis could have some cost associated with it, to avoid excessive real-world storage requirements.
Alternatively, we could have some new "Databank Server" and "Databank Client" elements which behave like Databanks, or which have to be linked to real databanks, and provide shared access to them.
Again these could be very expensive to make/buy, and/or could have usage costs.
However the databanks are shared, they could be protected to be read-only or read-write, based on the existing permissions systems.
For the sake of realism, lore could explain how the contents are shared, and there could be time delays built in to simulate the time taken to send the data between planets / systems.
The text was updated successfully, but these errors were encountered: