P0-P-172: Part 90: Server Architecture, Data Paging

I have finally managed to get mysql support into the Unity engine.

I am concentrating on making a single player game for now, just to get the database interaction working, but I do have basic multiplayer support included, it just hasn’t been tested or updated to accommodate my recent code additions. It should, however, be fairly easy to add multiple clients to the unity game server, as long as I am careful about how I write the database interaction code.

I have spent a lot of time reworking my existing client/server/database code, and I have more or less succeeded in getting basic functionality working. I am now at the same point I was before I changed the systems architecture, but without the c# gameserver.

There are still some performance issues with connecting to the database, but I am hoping that I can fix them with either coroutines or threads.

The next goals, once I have the database properly working, is to stress test the system. It should be able to handle loading and unloading large numbers of objects as the user moves through the world. The user should also be able to create custom objects, and move other objects, and have all of the object data stored in the database.

I then want to begin work on procedurally creating objects at random when a user explores an area for the first time. After the area has been explored, those objects will be paged from the database, so the gameworld will grow as players explore.