|
@FrameProblem... There are two database systems. One is local to the machine, and supports off-line work against the Realm. This is the one that is directly used by the program while working on it. The second is a cloud database used for distribution of changes to "subscribed" machines (a GM's second machine, a player's copy of the software, the future web-based player access, etc.).
As such, there are no "concurrent" updates. A GM can accumulate changes on the local copies for weeks, even years, without syncing them to the cloud (and thus, if using two machines, to each other). Doing this while working on two machines pretty much guarantees that eventually, one set of changes will over-write the other when both are sync'd to the cloud server.. last one there wins.
There was brief talk some time ago about some merging tools to allow GMs to see and select which conflicting updates would be accepted and which rejected. There has not been anything said about that in some time, though, and for now there is no such capability.
So, multiple GMs dramatically increases the possibilities of conflicting updates, and would require that such merging tools be created as part of the necessary support.
(Note; A GM can use two machines safely without the cloud syncing by backing up the Realms db on one and restoring on the other. This restore over-writes all realms, though, not just one.)
|