Fixed Spell Specialization Skills Reset to 49 Upon Zoning

65 druid on Mischief. resets only when you get 2 specs above their 140 cap. Noticed all had a 240 level cap until 1 spec was raised above 140. then they all had a 190 cap until the secondary was raised above 140.
All went back to 49 / 240 when zoned

The cap changing like that is normal. It would also do that before the patch where until you picked a specialization they all appeared to be able to be maxed to the primary cap, then secondary cap, etc.

It is a little confusing at first now, though, having to hit Primary minus 100 to get it to register the Secondary instead of just having your next skill over 50 becoming the Secondary.

[deleted]

Happening at level 65 on Agnarr. Reduced my spec skills and they started skilling up again.

This is not just an in game “zoning” bug. There is some sort of back ground check occurring to verify your not duping the system with higher specialization skills. As an example:

You can max all skills. DO NOT ZONE. Log completely out and back in (restart patcher). Upon character loading in (post save from logging out) you are presented with the following message:

“YOUR SPECIALIZE SKILLS WHICH WERE TOO HIGH HAVE BEEN REDUCED”

This is not just a zoning bug. It’s some sort of fidelity check the game is doing. So even with a character save and completely logging out (without zoning), this will occur. All specialization reset to 49.

Vacheron

Lvl 70 Enchanter, Lvl 70 Cleric, Level 70 Mage , Aradune - Zoning resets Specs, but is random. Dosent happen every time I zone.

BECAUSE THIS IS NOT A ZONING BUG. Don’t send the coders on a wild goose chase!

There is a hard code system check to prevent people from exploiting the system. Someone in developing and coding forgot to check the back end rules to prevent exploiting the spec system. The reason it’s random on zoning is because it has nothing to do with zoning. It’s a server save check.

This is 100% repeatable on camping out fully and logging back in.

Stop with the zoning bug junk. STOP IT

Also 100% repeatable when you zone and have any other spec. that is not your primary spec. above what the old caps were. Also you "zone" when you log out and back in soo...uhh...yeah.

Uhh, you do realize that logging out and back in makes you "zone" into the world, which triggers the same effects as zoning into another zone when already ingame, right? It is most definitely related to zoning.

Also, a character save is triggered when you zone, among other things. Stop talking like you work on EQ when it's clear even the most basic concepts elude you.

On Aradune, all 3 accounts, lvl 70 mage, lvl 70 cleric and lvl 66 Enchanter

Logging completely out and back in is most definitely NOT the same as zoning. You people have no clue…

If it were the same then having an achievement key check the achievement box but still not allow you to be key flagged would be fixed by zoning, right? WRONG, this doesn’t work. Need an example IE: Dread spire keep key. The key won’t recognize even though the achievement updates. Zoning does NOT fix this. The only thing that does is completely logging out to desk top, rerunning the patcher, and starting EQ fresh. Even logging out to character select and reloading (ZONING UHHH DERP) doesn’t work.

So NO reloading EQ completely is NOT the same as zoning. However, sometimes a character save happens while zoning which is why there is no consistency in people reporting as a zoning bug. It is not a zoning bug. It’s when the character is doing a hard save check which is repeatable 100% upon reloading the patcher and doing a full log in cycle.

There is a backend hard code that was not removed (forgotten) on the server side to prevent exploiting of the system.

And this is where I stopped reading. Running the patcher has nothing to do with anything in game. The patcher pulls the client files and downloads updates if it sees changes. You can login using "patchme" and not run the patcher at all to enter the game. Patch servers are different from login servers, which are different from world and zone servers.

Stop derailing the thread and let the devs look at the people that are replying with their levels, char names, servers, and let them determine what the issue is.

Rerunning the patcher leads to a fresh entry log in with the server select. Joining the server select fresh and loading the character refreshes all saves. This is one of the top reasons, when faced with log in and character issues, that the customer service, dev department, and associated game help, recommended NOT skipping the patcher before logging in and completing the full log in process naturally. Sure you can skip the patcher but the example was meant to illustrate the need to follow the proper process in order to find the actual source.

The whole “I stopped reading” comment you made is exactly why you’re ill informed and won’t help. You are derailing the topic by pointing the devs in the wrong direction with your less than novice understanding of the game loading procedure. The devs have quite literally recommended this process since 1999 in addressing the source finding and correction of all issues 100%. They always recommended NOT skipping the patcher.

This also leads to information that would help the devs source whether or not they can apply this fix on the back end rather than taking servers down… but you probably wouldn’t know that while your jamming the taunt button on TLP because someone told you that’s how it worked in 2003…

OK, I will give you that there are probably additional checks made when you log out completely vs just zoning, be that as it may it has no relevance to this issue. This bug is happening due to a check that is made while zoning and is 100% repeatable when zoning. Your comments to this discussion add nothing to help resolve the issue.

Incorrect, the additional checks are made every time you completely follow the relogging process. This is NOT 100% repeatable by zoning. Zoning does not always complete the full checks. It is not a zoning issue in this case. That is why, when people are reporting the bug while zoning, that the resulting effects/reports are inconsistent.

IE: while zoning sometimes people experiencing no skill reset, or partial skill reset, or full skill reset.

Telling the devs it’s a zoning bug is what is NOT helping. It is fully repeatable by doing a complete relog. Period.

ROFL... I tested it 3x it happened exactly the same each time, I can reproduce it 100% while just zoning.

It’s not happening that way for everyone. And nobody was getting the failure message, while zoning, that was given while relogging… which btw, will help the devs do CTRL -F in their code and find the source…

You know… the helpful game message I posted that can allow them to reverse look up where the error is coming from.

Yeah it's not "happening" the same way for everyone because everyone is not "testing" it. If you skill up 1 spec. to the point it locks it as your primary, then skill up a second one to above what your cap used to be before this patch then zone it will reset your specs to 49. 100% of the time.

ftfy.

They know where to look without having you tell them where to go. This isn't something that's been around for 25 years. It was just implemented with today's patch.

Heh. Are you sure they know where to look? The check was probably implemented 20 years ago and they forgot / didn't know about it until today...