Do you have use client settings true or false though? And if it's false, why did increasing my expansion setting from 16383 then enable the target?

Rof was 19 fyi, idk what emu considers rof2 though, I know cotf was 20 officially as it was the last one I bought on live.

First of all, that World:UseClientBasedExpansionSettings if you set that to false, clients will
use the expansion setting that you set on the server. (Rules, variables) but if you set that
to true, the client will use it's own limits. (I have mine set to false).
Here's an example. If you enabled expansions up to PoP and left that clientbased setting to
false, the client would see AA's available only up to PoP.

But as far as expansions, if you look in the "zone" table, the column marked "expansion", you
will see what expansion numbers are listed for each zone. I would encourage you not to
expect too much exact comparison to "Live" with the coding on the EQEmu.

RoF2 is still the Rain of Fear expansion.

We denote that in the server code as a separate and unique client build from RoF, just as we do with all other clients.


Each client has it's own set of opcodes and packet data formats that may or may not be compatible with other client builds.

This is why we have ClientVersion::{Unknown, Client62, Titanium, SoF, SoD, UF, RoF, RoF2}

I get all that, I'm just trying to figure why leaving it at 16383 (with client expac=false) disallowed us from using xtarget, and increasing it allowed us to, if 16383 truly means ALL expacs allowed.

Grumpy, you said yours is false so it should follow same rules as mine, but they're reacting differently to the numbers. If yours was true, itd make perfect sense.

Still don't know why we had them to start with, then lost them without changing any of the above settings in any table, but it's fixed now. Also, we could travel to UF before increasing past 16383, but xtarget was unusable and said UF missing. It all makes sense in theory that 16383=all bc it allows entry to zones, but in practice it thinks at 16383 one does not have UF to enable xtarget.

This is interesting. I had xtarget window, but as usual, I close it when I first get going, because I
don't use the window. (I'm still out looking for a corpse I lost in 2004)
I just tried bringing it up, but no, it's telling I need to purchase UF exp, haha BUT, I haven't changed
any exp setting since I installed the server. Haven't touched rules table at all, so in theory, if the
16383 setting would not allow xtarget, I wouldn't of had it in the first place to close it off.
I did some reading, some people wrote about issues with their RoF client UI (on live) and losing their
xtarget window after a patch, etc. I'll do some testing tomorrow.

yeah I thought it was weird, we were all fine (4 accts 4 pc's) until last night everyoen started losing it.

it might fix by making clientexpacsettings true, but to leave that false, it worked just fine for me increasing the rule as mentioned above. when i did it too far i couldnt get past charsel, backed it up to the 1048xxx notch, and both got in game and got xtarget back. idk what's going on but none of us are doing patches or we couldnt get in the game. And in my house, I'm the only one that's ever played on live so it wouldnt change the other clients' files if i did.