Status: Beta
Beta Date: November 2001
After a year of ups and downs for the intrepid SGP Battlegroup*, we finally offer the long-promised character generation code. Originally done by BEM and Audumla for Granite: NH by Night, this code has been in active use since January there without a hitch. The SGP Battlegroup gathered together to make sure that it worked on all the target platforms(MUX, Penn, TinyMUSH 2.2.x, and RhostMUSH), and we're satisfied that it works well enough for this release.
* The SGP Battlegroup: BEM, Audumla, Jeff, Hilikiradi, Brazil, Talek, Raevnos, Ronan, and Ashen-Shugar, in a reprise of his role as 'The Dark One'. Javelin@M*U*S*H returned for a cameo as 'The Angel of Light and Goodness'.
General Caveats:
-- Like all Beta code, there are anomalies and bugs that will need dealt with. We're not completely sure what they will be, but we're sure they will crop up.
-- You have to read the installer notes and intructions to have a prayer of succeeding.
-- It lacks helpfiles. A web version will be available as we compile the instructions.
-- You still need a competent coder to play.
-- We didn't test this on TM3, and have no plans to.
Q: So what took so long?
A: Testing! Oh, and a lot of RL hassles for the coders involved. We like to release code that actually works and careful debugging paid off. Some people don't live this way, but it sure does reduce the need for antacids....
Of course, as usual, we had to figure out why it didn't work on PennMUSH and port all the changes back to the other servers and make sure the code still worked. It does, we're happy, and we built 2 libraries to celebrate.
Q: Can my game beta test the code?
A: The cocoon is opened. Anyone can use the code. We'll take bug reports like we always do, and hopefully be able to keep up. The main reason that the code is in beta is that the helpfiles are not done to our satisfaction and set up for non-MUX servers.
Q: Oh good! I run this WoD game and I....
A: Bloody Roses provided us with platform and final debugging help for WoD and MUX. However, if you'd like to help build library objects for D&D 3E, Wheel of Time, Star Wars, or another pet game system, we will not turn you away.
Q: I like this stuff, but I wish that the list object/sheets/functions/commands....
A: Two words: Local Hack
This is not to say that we aren't interested in hearing new ideas, but rather that we aren't here to customize the code for every game that installs it. You hire coders to handle things like this, and you should have a competent coder to handle the general maintenance of the master room anyway. Should you come up with a really spiffy hack, we'd like to know, but what determines inclusion in the system will be how it fits with the overall scheme of the project.
Q: We currently use MIAM. Will we be able to convert our game to use this code?
A: Gods, we hope so. We have converted one game and it was the usual tedious business. Expect lots of pitfalls. Regardless, you will need a competent coder for -any- cgen conversion and be prepared for editing code that breaks because of that. We cannot and will not provide you with said coder. You have been warned.
Q: We use TinyMUSH 3.0. Will we be able to use SGP on that platform?
A: Good question. There are shadowy rumors that SGP works on TM3, but we don't test on that platform and generally don't pay attention to whether it does or not. There are no plans to 'port' to TM3, nor do we want anyone to 'port' it for us.
Q: Where are the walk-through statting rooms?
A: There aren't any. Those are not part of the scope of this code system anyway--though you can use this code to generate such features on your game. Walkthroughs are pretty complicated and everybody has their own preferences as to how they want them done, which is why we aren't going there right now. Either way, this -is- why you have that competent coder, right? We may provide a "HOWTO" for setting up such areas, but that isn't part of the scope of this document. If you'd like to help write one, please contact us!
Q: We've been waiting; we want to use this. What will we need to do?
A: Get a competent coder lined up -now-. We aren't kidding. There can be no absolution for neglecting this step of the process.
Second, if you aren't doing one of the game systems with a posted library, start compiling a lot of lists of stats by their type, and be prepared to wait for instructions to be posted.
Third, design an ascii layout of how the sheet should look, should your game be something other than one of the posted libraries. This file might help with that.
When you have completed these steps, you will be a long way toward being ready for actually building the assorted list attributes and internal realtionships that won't be present in the installer itself.
Q: Is there anything else I need?
A: A sense of humor. Building cgen can be a pain in the hiney.