The reason the code is ther is pretty simple. Basically, it was believe that if you are setting the stand_still flag, the object should not be animated. A poor assumption is made that the object being modified has no need for speed if it isn't getting animated. An example of this are the gems - if the artifact version is not animated, the gem object has no need for the speed. It probably won't break anything to remove the clearing of speed. The effect this will have is more object will be on the active list, which may have an effect on performance. crossfire-cvs-admin at lists.sourceforge.net wrote: > > Update of /cvsroot/crossfire/crossfire/common > In directory usw-pr-cvs1:/tmp/cvs-serv18952 > > Modified Files: > treasure.c > Log Message: > Small change to treasure.c: artifacts were getting their speed > set to zero for some reason. This had the effect of freezing > artifact-generated monsters. > > Commenting this out didn't seem to break the images for > other artifacts. > > PeterM > > Index: treasure.c > =================================================================== > RCS file: /cvsroot/crossfire/crossfire/common/treasure.c,v > retrieving revision 1.10 > retrieving revision 1.11 > diff -C2 -r1.10 -r1.11 > *** treasure.c 2001/04/21 01:22:43 1.10 > --- treasure.c 2001/04/25 07:46:57 1.11 > *************** > *** 1174,1178 **** > if (QUERY_FLAG(change,FLAG_STAND_STILL)) { > CLEAR_FLAG(op,FLAG_ANIMATE); > ! op->speed = 0.0; > update_ob_speed(op); > } > --- 1174,1178 ---- > if (QUERY_FLAG(change,FLAG_STAND_STILL)) { > CLEAR_FLAG(op,FLAG_ANIMATE); > ! /*op->speed = 0.0; */ /* why was this done? */ > update_ob_speed(op); > } > > _______________________________________________ > Crossfire-cvs mailing list > Crossfire-cvs at lists.sourceforge.net > http://lists.sourceforge.net/lists/listinfo/crossfire-cvs