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, Yahoo!, DotBot

Members: 0
Guests: 14
Stats
Files
Topics
Posts
Members
Newest Member
478
3,708
19,242
612
Jacki72H
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Bugfix Lists » AFKMud Bugfix List » AFKMud Bug Archive » [Bug] Combat damage does not ...
Forum Rules | Mark all | Recent Posts

[Bug] Combat damage does not affect all available wear locations
< Newer Topic :: Older Topic > AFKMud 1.7

Pages:<< prev 1 next >>
Post is unread #1 May 23, 2005, 5:18 pm   Last edited Nov 13, 2005, 11:28 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: Combat damage does not affect all available wear locations.
Discovered in: AFKMud 1.7
Danger: Trivial - Shortened number range.
Found by: Txzeenath
Fixed by: Txzeenath

---

fight.c, damage

Locate:
   if( dam > 10 && dt != TYPE_UNDEFINED )
   {
      /*
       * get a random body eq part
       */
      dameq = number_range( WEAR_LIGHT, WEAR_EYES );
      damobj = get_eq_char( victim, dameq );
      if( damobj ) 


Change to:
   if( dam > 10 && dt != TYPE_UNDEFINED )
   {
      /*
       * get a random body eq part
       */
      dameq = number_range( WEAR_LIGHT, WEAR_ANKLE_R );
      damobj = get_eq_char( victim, dameq );
      if( damobj ) 


The only thing this change does is make it possible to damage items worn on the newer locations which were a part of the Smaug 1.4a code update. This bug is also present in the Smaug 1.6 FUSS code.
       
Pages:<< prev 1 next >>