|
While I'm not familliar with Melville, nor even DGD-specifics, two things:
- C / C++ combat systems ought to have an example value in the more distant sense only for what you need. Especially things like the temporal flow of combat is highly dependent on how your codebase is being built, and LPC, being interpreted, tends to implement things a bit differently than a compiled MUD.
- You'll probably want to have a look at the combat modules from other mudlibs instead as they ought to be closer to what you need.
In practice, combat flow usually involves making the necessary amount of targets aggro at each other, determining the order of attack, the chance to hit, evasion / dodging, applying damage vs. armor / resistance then against health, checking the target for death / incapacitation, applying potential counters, then advancing to the next target in time order. Whether you'll add "special" damage like additional spell damage on weapons and their resistances is up to you, and you'll also want to determine at what point the player can interrupt actions to use skills and spells, and what the indirect consequences of such interruptions are, if any (if spell casting is a lengthy affair, what happens to the opponent's attack? Is the caster helpless? for how long? etc).
Beyond those considerations, your coder (and you) will have to decide whether the combat system will be based on call_out or on heart_beat, which might influence the pace of the whole thing - and depends on how well DGD manages either in short time intervalls (although the best choice _seems_ to be heart_beat by default, this isn't always the case).
From your post, hoewer, it looks like neither you nor your coder are really at ease with the tasks at hand. Coding a mudlib isn't exactly easy to get into, I would only advise you to either realize you're in this enterprise for the very long term, or try to get both of you hired as staff on an established MUD for a couple of months to learn the ropes from experienced people.
|