I do understand what everyone is saying about not using
POS_MOUNTED and just checking for the presence of a
mount.
BUT, if you are mounted, you are not standing, now are
you? Hence my desire for a new position - say what
you mean, mean what you say :p
Adding positions has got to be one of the more
annoying things in a mud... I'm thinking I'll just do
away with all positions as they are now and go to some
sort of state thing, possibly using bitvectors. While
it will be more code, it should make adding new
positions easier (say, flying or held).
---
eglamkowski@angelfire.com
http://www.angelfire.com/nj/eglamkowski/null.html <- Null webring
http://www.angelfire.com/nj/eglamkowski/eia.html <- EiA webring
Angelfire for your free web-based e-mail. http://www.angelfire.com
+------------------------------------------------------------+
| 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 : 12/15/00 PST