quote:Original post by C-Junkie
I have not tried actually coding this. (hypocrite?) I''m not sure exactly how to do it. My first idea would have been a class for each skill...but you''ll easily end up with 100+ classes. If anyone has actually used this system, would you mind sharing how you implemented it?
Okay, just for the record...I haven''t coded it yet, nor has the programmer on my team. (Well, technically, it''s not
my team, but that''s beside the point...
) But anyway, here goes:
Using a class for each possible skill (if I understand you right) is beyond overkill. I''m guessing you mean a character class for each skill, like fighter, wizard, and all those other generic character classes. (If I''m wrong, you can ignore the rest of this.) First, I classified my skills as Primary, Minor, and Secondary skills. The player is free to choose from any primary skills, up to a certain level. Once that level is reached, the class is determined based on the two highest primary skills, and then they are given access to skills in their class tree at x skill points, and outside their class at y skill points. That still gave something like 45 classes, which is IMO too many for streamlining the effect--you don''t want your player to get bogged down in classes to keep them from the story. So what I did was make a chart of all the possible 2-primary-skill combinations possible, and defined classes from those, allowing them to overlap. This got my class list down to around 10. Of course, you may have more, if you were going to have 100+ classes rather than my 45, but maybe that will help you (or any other designers working on a system like that).
Gee, I never realized I could be that long-winded....
--
WNDCLASSEX Reality;
...
...
Reality.lpfnWndProc=ComputerGames;
...
...
RegisterClassEx(&Reality);
Unable to register Reality...what''s wrong?
---------
Dan Upton
Lead Designer
WolfHeart Software
) but how exactly do you wish to get a secure AI thing happening on remote machines? That is a fair bit to ask from a client 
