Temple of Solusek Ro - Unknown zone
Just a trivial question. I have the zone_point working properly from old lavastorm to soltemple, (as opposed to the quick fixes some are using) and still get that infamous "entering unknown zone". Still zones good, just that message. But I did notice, when using gm #zone 80, it gives the proper message, "Entering Temple of Solusek Ro.
Anybody have an inclination of what the gm command is doing right ? hahaha |
I am having a similar (but not exact) issue with that same zone on my own server.
I set up the warp-npc for Sol Temple and Najena. Najena works perfectly. On my main machine client, I can login to Sol Temple just fine. No problems at all. My brother on his client can log in as well, no problems. But when his wife logs in to Sol Temple (using a different machine & client), she warps into a box with the text "teleport to 262,9,0" stamped on it. It is very strange. Tests confirm her machine is the culprit, she can login to Sol Temple on the other machine just fine. She can spin in place, but not move at all. I just set up another client today on an old laptop. Everything works fine, and the files are exactly the same as my main client. But I get the same issue when logging into Sol Temple on this laptop. Now, here is the strange thing- stuck in my box, I do a /loc and I get the coordinates that match the "safe point" location for Lavastorm, even though I am in Sol Temple! So the command got the zone correct, but it warps me to the safe spot of the zone I just left. A zone loc confirms I'm in Sol Temple. Why would some clients work perfectly, and other (identical) clients do this same bug? Thanks |
Quote:
|
Quote:
|
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. |
Quote:
|
I skimmed over the part where you said you were zoning in fine. Generally when it says entering unknown zone the issues I stated are why.
Dunno why you get all passive aggressive anytime anyone attempts to help you. I'm sure you'll go real far lolol. And no. No one is getting that message but you. |
Quote:
#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). |
Quote:
target_y 261.96 target_x 36.72 target_y 1.19 target_heading 383.5 I also have any and all client_version_mask set to 4294967295 for all zone_points. Quote:
Quote:
Me and the Discovery channel: "Hey monkey, where do i find green bananas?" Splose and the monkey: "Green bananas are no good for you, but let me tell you how hard it is to get coconuts out of the tree." |
Quote:
Quote:
Quote:
I was telling you the possible reasons why you weren't able to zone in. Because.. Again.. I skimmed over the part where you said you were zoning in fine. Good luck figuring it out though guy http://www.eqemulator.org/forums/ima...ons/icon14.gif https://i.gyazo.com/0658a5b74b77a21f...1f0654d63e.jpg |
I agree 100% with Splose. Just a thought, When people are looking at posts to help someone.
Sometimes we miss a part of a post that may have important information. Such as you being able to zone in fine but the message still appears. Generally that may be due to how a sentence is worded and we just miss it. With that said, if people are just trying to help out and your being a prick about it then good luck and figure it out yourself huppy. |
Quote:
In that other thread "Spell support", I made a simple post about a particular spell and it's setting. What did Splose do ? went off on his opinions about Emulator and Titanium. But don't worry Splose, my posts are finished. You're obviously going to trainwreck every one of them, like you have a reputation for already, and had some deleted around here recently. Good luck. |
Quote:
Quote:
Quote:
Then you edited all your posts to say "Redacted thread derailed" like a douche. Quote:
Funny how you know 0 about that situation but you bring it up though. Turns out I was in the right. You should look into it. :) Edit: BTW your server is gonna be ASSSSSSS lol. |
Quote:
Quote:
I am just a newbie here, but I am very interested in getting my server up to snuff, and I am willing to do the work necessary, assuming I can get the information. I don't want to see anyone angry here, as we need all the input we can to fix the various issues with this massive & exciting project. Thanks all. |
Quote:
Check your zone_points table. Running this will give you the 2 zonelines that go to solro temple. I would try and make them virtual zone lines and see if that makes a difference. Code:
select * from zone_points where zone = 'lavastorm' and target_zone_id = 80; |
Quote:
Quote:
So be it Splose. I was selfish and wasn't there for you for all your other servers. TownshipEQ, EQAwakened, Area51, EQInfinity, (kingly's) Rise of Norrath. Whatever happened to those ? And now EQEmpires. Don't worry. I will help promote yours too. (all over the internet) ;) Be seeing you Splose ..... |
Quote:
Hyyr, I went ahead and copied my 2 working zone lines from my zone_points table as an update query. I would recommend backing up your zone_points table and running these 2 queries. They will change whatever you have to what I have (assuming yours is any different). Note: If your database is not named 'peq' you will have to change it accordingly. I took these from a stock PEQ db with 0 changes so I would assume our schema should line up. The 2 IDs my zone_points have are 1877 and 1882 if yours are different update it at the end of the queries. Code:
UPDATE `peq`.`zone_points` SET `zone` = 'lavastorm', `version` = 0, `number` = 20, `y` = 0, `x` = 0, `z` = 0, `heading` = 0, `target_y` = 250, `target_x` = 56, `target_z` = 3, `target_heading` = 65, `zoneinst` = 0, `target_zone_id` = 80, `target_instance` = 0, `buffer` = 0, `client_version_mask` = 4294967295, `min_expansion` = 0, `max_expansion` = 0, `content_flags` = NULL, `content_flags_disabled` = NULL, `is_virtual` = 0, `height` = 0, `width` = 0 WHERE `id` = 1877; |
Quote:
I'm not sure how the first set of coordinates works, as it doesn't appear to match anything relevant. Nor do I know why there was a second entry for the same zone, with 0,0,0 as the first set. Could this be the reason I am having problems? I can add this line (ID1877) back in, but why would I need two zone points, when the client masks are the same? I made the slight zone in modifications suggested above, but I still get ported into zone 31 (Sol A) instead of zone 80. What do you mean by "virtual zone"? I did set up the invisible-NPC-zoning trick, but I would like to get the actual zone point working if I can. Is that what you meant? Thanks very much in advance! |
I'm working on your response. I'll let you know how it works. Thanks!
|
Quote:
Code:
INSERT INTO `peq`.`zone_points`(`id`, `zone`, `version`, `number`, `y`, `x`, `z`, `heading`, `target_y`, `target_x`, `target_z`, `target_heading`, `zoneinst`, `target_zone_id`, `target_instance`, `buffer`, `client_version_mask`, `min_expansion`, `max_expansion`, `content_flags`, `content_flags_disabled`, `is_virtual`, `height`, `width`) VALUES (1877, 'lavastorm', 0, 20, 0, 0, 0, 0, 250, 56, 3, 65, 0, 80, 0, 0, 4294967295, 0, 0, NULL, NULL, 0, 0, 0); |
Well, I added the other zone point back in & double-checked everything. I still get sent to zone 31 instead of zone 80 when I hit the Sol Temple zonepoint. When I use #zone 80 it works perfectly. The zone-in to Sol A also works where it should. Very odd, indeed.
I may re-enable my npc zoner for the time being, as I do have better things to work on right away (like repopulating Lavastorm). I'll get back to this later, unless anyone has something else for me to try. Does anyone know what the deal is with the target_heading setting? The range appears to be 1-512, but it doesn't always work, and I've seen some rows set to absurd numbers like 999 & 20000 & such. Is there a resource for learning what all of the parameters for all of these fields are? Thanks very much! |
Quote:
Thanks for all of your help. Working on this thing is just as fun as playing EQ. |
Quote:
Yeah.. Back in the day we used to have to multiply the heading x2. Can't remember why it was like that as it was a long time ago but those could just be old and a result of that. I believe that thing has since been fixed because I've been using just the heading my #loc gives me and it has been working fine. You can check some of these pages out. They will sometimes tell you what everything is. https://eqemu.gitbook.io/database-sc...ries/zone/zone |
All times are GMT -4. The time now is 03:24 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.