Installing Areas

Posted by Asean Novari on Mon 14 Mar 2005 09:06 PM — 7 posts, 28,593 views.

USA #0
Ok.. I run a swr1fuss with the saquid's 2billion vnum snippet installed..

Problem #1
When I vassign myself a range of vnums that goes over 32767 it
instead assigns me a lower vnum and sometimes the high vnum is
a negative number..

Log: Admin: vassign self 80000 89999
Log: Updating area entry for Admin
Done.
Admin has assigned you the vnum range 80000 - 89999.
Log: Updating area entry for Admin

----------------------------------------------------------------------------
IMMORTAL DATA: Wizinvis [X] Wizlevel (105)
Bamfin: %s appears in a swirling mist.
Bamfout: %s leaves in a swirling mist.
Vnums: Room (14464 - 24463) Object (14464 - 24463) Mob (14464 - 24463)
Area Loaded [yes]


any ideas as to why this is going on... I can get around it
by using aset.. but i dont like having to get around things..


Problem #2
The area list.. when my area is in prototype form it shows on
the list.. the second I installarea it it dosent.. Any new
area I put on the area list dosent show up.. I can takes the
old ones off and put them back on and they dissappear then
reappear but the new ones never show..

Amended on Mon 14 Mar 2005 09:09 PM by Asean Novari
USA #1
New development as to the area list not displaying my areas...

it seems it just wont display my areas if they are over the number 32767..
Australia #2
Grep through the source and you will find a lot of hard coded values, some are 32000 and some that are 32Whatever the rest is, you will find that this is the cause of the probelm.

Make a define in mud.h for MAX_VNUM and give it a value that you wish to have as your max vnum( i have mine at 60K as i dont see any need for more), then replace all the hard coded values with MAX_VNUM.

Works a treat.

Peace.
Amended on Tue 15 Mar 2005 02:46 AM by Robert Powell
USA #3
You'll need to be sure anything that touches vnums is using an int now instead of a short. Including any display code that might be trying to show it as a short.

Glancing over the most recent FUSS packages I see that the code already treats the vnum ranges in area_data as int so I'm not sure what else was done. It was not necessary to apply Sadiq's patch.

do_score is also using %d which is the tag to display an integer value, so I'm not sure why your results differ. Are you certain you're using the SWR FUSS package?
USA #4
Im positive im using stock swr1fuss package..

I went through all of my files.. and looked for do_zones
I found 3 places in bd.c I had to change the number because it
was still at the old limit. After changing these numbers and
recompiling I can now get my zones with greater than 33k vnums
to show on the zones list....

the 3 places were do_vnums do_zones do_newzones

However, I still have the problem of the vassign messing up my
requested vnums.. *referr to problem 1 post 1* and I've looked
at the do_vassign function in act_wiz.c and I dont see how the
code could change the numbers..


Amended on Wed 16 Mar 2005 01:49 AM by Asean Novari
Canada #5
Well, there could be several problems, your numbers could be mangled by do_score, is it the same numbers in your pfile for example, and in the area? At least there is give you a way to cut down your search.
USA #6
When looking through do_score, does it give you a dash between the high/low vnums? Might have been something added in at some point to make it read 80k through (-) 89k...