Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
Bug in get_exp_worth( )
Oct 10, 2017, 1:26 am
By GatewaySysop
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
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Users Online
DotBot, CommonCrawl, Yahoo!

Members: 0
Guests: 10
Stats
Files
Topics
Posts
Members
Newest Member
477
3,705
19,232
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Bugfix Lists » AFKMud Bugfix List » [Bug] E resets produced by in...
Forum Rules | Mark all | Recent Posts

[Bug] E resets produced by instaroom have invalid format
< Newer Topic :: Older Topic > AFKMud 2.01

Pages:<< prev 1 next >>
Post is unread #1 Oct 14, 2007, 10:10 am
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Bug: E resets produced by instaroom have invalid format
Danger: Medium - Leads to minor reset corruption when using the automated tools
Discovered in: AFKMud 2.01
Found by: Dialan
Fixed by: Samson

---

reset.cpp, add_obj_reset

Locate:
else
      room->add_reset( cm, ( cm == 'P' ? iNest : 0 ), obj->pIndexData->vnum, v2, v3, 100, 100, 100, 100, -2, -2, -2 );


Change to:
   else if( cm == 'P' )
      room->add_reset( cm, iNest, obj->pIndexData->vnum, v2, v3, 100, 100, 100, 100, -2, -2, -2 );
    else
      room->add_reset( cm, obj->pIndexData->vnum, v2, v3, 100, 100, 100, 100, -2, -2, -2, -2 );


A subtle yet noticeable problem when using the automated instaroom or instazone commands to populate resets. Equip resets were still setting up the nesting value of 0 even though the rest of the code had been altered so that this first value was no longer needed. This error crept in during the conversion to the KEY'd area file formats.
       
Pages:<< prev 1 next >>