Best way to handle player data? (541812)

Hey guys!

Currently i’m making a game that needs to load alot of player data upon game load everytime the game starts.

Data examples would be items, characters, stats, etc.

Currently I’m storing everything in a MSSQL Database and then posting/retrieving data via. the WWW Requests in Unity. However, I’m not sure about that this is the most efficient and fastest way to do it.

Since this is a Webplayer game, I cannot use files to store the data, since that’s not possible to create from Unity on a webserver.

I am using PlayerPrefs, but since that can only store tiny amounts of data, that’s just storing the Player’s Account ID for caching login.

Is there any other way you would go about data structure? My only requirements is that it can all work on a Webplayer.

Thanks everyone!
/ Kevin

I think that’s a reasonable approach if you’re familiar with SQL. You can have the schema mirror the data structure, which would let you query the data more easily (e.g., a web app that tells you who has what items), or store all the data in a blob as json/bson. The latter would be easier to develop since you don’t have to change the schema with every change to PlayerData.

A third option would be to use a no sql document store like Mongo that lets you do both, but if you’re familiar with MSSQL I’d stick with that.

In any case make sure you understand the authentication issues-- make sure every request is authenticated by a token so people can’t read or write to other people’s player data.