How do I stop players from spawning in Crescent Reach?

[Lucia Moore]

Update

Okay, I'm getting an error message now (or, at least, I'm looking at the correct window now) and I can see what's screwing up, but have no idea why, unless it's something hardcoded into the client or server?

[Status] SoF Start zone query: SELECT x,y,z,heading,bind_id FROM start_zones WHERE zone_id=383 AND player_class=2 AND player_deity=204 AND player_race=1

No start_zones entry in database, using defaults

So, if I changed that start zone entry in the database to 9, and I have the whole "separate SoF start zone" rule disabled, why is it still looking for a 383 entry in the database?

[Kingly_Krab]

Can you post some pictures of your rule_values and start_zones settings perhaps?

[Lucia Moore]

Originally Posted by Kingly_Krab

Can you post some pictures of your rule_values and start_zones settings perhaps?

Sure.


There's the relevant part of my rules. As you can see, I have SOFStartZoneID set to -1, so the server shouldn't care if the player is using an SOF+ client or a Titanium client.


These were all previously set to either 382 or 383 (the newer Freeport zones). I changed them all to 9 (freportw, the classic West Freeport).

As I indicated above, I am receiving an error output from my server because, for some reason, it is still trying to spawn players in zone 383, and is erroring out because it cannot find an entry for 383, which make sense, because I removed it, because I don't want players spawning in 383.

An idea just occurred to me...

There are two entries...a zone_id, and a start_zone....which one of those ACTUALLY controls where you spawn? Is it possible that start_zone is just what the server looks for, but zone_id is the actual zone it attempts to spawn you in?

Edit: Nevermind, that's not it. zone_id is what it looks for AND where it spawns you. I just checked. So the real question is WHY is it asking for 383? Is the CLIENT asking for 383? If so, how do I change that? I don't want ALL of my players spawning in the same zone, so using that sort of workaround isn't really acceptable.