My area crashes the server! Why?

Posted by Oblisgr on Wed 18 Sep 2019 07:46 PM — 5 posts, 23,266 views.

#0
Hello, i had built a new area (actually replacing newacad. are) using the editor and everything worked fine. Until i desided to change the vnums of everything so i can seperate object types.

Anyway... after changing the vnums my pre-combiled server always fail to start, because it finds errors in my area. I have checked everything and found no error. The editor starts and saves the area just fine. But the server wont start.

Can anyone understand what's wrong?

I share my are file:

https://sharefiles.app/download/5073dfdc93a55fe7f4837f55784adc0407b26286

Below i will provide the error report:

Quote:

gods.are : Rooms: 1200 - 1201 Objs: 1200 - 1200 Mobs: 1200 - 1200
limbo.are : Rooms: 1 - 43 Objs: 2 - 99 Mobs: 1 - 99
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3594
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (1) 'M': mobile 100002 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3598
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (5) 'M': mobile 100003 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3606
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (13) 'M': mobile 100004 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3612
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (19) 'M': mobile 100005 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3642
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (49) 'M': mobile 100006 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3652
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (59) 'M': mobile 100001 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3664
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (71) 'M': mobile 100007 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3673
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (80) 'M': mobile 100008 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3681
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (88) 'M': mobile 100009 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3686
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (93) 'M': mobile 100010 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3692
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (99) 'M': mobile 100011 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3696
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
Wed Sep 18 23:30:10 2019 :: [*****] BOOT: Load_resets: newacad.are (103) 'M': mobile 100012 doesn't exist.
Wed Sep 18 23:30:10 2019 :: [*****] FILE: newacad.are LINE: 3705
Wed Sep 18 23:30:10 2019 :: [*****] BUG: Get_mob_index: bad vnum 0.
USA Global Moderator #1
Quote:
https://sharefiles.app/download/5073dfdc93a55fe7f4837f55784adc0407b26286

I don't see any file there.

Have you considered the possibility that your problem is indicated by this message?
Quote:
mobile 100002 doesn't exist
Australia Forum Administrator #2
I can't see any files either so it is impossible to say.
Australia Forum Administrator #3
Which version of Smaug exactly? The more modern ones are less likely to crash.

If I remember correctly the older code just assumed that certain vnums existed, without checking. If you removed such a vnum, that could cause a crash.

You could look into exactly what the crash is about with gdb:


http://www.gammon.com.au/gdb
#4
I just returned the vnums to the previous numbers.
10400 and so on
and it worked back again