It has been a long time since my last post. Life stuff beckoned and demanded my attention. Finally, I have delivered something beyond excuses. It’s not much – a simple WebSocket server that responds to requests to fetch dungeon data – but I am pleased. Dungeon data are stored on files on the server. So it’s really a small, slightly crappy excuse for a web server. The Game Server. So I am now the proud own of a small, homemade “sort-of-web-server” with a key difference – fast stateful connections. So it’s more like the beautiful supermodel offspring of a web server and plain ol’ TCP sockets, and less like Frankenstein. It was easy to build and the only reason it took so long was the aforementioned wetware commitments and a new job. The World Cup has not helped either.
Press this button and the dungeon data will be returned. Everything is awesome.
OK , so now I know how the Game Server will work. Not sure what to do next. I have several building blocks done, but nothing assembled together. So I now have:
- A game server concept suitable for multiplayer play
- A basic sprite animation approach
- A combat engine concept
So the options are, in descending order of fun:
- Creating autonomous agents to control behaviour of monsters and NPC’s
- Finish a first cut of the game engine
- Finishing the game server
- Create some better graphics/images etc
- More Stuff
I think option 2 is the best way to start, with monster behaviour a separate component. I could even create a text based game, command line version of the engine to test the concept…..Hmmm. That sounds good. A solid engine which I can then tart up with pretty eye candy. Considering my current level of graphic design skills, this sounds like a good bet. I always bet on “ugly but smart”.
So much new stuff. So many ways to get it wrong. Serious fun.