Design
DB Sync
DB Sync
Goal
- Multi-Framework compatibility - "Abstracting" the framework's tables away via a separate sync process with handles/merges the data as needed into FiveNet compatible table structure.
Idea
- Sync process that takes care of reading and transforming the data.
- Cleanup of deleted, e.g., users, vehicles, etc., should be handled as well.
- Config presets for common frameworks (e.g., ESX, QB)
- For communicating changes from FiveNet to the gameserver, the NATS websocket system or a custom websocket system could be used (messages would be encoded via Protobuf JSON).
- A "state" file (like log collectors use to store the "last line") to store the last "ID" (in case of tables without an ID field, it would use, e.g., the
owner
field).- In case of multiple queries, the state is stored per query index number in the config file.
Limitations
- Only one (main) phone number per char/user.