Those 2 sites: www.kyndig.com and www.mageslair.net
I personally like hardcoding values that affect balance. Once you achieve balance, you dont mess it up as easy. :) Chris Litchfield -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jamie Harrell Sent: Wednesday, March 13, 2002 12:13 PM To: [email protected] Subject: Re: Updated code base? > Also, I notice things like races and classes where still hardcoded >into the code, any thoughts on makeing these elements datafiles instead >so that classes and races can be added at will perhaps even at run time. > I wasn't sure on spells as well but I take it those where hard coded as >well. Sure, you could use OLC 2.01, but if your a die-hard 1.81 fan, there are even snippets out there on sites like Kyndig.com and The Mages Lair (I think..) that allow you to "un-hardcode" these right out of the codebase... I've even used them as some base-work for my own projects into this, good stuff I tell you :) > The number one idea is, flexability of the gameing system. Isn't that the goal of every good programmer? ;) >A system where races, classes, spells, and perhaps even some skills are not hard >coded elements but softcoded scripts or datafiles that can be read >updated at real time or at boot time, and trying to avoid haveing to >recompile the system for these (although quite major) changes. This >could be viewed as a major overhall of the system but I think it can add >quite a bit. Sounds like you've got some very definitive ideas, this is VERY healthy for a new-coder in the ROM community, atleast it'll keep you focused on what you want... In that case also, I might steer clear of OLC 2.01 again, and go with 1.81, some security patches, and some more unique code of your own which would do things as your invisioning. There's nothing more frustrating than starting with someone elses code on something, and then realizing that this system does it in such a way that it's even MORE work to get things done the way you want. > Now if there's already a project that uses Rom in this avenue, then >perhaps my attention is best focused there. And I know I"m not the >first to offer these ideas to say the least, But I'm curious what >perhaps the general thought of them are. Bad most likely but I'm >curious never the less. ROM is what you make of it, it's a good starting point for a lot of code, but like I said before, using someone elses code can either be a god-send from time to time, or a nightmare the rest... I suggest you start with something basic, and keep your eventual goal in mind, it'll help you in the long run, and keep your MUD focused towards a singular series of goals.... If you can manage to do this, your already a step ahead of the game. Best of luck in your coding efforts, -- Jamie Harrell | [EMAIL PROTECTED] | URL: http://icechild.dhs.org ICQ: 2985611 | AIM: Liquidicie -- "A computer scientist is someone who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful." -- -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
