Any project needs a roadmap. For my SignalR MUD I’m going to try and embrace the concept of incremental and frequent releases once I get to writing code. Each step should yield a functional end result that adds functionality and moves the project forward.
There will be a couple of phases.
- Creation of the basic framework
- Making the UI for players not suck
- Creating a design interface to allow non-programmatic extension of the game by creating areas, creatures, items, etc.
- Creating an admin interface to allow modification of accounts/existing users etc.
A rough outline of the steps involved in phase 1:
- A simple SignalR chat application – user goes to the site, is asked for a name, and can begin chatting. Really bare bones
- Login/Account creation – using some kind of single/social sign-on and persist accounts. Will need some kind of validation to ensure uniqueness, etc. There will be roles as well – general user vs. admin, etc.
- Add rooms – people will only see messages from other users in the same room and will be able to move from room to room
- Add “characters” – add functionality so that users can create a character based on common role playing game concepts – gender, race (human, elf, klingon, whatever), class (warrior, mage, whatever)
- Extend “characters” by adding NPCs (non-player characters) They will functionally be the same as a character, except they will be controlled by the system.
- Add commands – When users are logged in and in the game as their character, we need a system that allows them to do things other than talk. User inputs will now be parsed and we will route their command through some kind of handler if it matches the desired pattern
- Add the physical universe
- Character bodies and body parts
- Items (things you can wear and use or do stuff with)
- Inventory management
- Add AI to the NPCs from step 5
Phases 2+ will be in other posts.