AlexSot
-
Posts
9 -
Joined
-
Last visited
Never -
Donations
0.00 GBP
Content Type
Profiles
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Posts posted by AlexSot
-
-
checks are not problem.... the problem is 132 error.....
Have you modified 0x03 warden packet for 2.4.3? It's required step...
No, I do not know how to do it ... that is why I ask for help
-
checks are not problem.... the problem is 132 error.....
-
some new info... packets to client are also wrong.... fatal error occurs
-
I just realized.... checks fails cause there are wrong data in database.... need check result's for 2.4.3 client....
-
and some new fails
Kicking account 1317916 for failed page check Offset 0x0000959C, length 21
Kicking account 1317916 for failed page check Offset 0x0000A078, length 24
Kicking account 1317916 for failed driver check 'ndis_x86'
-
Just tested it again...
clean client after entering world
Kicking account 1317916 for failed check, MEM Offset 0x70F357 length 7 has content 'CE0F839E000000' instead of 'F08B82D0000000'
Is it possible to change this values somewhere ?
-
there are diffs in packet format to wow client... cause my players got disconnected when try only to log into the world with warden turned on
sorry for my english
-
Hey guys.. what about packet format for 2.4.3 client?
Improved Hunter's Mark
in OldGeneral discussion
Posted
Any ideas how to fix this talent?
I tried to place some modifications in Unit::HandleOverrideClassScriptAuraProc... but it's take no effect cause this function does't called.