The Chosen

I’ve had a lot going on lately and haven’t had much time to sit down and document my adventures, let alone sit down and actually write code for the RTS. Hopefully this will catch you up on what I have been working on for the past 2+ months. Progress on the RTS had slowed down mainly because I still had some legitimate doubts about the server-side code I was going to have to write to handle the enormous amount of data. I was sure that I could get something working, but instead of storing data in cryptic text files like I have done before, I wanted to try something entirely new. I had been looking into Java database clients (JDBCs) for a while but never had the real need to get one working, so this seemed like the perfect time to push my limits once again. In addition, the actual performance of my previous servers was severely limited because of the code structure I used, and it needs to be drastically re-designed.

Knowing that a major overhaul was gonna be necessary on my server’s design, I figured that now would be as good a time as any to design a new server structure that incorporated a complete database back end, as well as data protection and more sophisticated client management interface. Not entirely sure what would be necessary in the RTS database, I made the tough decision to put the RTS engine on hold while I dedicated my designing, coding and testing a completely new sever structure.

I started by once again trying to get a JDBC client to run, this time with the HSQLDB package. My past attempts at getting the JDBC working all failed miserably so this time I was absolutely determined to get it working. I sat down expecting a big fight to get it up and running and much to my surprise, this time it just worked. With very little fight at all I got a small test app setup and running just like I would like. After a very brief celebration, I began writing a new server.

While it would be nice to just be happy about the new server and start implementing it into the RTS, I would rather see the design tested in some working environment to ensure that this structure will, in fact, do what I need it to do. I eventually decided that I would use pieces of my old chess program to create a new stratego program to use the new server. The concept is an entire tabbed interface where users login, chat in the lobby, join as many games as they want, and play stratego with other players over the internet, with all the traffic running through my server of course. Most of the networking and database code is complete and working but there is still a lot that need to be fixed and/or improved in the client side code. As of right now, it is entirely playable but still has a few code bugs that need to get worked out, and some design issues that need to get fully implemented before I release it beta group. More news will be posted on FreshProgramming.com.

Despite numerous distractions, I final got my my Chat server up and running. Spending all that time one networking side of the code has really improved my confidence in the multilayer side of this project. As part of the process of getting my first server up, I also have all configuration done on my home network, meaning that the next server application I write will be a much simpler process. Also, because I picked a program that I use on a regular basis, I am able to work out all of the design problems in a less stressful environment, and will have an excellent template to build from when I start on my RTS server. In addition to my progress on the server development, I have also made some decent progress on the GUI. I believe I have the entire layout handler complete and have a complete default GUI setup, functional, and ready to go.

Whenever I start a project like this, I also try and identify all of the possible problems, and troublesome issues first. Long before I start writing any code that will end up in the final game, during the first design meetings, I isolate each issue, either mentally or in actual test code environments, and make sure that the design concept is possible, and within grasp. This project was no exception, and I wanted to make sure I knew what I was doing.

(more…)