> ------------------------------------------------------------------
> Its funny that this question should be brought up. I tried the same
> thing you are talking about, with no luck. Basically, I prompted for
> race first, then (depending on which race was selected) I sent a
> class menu to the descriptor. By making several class menus, it was
> easy to do, but the problem was that the player could still choose
[SNIPP]
> Sorry about the big reply, I don't know if this helps at all. If
> anyone is interested in a snippet on the subject, let me know and
> I'll try to finish it soon.
> FIRE
I don't think that's a good design choice... mainly for roleplaying
(yesterday I wuz a nice wild elf with tattoos on my face, but now i'm
a big stinky troll from the Vast Swamp) but this method is prone to
"cheats"...
Imagine: if i wanna cast spell, i transmute myself to an elf, if i
wanna regen HP, into a troll, if i need to fly, into an
avariel/urd/half-dragon... and so on. The player are very able to find
all the weak spots on the system =)
By the way you should modify the function parse_player_race() to take
into account the race/class restriction you need.
Greetings from Italy and excuse me for my bad Englis, PLEASE =)
--
Razor [Chief of Darkmud: Breed of Darkness @ darkmud.gamersrevolt.com
4000]
If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/10/01 PDT