Log in

View Full Version : Zone Unreachable


ChaiHal
12-15-2025, 06:09 PM
A friend and I ran into a strange issue yesterday. We decided to run around Blightfire Moors, a zone we'd never done before. Whilst I could zone in, he couldn't with the EQ Client (ROF2) giving the message

You are not experienced enough to pass through an inter-planar portal

We are both using the same client, as he has a copy of my EQ folder. The only difference I could see is that my account has status 250, whilst his is 0. Changing his account to 250 allowed him access.

Now, whilst this is a workaround, I'd like to at least try to understand why and fix it for this zone and any others which may have the same issue.

The zone log states

[12-15-2025 21:41:31] [Zone] [Info] Character [Chunky] does not meet minimum status requirement ([0] < [80])!
[12-15-2025 21:41:31] [Zone] [Info] Kicking character [Chunky] from zone, not allowed here (missing requirements)
[12-15-2025 21:41:31] [Zone] [Info] Routed player to public static instance [6] of zone [poknowledge] (202) version [0] long_name [The Plane of Knowledge] notes [Plane of Knowledge Unused]
[12-15-2025 21:41:31] [Zone] [Info] Client [Chunky] zone_id [202] instance_id [6] x [0] y [0] z [0] heading [0] ignorerestrictions [1] zone_mode [6]
[12-15-2025 21:41:32] [Zone] [Info] Routed player to public static instance [6] of zone [poknowledge] (202) version [0] long_name [The Plane of Knowledge] notes [Plane of Knowledge Unused]
[12-15-2025 21:41:32] [Zone] [Info] Reset to [1 Hour] from original remaining time [59 Minutes and 23 Seconds] duration [1 Hour] zone [PID (9289) Blightfire Moors (395)]
[12-15-2025 21:41:32] [Zone] [Info] Save for [Chunky] took [0.013430276]
[12-15-2025 21:41:32] [Zone] [Info] Save for [Chunky] took [0.069274329]
[12-15-2025 21:41:32] [Zone] [Info] Zone will go into an idle state after [60] seconds.

ChaiHal
12-16-2025, 06:14 AM
OK, so I've continued my ivestigations.

I've got the latest (pre-complied) executables.
My database is up to date (version 9328, bots_version 9054, custom_version 0).

I downloaded the latest sql files for creating a new database and checked that the data for "moors" in db_name.zones was correct. It was.

Then the zone log got me thinking, the entry

[12-15-2025 21:41:31] [Zone] [Info] Character [Chunky] does not meet minimum status requirement ([0] < [80])!

didn't sit right. Why the "[0] < [80]" when the min_level is 0 and the max_level is 255 for that zone.

Sure enough the min_status is set to 80. A test of changing this to 0, followed by a server restart, and now zoning in works! I'll do some more testing to be sure this is the fix, sometimes, whilst researching a fault, I confuse myself and other things I've tested may still be in place and I've jumped to the wrong conclusion.

Unfortunately I was unable to find a database schema, which I was hoping would indicate what min_status is actually for. Does anyone have a link to it?

Also, why is it set to 80 for a new database? Is there an issue with this zone and hence developers have flagged it to stop players entering?

EDIT: Zoning in tested by another user and all's fine. Changing min_status to 0 works! I've also logged onto a few random other servers and some have the same issue. If you're running a server might be worth checking?

Sturm
12-16-2025, 07:23 PM
Status is an account setting for your level of access.
80 = Guide
120-ish = Senior Guide (something like that)
255 = Uber GM (whatever it's actual name is. lol)

With a bunch of different ranks in between those.
This TSS zone is set to a min_status of 80 because it is not a released zone in the PEQ database. Only Guide's/GM's can travel there

This is not a mistake and is 100% intended, this is how you restrict regular players that have a status of 0 from going to places they are not allowed to go, using commands not intended for them, ect...

Happy Adventuring!

ChaiHal
12-17-2025, 08:59 AM
Thank you for the clarification, it all makes sense now.