Temple of Solusek Ro - Unknown zone

[Nightrider84]

http://www.eqemulator.org/forums/sho...light=nektulos

Check this post out, most of the problems have to do with the client_version_ mask of the clients trying to zone in. Basically it sends your character to a ghost zone that doesn't exist based on the clients trying to zone into it, because of whatever expansion they had at launch. Once the subnet mask is changed it should work. You may also need to go into your DB and remove any extra lines of code that send multiple clients to the same destination and just leave 1 that handles every client.

for example nektulos had a few lines that would send titanium clients into the classic version and anything above that into the new version of the zone. Thats partly the reason why titanium is the only one that can zone into old high pass and not the new clients.

I looked it up, Should be line 1,877 and 1,882 on your Zone_points DB that controls the zone in from lavastorm.

[Huppy]

Originally Posted by Nightrider84

Check this post out

As per my original post on this thread, I'm not having any problem zoning, it's just that message I get, when i do. Do you get that same message "Entering unknown zone" when you zone into soltemple ?

[Hyyr]

Originally Posted by Huppy

As per my original post on this thread, I'm not having any problem zoning, it's just that message I get, when i do. Do you get that same message "Entering unknown zone" when you zone into soltemple ?

How did you get your zone point to work? No matter how much I tampered with it, the zonepoint to Sol Temple (zone 80) from Lavastorm would always warp me into Sol A (zone 31) for some reason. There is only a single zonepoint for Sol A defined in Lavastorm, and it works as it is supposed to.

#zone 80 command works perfectly, and indicates "Entering Temple of Sol Ro" when I use it.

While the zonepoint is warping me to Sol A (instead of Sol Temple as it is supposed to) I DO get the message "Entering an unknown zone". I always assume these two issues were related, but it looks like they may be completely separate (since you somehow fixed the zoning issue, but still get the unknown zone message).