Mark Wedel wrote: > - Change inscription - instead of looking at range field of the player, > have the spell to be inscribed part of the inscription command, eg > 'inscribe scroll of identify' > (is this still something that needs to be done?) > Yes. When inscribing spell scrolls, one needs to do something along the lines of "mark scroll-to-inscribe-over; cast meteor swarm; use_skill inscription". The change suggested there would make it so one would use something like "mark scroll-to-inscribe-over; use_skill inscription meteor swarm" instead.
> - Generalize the code better - split between 'rules' and 'engine' > (see TODO for more info - wonder if we really want to go that route - the > code > re-orgs as suggested is different from this, so maybe it just goes away as > something TODO?) Personally I don't think we want to go that route, however the suggested code re-orgs such as what I proposed a while back in the mailing list, would as a side affect make splitting the 'rules' and 'engine' easier, if at any point we decided we wanted to. IMHO we should do the code re-orgs and decide if we want to split the 'rules' and 'engine' after. Alex Schultz _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
