Login
User Name:

Password:



Register

Forgot your password?
 features of a good MUD
Jul 16, 2025 3:22 am
By Siumre
 Dusting off the old code...
Jul 16, 2025 2:42 am
By Twoun1980
 A SMAUG Collaboration
Jul 15, 2025 10:31 pm
By Siumre
Overland with Bitmaps
Jul 4, 2025 11:57 pm
By Samson
void nanny_get_new_race -- comm.c
Mar 13, 2025 7:08 am
By Elwood
SWFotEFUSS 1.5.3
Author: Various
Submitted by: Samson
SWRFUSS 1.4.3
Author: Various
Submitted by: Samson
SmaugFUSS 1.9.8
Author: Various
Submitted by: Samson
AFKMud 2.5.2
Author: AFKMud Team
Submitted by: Samson
SmaugFUSS 1.9.7
Author: Various
Submitted by: Samson
Users Online
GPTBot, Anthropic, AhrefsBot, Google, Amazonbot, Bing, DotBot, Remcon

Members: 1
Guests: 5
Stats
Files
Topics
Posts
Members
Newest Member
507
3,812
19,728
596
Twoun1980

» SmaugMuds » 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 12:10 pm   
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,708
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 >>