Modulizing "Added Spells, Skills, Commands, etc"

From: Treker (
Date: 08/18/00

Perhaps in future releases of CircleMUD, it'd be a good idea to make a
header/source file pair called userdefined, which would contain all of the
"added" spells and skills, thus centralizing any of the seek-and-replace
work to one (or two) files, making it many times easier to add new spells,
skills, commands, and probably reducing the code size (after adding the
spells) as compared to the current method which forces the coder to run
through more code than is required normally.  Of course, this is just a
suggestion, and would probably require revamping a good lot of the MUDs
spell interpretation functions/methods, as well as object-orienting a lot
more than is currently.

I understand that Circle works fine without classes, but I can see many
places where classes would reduce the code size and complexity.  I guess I'm
babbling, so I'll stop.


> -----Original Message-----
> From: Circle Discussion List []On Behalf Of
> Alex
> Sent: Friday, August 18, 2000 5:52 PM
> To:
> Subject: Re: [CIRCLE] Welcome and Coding
> > Yes, I understand, but that's no excuse for someone not to take
> charge (ie:
> > the original coder(s)) and to organize some of the obvious things.
> A quick history lesson:
>   CircleMUD is based on DikuMud, a product of the early 90s and a team of
>   5 coders.  Jeremy Elson created CircleMUD and since he began 4-5 other
>   coders have put work into it.  The official base code release is
>   reasonably well organized, not all of the addons or snippets are.  This
>   is generally the case with unofficial addons.
> > Such as the current bpl16oasis+dg greera distribution which has a new
> > line in constant error in act.wizard.c
> Two things here:
>  a) 'greerga' not 'greera'.  His name is George Greer.  He prefers to
>     go by that, just as I prefer 'Alex' rather than 'fletchra'.
>  b) That's not an official release by George, Jeremy, dak, or myself.
>     The person who put it together may have made a mistake.  Check over
>     the README file, drop a line to the person who is credited for the
>     collection of the work, and point out the error and a fix.
> The only code that we (being the CircleMUD team) have any direct control
> over is the offical patch levels that we release.  Anything else is
> outside of our control.
> > Sorry, as I said, I'm new to the list and the Circle
> Documentation world.
> >      | Ensure that you have read the CircleMUD Mailing List FAQ:  |
> >      |  |
> Read this then.  And you'll note that it suggests reading the CircleMUD
> FAQ also.
> Ae.
>      +------------------------------------------------------------+
>      | Ensure that you have read the CircleMUD Mailing List FAQ:  |
>      |  |
>      +------------------------------------------------------------+

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  |

This archive was generated by hypermail 2b30 : 04/11/01 PDT