You wrote: > >CC: Steve <quickey@cyberverse.com> > >> I am planning a generic polymorph system, to allow for lycanthropy, >> polymorphing, and other similar things. If anybody has already done >> I was wondering what you did about the following: >> 1. Char QUITS or RENTS , do they switch back to their original >> when they do this. And if so, is save_char already written to >> the correct one or will it save the morphed version. >> 2. Also i was thinking of using the original/character structures >> like in switch, is this wise? >> 3. What about EQ, should i take it away from the other character, >> give it or should i just make a copy and take the orig >> char_from_room() him. > >I was implementing some morphing code for mobiles a while back; the >actually implemented to a permanent form in the game was a werewolf. >would walk around as a Midgaard citizen (level 8), and if it was >attacked, it turned into a level 15 werewolf until it finished combat. > >All I changed in the data structure was the description, the name and >alias list. The next step was to change the level (perhaps experience >for coder realism) and the stats. As far as players go, it would all >depend on the character. If the character changes due to a full moon, >renting or quitting would probably reset the lycanthropy to normal. >Equipment should transfer, however clothes or armour would probably >damaged in the process if the character grows in either transformation. > Suggestion... look at silly mud's code for polymorph spells.... >From what I"ve been told, to polymorph characters, you must be careful how they're handled, storing the original character, and handleing thing's properly if a crash, or when the polymorphed character dies...
This archive was generated by hypermail 2b30 : 12/07/00 PST