and...now we're all havign this issue. Not with the zoning, but with our extended target windows. the game says we need to own underfoot. Thing is, we all had the extended target window until yesterday or this morning, now it's disappeared. It's not like we patched or anything, so what's the deal?

i tried changing accounts owned in account but that didnt do anything unless i have to restart server but that would make no sense, /camp desktop and back should be more than sufficient for account flags. I would understand if it was never there, but why would they all disappear now? Even on my GM account

I thought i was going to get it fixed when i found the other expansions setting (variables) thats in hex powers (-1), then doing the math setting it to include RoF for all, but that didn't work. However, before I realized my extended target window had also disappeared, I'd spent an hour trying to fix the zone-in from BFM to CR to no avail. It zones you in at a heading that will zone you right back out again, but no matter how I tried to make it take effect and regardless of the correct heading now showing in the db, it still zones in facing back out. grr. [if anyone's curious, most know 0 is base, 1 is 1, 255 is 8th expac, but the default 16383 is only 12th expac. from there it goes 32767, 65535, 131071, 262154, 524287. I searched all over and nothign had a list just one number or another. 255 was in one place associated with "all available" and another with just GoD. So i ended up searching for 16383 itself on google and eventually found that it and the other numbers mentioned in regards to expansions were all 1 lower than hexadecimal powers of 2. The lower numbers should look familiar 16, 32, 64, 128 etc.

NOw, these numbers dont coincide with expansion numbers, or 0 would be first not base game, 255 would be 8th not 7th etc..then it gets trickier when 16383 is neither the 14th nor the 13th expac, but the 12th (at least from the documentation i found) so after testing 524287 and finding it did not enable xtarget nor flag for UF, I took it up a few more notched to what I believe is the max the game can even process: 2097147. After 2097148 numbers start going negative (discovered in bazaar after recent years' inflation in particular) so, that's what I'm going to go with and cross my fingers.

I know on Live they can take certain features and give them to everyone, i.e. change teh expansion that feature counts as, but I haven't been able to find anything like that for extended target in eqemu yet. I also havent tried zoning to UF+ with a non-GM account yet to see if that's an issue or just the extended target. This expansions owned flag is a pita though, and only so far restricted to the extended target window access (and regardless of expansion flags). We all had it when we made toons, so it wasn't the client game folder. We all play from different computers, so it's not a corruption in a file in the game folder or we wouldn't all be affected. I didn't change anything that was remotely near anything that SHOULD affect this in SQL, all I've done since before this began was create recipes and NPC-specific .pl files.

To test this out I just now ported a non-GM account with me to brell's rest, no problem, so the expansion is fully available. That leaves the question stil labout what happened to the extended target windows. They should be usable in eqemu, there's a # command to set how many targets someone can have on it even, and that goes through without issue. What could this be?

Double check Character:EnableXTargetting in rule values table, make sure it is set to true.

it is set to true...

might World:UseClientBasedExpansionSettings have anythign ot do with it? it's set to false, though i haven't touched it, that's how it came by default

Also, I just found yet another expansions setting, this time in rule values, and I changed it to match the variables change I made earlier. restarting server to test again. haven't touched the useclientbasedexpac setting yet as i'm not entirely sure what that does.

If you changed your expansion settings to an expansion "before" xtarget was around, that would of disabled it.

ok so that seems to have broken the game (setting rule_value world::expansion whatever to 2097147) I couldnt enter game form charsel after several attempts and 2 server restarts, so I went down a notch to 1048575 and restarted, entered world no problem.


AND: It fixed teh extended target issue as well. Idk if peq.variables.expansions affected anythign whatsoever, but peq.rule_values.world::expansions whtaever did.

Now to figure out what expansion the server thinks that is, VoA or RoF.

World:ExpansionSettings 16383 to enable ALL expansions

No, I hadn't. I'd changed it after the xtarget issue started, and changed it from 16383 (supposedly TSS) to 524287 first (what I believed to be UF, but may be SoD) and then to 2097147...don't use that number, though it doesnt seem to affect a single thing when changed under peq.variables.

What I found in rule_values, was that it was also set there to TSS (16383) and I hadn't touched that even remotely, though changing it here now has fixed things. 1048575=good. 2097147=bad mmkay (I thought 2097148 was the game-breaking threshhold, but apparently its 2097147 or a little less)

That's what an old post said about 255, back when y'all only supported the Titanium client, but it doesn't.

Ok, I need a waitress, a stiff drink and a pillow :)

https://image.ibb.co/iOHoEx/tenor.gif

Set it to '0' and it will match the server-select message about no expansions :)

lol, just not a stiff waitress huh. Idk which 16383 is for sure, TSS, TBS, or even SoF, but it doesnt = ALL. Using a higher number worked (though NOW i find a post about the issue saying to use the client expac setting on true) In hex, going by powers of 2, 16383 is only 14, well 1 below it like 255 was 1 below 8 previously, and since RoF was the 19th expac, it is impossible for 255 to have meant ALL, and 16383 to mean all (except if all=SoF or before) 524287 as a bare minimum must=all currently being that that denotes a power of 19, but if the number needed is the expac+1 due to the base game, then 1048575 is required, and after my testing, works.

If for some reasons someone wanted to run a server starting in SoF and unlocking only 1 expac at a time as they went, these numbers would be needed to do so, but from my understanding, no one has even attempted such a thing here just used some QoL aspects of newer stuff, not the actual content.

That's also assuming the client being used is fully adaptive to each expansion rather than just turning on/off certain features.

It should be. If you downloaded the rof2 client off steam, then tried to login on an alt that didn't have the expacs, you could still get in using the client, but couldnt make use of anything exclusively rof2. I know something's flat out changed in the game, like the commonlands zones, but I wasn't around then to know if someone without the expacs they changed on could play from a client that was, though I'm sure once they removed the files it's a whole new ball game.

Tegila, I have both the UF and the RoF2 clients. My expansions settings are 16383.
I can access any and all zones (currently) in the database, which is up to 20, Rain Of Fear.
That access, I can do with the RoF2 client. Like a few minutes ago, I was in eviltree zone.
BUT, if I try that with a basic UF client, it won't happen on my server, not even with GM toon.