[crossfire] More server speed reducing the objects number

Mitch Obrian mikeeusaaa at yahoo.com
Sun Oct 16 14:28:42 CDT 2005


Also the corpses should look bloodied up, and if
someone consumed the monster totaly with fire spell
etc then a corpse shouldn't be dropped.

--- Mitch Obrian <
     mikeeusaaa at yahoo.com
     > wrote:

>
      The corpse idea isn't a terrible idea /if/ we have
     >
      corpse pics for all the various monsters.
     >
     
     >
      Also 2x2 creatures should have a 2x2 corpse.
     >
     
     >
      This can be done if we can get the talented artists
     >
      who created our current monster pics in on the job.
     >
     
     >
      Also, we need a new type. Container-food-weapon. So
     >
      we
     >
      can still eat corpses... and can use them as a
     >
      weapon
     >
      (ala nethack)... not an effective weapon though :P.
     >
     
     >
      --- Alberto Sáez Lodeiros <
      cerzeo at gmail.com
      > wrote:
     >
     
     >
      > > Mark Wedel wrote:
     >
      > >   Downsides:
     >
      > >
     >
      > > 1) Monsters that pick up loot would now need to
     >
      do
     >
      > more work (instead of the
     >
      > > objects of 5 dead creatures merging, they would
     >
      be
     >
      > all seperate, instead of the
     >
      > > common objects merging.
     >
      > 
     >
      > Monsters can pick up only the objects over the
     >
      flor,
     >
      > but not into the
     >
      > corpse-container.
     >
      > Or maybe, when the monster is over the
     >
      > corpse-container, check the
     >
      > object into it, and then move one random object
     >
      from
     >
      > corpse-container
     >
      > to monster inventory.
     >
      > 
     >
      > > 2) point 2 from above- fire effects may now have
     >
      > more objects to check for
     >
      > > destruction because they don't merge.
     >
      > 
     >
      > When a fire spell (for example) burns the corpse,
     >
      > you can make a
     >
      > simple python routine, which destroy all objects
     >
      > into the
     >
      > corpse-container. Or simply, the same thing that
     >
      > occurs when fire
     >
      > reaches a chest, which is also a container.
     >
      > 
     >
      > >   All that said, I'd think this should be more
     >
      > driven by actually thinking this
     >
      > > is a good or bad feature, not memory or
     >
      > performance reasons.
     >
      > 
     >
      > You can set a timer in the corpse which will
     >
      destroy
     >
      > the corpse and
     >
      > all its contens, past 5 minutes, for example. In
     >
      > this way, we will not
     >
      > wait for server resets to clean the maps.
     >
      > 
     >
      > --
     >
      > -- Powered by Fedora Core 4 Linux --
     >
      > -- AMD Duron 1.3 GHz --
     >
      > -- 512 Mb RAM DDR 400 MHz --
     >
      > -- HDD 80 Gb 7200 RPM --
     >
      > -- GeForce 2 MX 400 --
     >
      > 
     >
      > _______________________________________________
     >
      > crossfire mailing list
     >
      > 
      crossfire at metalforge.org
      
     >
      >
     >
     
     
     http://mailman.metalforge.org/mailman/listinfo/crossfire
     
>
      > 
     >
     
     >
     
     >
     
     >
     
     >
     
     >
      __________________________________ 
     >
      Yahoo! Mail - PC Magazine Editors' Choice 2005 
     >
      
      http://mail.yahoo.com
      
     >
     
     >
      _______________________________________________
     >
      crossfire mailing list
     >
      
      crossfire at metalforge.org
      
     >
     
     
     http://mailman.metalforge.org/mailman/listinfo/crossfire
     
>
     
     


		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free.
     http://music.yahoo.com/unlimited/
     
    


More information about the crossfire mailing list