[Tinymux] The Plan for TinyMUX 2.4, 2.5, and 2.6

[Roy Anger]

On Wed, 2005-06-29 at 17:05 -0700, A Character wrote:
> >So that the years and version match again, there will not be a TinyMUX
> >2.5. I'll start the TinyMUX 2.6 tree in mid-December. The SQL
> >connector should be finished, but if it isn't, it will move to 2.6,
> >and I'll remove the unfinished parts of it from TinyMUX 2.4.
> 
> I have heard, perhaps, a billion things about SQL and MU*es working 
> together.  But what I haven't seen (though, admittedly, little searching) 
> was tutorials about how to get that working or more specificly what the heck 
> SQL is and why I would want something like that for my MU*.  Anyone wanna 
> enlighten me?
> 

To give actual examples, this could allow your game to interface and
share the data with other technologies. For example someone could be
running the web discussion board software phpbb2, which can use a MySQL
database to store information. Were TinyMUX able to, through softcode,
connect to a SQL database you could write softcode commands so that the
game and the game's website would use the same data for in game bulletin
boards and website discussion boards. In fact this has been done for
PennMUSH which support SQL. See
http://sourceforge.net/projects/mushphpbb


Another idea could include a web based chargen where the potential stats
and rules are stored in the SQL database and a webpage frontend using
something like php will use that information to dynamically create the
webpage for chargen based on user selections (IE, different skills if
someone chooses the Race Human vs Vulcan). Once the person is done their
characters stats are either stored in the database and retrieved in game
via softcode or could be loaded from the SQL database to a traditional
character object in game. I actually have something like this half done, 
though I was tinkering with it and never completed it. I was using a 
phpbot to make the connection between the website/db and game.

So there are a couple of actual examples of possible SQL uses.

R