Post: #1

Hi guys, I decide today to update again my server.
To my surprise after updating the server, I started to have a very crazy reading on map 0. My though, its some problem on my sphere folder.

So... I download a clean no mod sphere folder. Straight from sphereserver.
(lastest revision 16-4-2014).

And to my surprise I got the same readings.
here is what i am talking about:



in my console I got:
and

I have tried to change in sphere.ini
both ways... the same problem remains.

Any ideas???

---

my UO its the latest before change to UOP.
Client version: 7.0.23.1 (patch 65)

---

I decide to download the latest UO version. Lets see...

Post: #2

Comment all maps ;

//MAP0=7168,4096,64,-1
//MAP2=2304,1600,32,2,2
//MAP3=2560,2048,32,3,3
//MAP4=1448,1448,8,4,4
//MAP5=1280,4096,64,5,5

Then state correct map scripts in spheretables ;

scripts/maps/sphere_map0.scp
scripts/maps/sphere_map0_ml.scp
scripts/maps/sphere_map1.scp
scripts/maps/sphere_map2.scp
scripts/maps/sphere_map3.scp
scripts/maps/sphere_map4.scp
scripts/maps/sphere_map5.scp
scripts/maps/sphere_map_points0.scp
scripts/maps/sphere_map_points0_ml.scp
scripts/maps/sphere_map_points1.scp
scripts/maps/sphere_map_points2.scp
scripts/maps/sphere_map_points3.scp
scripts/maps/sphere_map_points4.scp
scripts/maps/sphere_map_points5.scp

Only prefer MAP settings if you have not original maps like custom map. Spere can recognize the size of original maps according to mul files that you state in MulFiles=mul/

///Note- This is correct if you have 56b-pre release otherwise, neglect what I suggested.

Post: #3

Thx! But i solved by re-installing an updated version of UO.

Post: #4

Avatar, as of a few revisions ago, these MAP settings in sphere.ini are mandatory to activate a map except for map0.

Post: #5

It's not recommended update sphere_map*.scp files with resync, you must restart the server
these console errors are not a problem at all, its just because you updated the script without restart the server

but anyway if you find something wrong just report it and we will fix it

Post: #6

Certainly the new files are wrong:

-Regions with the same defname as another already readed.

and

-Duplicated:

Post: #7

I found a small conflict on shrine regions, shrines on felucca and ilshenar are using the same defname (eg: a_shrine_valor, etc). This will reproduce the "Adding rect to region with different map" console error, will be fixed on next sphere_map2.scp update

but about the "conflicting teleport", there's nothing wrong, maybe you just updated the script with a resync instead restart the server, this will spam the console with many "conflicting teleport" errors but it's not really a script error. Maybe this occour because sphere create a "teleport list" on server startup, and when the script got resync, sphere will try to build a new "teleport list" again but it already exists

Post: #8

Removed /maps/ and copied over the SVN ones, restarted Sphere and it's showing them on each startup: http://pastebin.com/PeEm9LaX

There are repeated names for teleports:

Post: #9

bah you're right
yesterday I moved ML teleporters from map3 to map0_ml file but I forgot to previously remove it from map3. I fixed this some minutes ago, now everything should work fine

Post: #10

@Ben
Thanks Ben. Since i stuck the point which is 56b pre-release,There should be lots of new adds. Need to finish reading revisions from beg to end. It looks I missed some points.