Hi!

So, we're working on a really cool project. Our project aims to help multiplayer game developers in their journey of developing a multiplayer game. Basically, it's a multiplayer engine that should simplify the process of creating a server for a multiplayer game.

In the engine's development process, we encountered some questions. Several of them we answered ourselves easily, but we are in some need of advice with several other questions.
We've created a survey to help focus our question and learn if other game developers encountered the same issues as we did and if our solution to them is viable.

We would really appreciate your response.

Survey

Thank you for your time!

On 8/3/2019 at 2:01 AM, hplus0603 said:

If your multiplayer server is for "asynchronous, turn-based" games like Candy Crush Saga or Backyard Monsters or Farmville, it's possible that a generic multiplayer back-end could make sense.

However, for any game with real-time requirements (action games,) the multiplayer game server needs to have very tight integration with the game logic of the game client, and generally the server and client will share that game logic code.

What kinds of games are you targeting with your "generic" engine, and how do you intend to solve the game-specific functionality challenges?

We currently have a working solution for an FPS backend, a shared RPG(Diablo style) backend, and working on a MOBA solution.

We are aware of the required integration between server&client, and we're working on an SDK that will allow developers to integrate it easily.