Well, I’m sorry to say that the current version of Crystal Lotus (for Windows Forms) is going away. I will spend a blog article or two discussing the code, but essentially the main progress I made was with the deck editor and core card functionality. The majority of my time was spent being frustrated with NeoForce Controls, XNA 3.1, and .NET 3.5 before I finally switched to Windows Forms. The code was all ported successfully, but the project stalled not long after due to school-related workloads.
Thankfully, I’m switching to EnigmaEngine, XNA 4.0 and .NET 4.0 for a fresh start. I’ve also talked and read more about designing and writing a rules-enforcing application, so I feel better prepared. I will do an entre-mortem of Crystal Lotus 0 (I’m a programmer… I count starting from 0). Then, after my tests in May, I’ll jump start Crystal Lotus.
Before I begin my entre-mortem, I would like to mention that I’m a high school student. As a result, I haven’t taken an actual CS course at a college or university, but I have been programming C# for well over 2 years. Therefore, kindly judge by quality of code or end product rather than age or the fact that my life is hectic with AP and IB tests and classes.
Generally, in the games industry, a development team will conduct and publish a post-mortem of their game several months after the first or second patch of their game. However, since Crystal Lotus is nowhere near finished and is instead adopting a ‘one step sideways’ plan of action, an entre-mortem seems more appropriate. An entre-mortem is simply a reflection on the design and development of the application. For Crystal Lotus, the entre-mortem will focus on the code and code design but will stray into art and UI occasionally. Additionally, the optimistic scope of the project will be discussed, with the intent about reaching a reasonable conclusion about the development timeline for such audacious projects. (more…)