Temple of Solusek Ro - Unknown zone

[Splose]

Originally Posted by Hyyr

Splose, Huppy was actually responding to my question with that statement. My apologies for adding confusion to the thread. I asked the question I did because I was having the same issue Huppy was, except I was also having problems zoning.


I am using the Titanium client, as I want to use as many of the original zones as I can. I am also getting the message on multiple machines. All of these are clean Titanium installs. Going by your list there, if we assume the client is OK for now, that leaves the zoneserver, or the DB tables. If the former I assume we are stuck with the issue, if the latter, where would be the best place to look in the DB for this?

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.

No worries. I don't think anyone is really getting angry just kinda tired of trying to help someone and they're constantly a douche to you when they answer you lol.

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.

select * from zone_points where zone = 'lavastorm' and target_zone_id = 80;

[Hyyr]

Originally Posted by Splose

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.

I actually only have a single entry for zone 80. This is ID1882. There was an ID1877 entry that I deleted, as it was identical to the other except the first set of coordinates y x z (not target_y, etc) which were set to 0,0,0.

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!

[Hyyr]

I'm working on your response. I'll let you know how it works. Thanks!

[Splose]

Originally Posted by Hyyr

I'm working on your response. I'll let you know how it works. Thanks!

Since you deleted one you can probably just delete the other one and run these instead. Might be a bit simpler.

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);
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 (1882, 'lavastorm', 0, 88, 1360, -1650, -105, 0, 250, 56, 3, 999, 0, 80, 0, 0, 4294967295, 0, 0, NULL, NULL, 0, 0, 0);

[Hyyr]

Originally Posted by Splose

Since you deleted one you can probably just delete the other one and run these instead. Might be a bit simpler.

Those match my zone point entries perfectly. There must be something else wrong in the database.

Thanks for all of your help. Working on this thing is just as fun as playing EQ.

[Hyyr]

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!

[Splose]

Originally Posted by Hyyr

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!

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