Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
auth_update crash
Dec 23, 2017, 10:15 pm
By Remcon
check_tumble
Dec 18, 2017, 7:21 pm
By Remcon
parse description bug
Dec 15, 2017, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Users Online
CommonCrawl, Yandex, Majestic-12

Members: 0
Guests: 9
Stats
Files
Topics
Posts
Members
Newest Member
478
3,708
19,242
614
BenitoVirg
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Bugfix Lists » AFKMud Bugfix List » AFKMud Bug Archive » [Bug] Repairset command is no...
Forum Rules | Mark all | Recent Posts

[Bug] Repairset command is not recognizing mob names or vnums
< Newer Topic :: Older Topic > AFKMud 1.64

Pages:<< prev 1 next >>
Post is unread #1 Mar 6, 2005, 3:17 pm   Last edited Nov 13, 2005, 11:53 am by Samson
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Bug: Repairset command is not recognizing mob names or vnums.
Discovered in: AFKMud 1.64
Danger: Medium - Unable to use command properly.
Found by: Celestria
Fixed by: Celestria

---

shops.c, do_repairset

Locate:

   if( !( keeper = get_char_world( ch, argument ) ) )
   {
      send_to_char( "Mobile not found.\n\r", ch );
      return;
   }


Change to:

   if( !( keeper = get_char_world( ch, arg1 ) ) )
   {
      send_to_char( "Mobile not found.\n\r", ch );
      return;
   }


You just have to stop and wonder how something like this escapes detection for so long. In any case, the problem arises from using the wrong argument variable to look for the new repairshop mob. arg1 holds the intended target, not argument. This bugfix technically existed in the 1.7 release which was just made, but since there had yet to be any downloads of the new code, it was added at the last second as a 1.64 fix. This has to be some kind of new record
       
Pages:<< prev 1 next >>