Highpass unknown zoning issue in titanium client?

[lonmoer]

Hello,

I set up a new server with just the default peq stuff and bots with no other changes. I'm trying to zone into highpass but it shows that im zoning into "unknown zone" and then i can't log in my character at all.

I've searched the forum and found similar problems but their issue seems to be that they're using SoD or RoF clients that don't have the old zone files and that is not the issue in the titanium client.

The closest thing I could find was this thread:

https://www.eqemulator.org/forums/showthread.php?t=42531&highlight=unknown+highpass

but i've already checked those points in my DB and they exist. Any ideas as to what my server is doing?

Also the log shows this:

[02-22-2022 :: 12:29:03] [World] [Info] Sending client to zone [highpasshold]

but the titanium client doesnt have highpasshold files. Is my server trying to direct me to the new highpass?

[Firepaw]

Generally the accepted solution to this problem is to find the correct zone file. The discord is very active and might be able to help you more on how exactly to get these files.

[lonmoer]

Yeah, that was my next thought so I downloaded the rof2 client and placed the highpasshold files in there too but the character was still stuck in the unknown zone.

[Nukerella]

Have you tried loading using the rof2 client instead?

There are multiple files for each zone and from what has been reported to me over the past 8 years is some zones just don't work with titanium.

[lonmoer]

Yes, i tried it with a clean rof2 client and it did the same thing.

[image]

You can’t just take maps from new clients and hope to inject them in old.. zone names are hard coded in titanium you should be going to “highpass” not highpass hold. You have the new zone points need the old ones for titanium

See previous discussion http://www.eqemulator.org/forums/showthread.php?t=39844&highlight=Highpass+zone+point&page=2

[krauser1]

1. make sure the zone-passing area is point the new zone or the old one in ur db
2. tried to use the gm command : #zone *** to confirm if the zone is available.