Advertisement

Looking for help and direction - Robotz

Started by December 17, 2006 11:26 AM
0 comments, last by BlodBath 18 years, 2 months ago
I am trying to develop a freeware 2D board game in C#, using GDI+ for the graphics (since it is a simple board game, I think GDI+ will suffice for now). To get a feel for the game and what I am trying to accomplish, I offer the following links: My post in the "Help Wanted" forum here on gamedevAn attempt to visually depict the game designAn attempt to capture the game design in words How can I get the design to the point where the coding will flow pretty "easily" from that design? So that the programming tasks will be evident and the OOP will sort of fall from the design? I have a pretty decent team assembling, and I feel like they are waiting for some direction. I want to give them that direction, but I'm not sure how to get things moving along. I am wondering if my design were better if that would help. I appreciate any input that can help get things moving along. The concept of the game IS indeed very simple. The game pieces have very simple rules. The game board is a finite 10 x 10 grid. The actual game play will consist of me making my moves and then my opponent making his / her moves. Not very complex, but I feel "stuck" as far as telling who to program what and how to get things going. Thanks!
Generally to start a small project like this I prefer to just start writing base classes and very general functionality. For your project, things like map rendering, interface design, and the base robot type could be good starting points.

Multiplayer games often work best when you create controller classes to manage player actions. This way you can associate everything a player does with an object. A player class is usually a useful construct to manage everything about a player. Gameplay classes might take a 'connection' object to refer to either a local or network connection with a standardized interface for sending/recieving data. Don't try and complicate the design with complex methodologies or you'll more likely than not end up coding twice as much as you need to with no benefit for a small thing like this.

This topic is closed to new replies.

Advertisement