Sites

Menu

Tutorials and guides

[Experimental] Database sync worker

The Database Sync Worker Example is experimental, as is this tutorial. We have made the tutorial and feature available to gather feedback to help us shape this functionality.

Do not use the feature for production game development: we do not support it or its tutorial and are not committed to further developing this functionality. See the GDK’s roadmap on GitHub for information on features in development.

This tutorial takes you through how to integrate the Database Sync Worker Example in a GDK project and use it to store persistent data outside of a SpatialOS deployment.

The Database Sync Worker is a SpatialOS server-worker designed to easily synchronize and persist cross-session game data (such as player inventories) between SpatialOS and an external database.

This tutorial uses the GDK’s Example Project, where the Database Sync Worker will synchronise players’ “All Time Kills” and “All Time Deaths” counts in a local Postgres database.

Prerequisites

Before starting this tutorial you must follow:

This tutorial assumes that you are familiar with the basic development workflows of the GDK from the “Set up a project” guides: Example Project, Starter Template.

Additionally, to communicate with the Database Sync Worker, you will be sending SpatialOS commands and listening to events, so a basic understanding of SpatialOS messaging is required. (This is something the GDK typically abstracts from you when you build Unreal workers - in this case we will be integrating a C# worker using the SpatialOS Worker SDK directly so these concepts are important to understand.)


> Next: 1: Set up



——
2019-11-25 Page updated without editorial review: experimental wording
2019-07-31 Page added without editorial review

Search results

Was this page helpful?

Thanks for letting us know!

Thanks for your feedback

Need more help? Ask on the forums