Are you sure the client you're using has the old zones? Would you mind using #zone to go there and see if it works, if it doesn't, that's why it's putting you in Crescent Reach, if you can go there, the problem lies elsewhere.
|
Quote:
Quote:
As per the piece of code you quoted earlier: Code:
in_pp->x = atof(row[0]); Quote:
|
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? Code:
[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 |
Can you post some pictures of your rule_values and start_zones settings perhaps?
|
Quote:
http://i.imgur.com/5oExaqE.png 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. http://i.imgur.com/ulEPyqS.png 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. |
Here is what my settings look like:
Rule Values: http://i.imgur.com/VtujPC1.png Start Zones: http://i.imgur.com/PezjdS7.png |
Some "people" dont appreciate being referred to as "people" when said "person" is trying to help, instead they get this rude note,
Quote:
Quote:
Quote:
|
Quote:
This seems like a really stupid problem to have, and simply changing the start_zone should work, but it doesn't, and I'm at a loss as to why specifically because I'm new to this and don't have all of the answers. Kingly_Krab You seem to have everyone spawn in the same zone, though. That's fine, but what I want to do is simply make it so that newbies start in the old Freeport instead of the new one, and I'm starting to suspect that it may require a source code change to do that. I still don't know why my server is still saying "WHERE zone_id = 383", but that's why it's not working. It's still looking for the Freeport revamp, and when it fails to find that, it defaults to Crescent Reach. |
What client are you using? I know on live you can no longer start in anywhere but CR, and I'm not sure if RoF acts like this and it could be causing problems?
|
Last resort question, did you restart your server or #reloadallrules after doing all of this? Or are you doing it live without reloading or anything?
|
char_create_combinations table is what your looking for, change that plus the start_zones table
|
Quote:
|
Quote:
|
Quote:
|
Here is the code that processes the create character zone selection: https://github.com/EQEmu/Server/blob...ient.cpp#L1473
I don't have a database in front of me or I'd trace the logic... |
All times are GMT -4. The time now is 11:14 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.