- Game Engine
Game engine as a Service - powered by RestHub.js
If you’ve never heard about Mythic-Forge, have a look at the first version.
After a first implentation with a Java-based server and two Flex web applications, it was obvious that Flex was not the right solution.
At work, we were using the RestHub framwork since several months, from which I was an active contributor.
No more Flex Web applications means a new communication channel between UIs and server. As the game is multiplayer and online, this channel has to be always wired: web sockets seems a good candidate (early 2011: not widely supported). But web sockets are just… sockets. I made a quick implementation of the STOMP protocol in Java for my server (none available at this time).
It allows to share state between players and server, but also between game developers.
The UI was far more easy and beautiful, with notable additions (shortcuts, syntax highlighting, code validations, icons). And automatically testable with Selenium
Push to deploy your game
Every file save was linked to a commit in a git repository on server side. Finally, a deploy button make a git tag, concat and optimze all JS and CSS files (thanks to Require’s optimizer), and copy it to a public folder accessible to players.
It allows game designer to develop within a staging area (using the real game objects and maps), and roll out they work when ready, without game outage !
Tales of Eethia 2
But I didn’t put efforts on communication, and very few people had played. Discouraged, I gave up.