Bug: Run command does not stop the player if combat begins
Danger: High - Game exploit condition. Could be used to circumvent required events.
Discovered in: AFKMud 1.77
Found by: Zeno
Fixed by: Samson

---

act_move.c, do_run

Locate:

         if( ( pexit = find_door( ch, arg, TRUE ) ) != NULL )
         {
            if( ch->move < 1 )
            {
               send_to_char( "You are too exhausted to run anymore.\n\r", ch );
               ch->move = 0;
               break;
            }
            if( move_char( ch, pexit, 0, pexit->vdir, TRUE ) == rSTOP )
               break;
         }

Below that, add:

         if( ch->position != POS_STANDING && ch->position != POS_MOUNTED )
         {
            send_to_char( "Your run has been interrupted!\r\n", ch );
            break;
         }

Locate:

      while( ( pexit = find_door( ch, arg, TRUE ) ) != NULL )
      {
         if( ch->move < 1 )
         {
            send_to_char( "You are too exhausted to run anymore.\n\r", ch );
            ch->move = 0;
            break;
         }
         if( move_char( ch, pexit, 0, pexit->vdir, TRUE ) == rSTOP )
            break;

Below that, add:

         if( ch->position != POS_STANDING && ch->position != POS_MOUNTED )
         {
            send_to_char( "Your run has been interrupted!\r\n", ch );
            break;
         }

As written the run command will allow anyone using it to fly right past an aggro mob that might be in the room. If the mob initiated combat, that combat does not break the run loop since it has not checked to be sure you're still in the right position while moving. Anything which takes you from either standing or mounted should halt the run, so this will also catch anything else which causes positions to change.