Skip to main content
HyperX separates data by owner and operational workflow. Decide what the data belongs to, create the required Console table if needed, then read or save it from the SDK.

Which Feature Should I Use?

Store account-wide settings and save data as user data. If you need a flexible JSON bundle, define an object field in a user data table and store the payload there.

Read Shared Data

Shared data is created and published from Console. Clients read it. When no record ID is specified, HyperX reads the first record in the table.

Save User Data

PutUserData accepts POCOs, anonymous objects, and dictionaries, then serializes them with JsonMapper. Use PutUserDataJson or the JsonData overload when you need exact JSON text or tighter Unity AOT control.
When no record ID is specified, HyperX reads or saves the first record in the user data table.

Save Multiple Records

For tables that need multiple records, HyperX generates the record ID. Store the returned RecordId to read that record later, or list the current user’s record IDs in the table.