Changes

:: For example a bucketon the ground.

:: For example a spongein one hand.

:: For example a broomin both hands.

Quite simple. When the unit is loaded, it collect collects all mover desc containing all tags from the <code>desc_tags</code> property and all mover anim containing aall all tags from the <code>anim_tags</code> property. When the mover is generated, it randomly choose chooses one of the collected mover desc and then it try tries to choose one of the collected movert mover anim which uses use the '''same skeleton''' as the choosen mover desc model . This is important because sometimes you want to have group containing models with different skeletons and animations with different skeletons. But you want only valid model-anim combinations. '''For example''' group of walking men and women where men use different skeleton than women. '''Optimization''' Because engine ensures that only valid model-anim combinations will be created, it may seem that animation tags should contain only tags describing the animation activity. But because the model-anim combinations are choosen in the moment of mover generation, we want to limit the combination pool as much as possible. Because of that mover anim tags should contain (apart from the choosen activity itself) tags describing compatible mover desc mode. In <code>mover_anim</code> the example above these tags are <code>human</code> and <code>man</code>. And in the related mover group use these tags in <code>anim_tags</code>. In the example it is the tag <code>man</code>.