iforgotmypassword
-
Posts
56 -
Joined
-
Last visited
Never -
Donations
0.00 GBP
Content Type
Profiles
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Posts posted by iforgotmypassword
-
-
same for me
-
infinite loop in WardenMgr::Update
-
1st replace "session->m_WardenTimer.Reset();" line 158 by "session->m_WardenTimer.SetCurrent(0);"
didn't help, I will try to increase timer
did not help too
-
1st replace "session->m_WardenTimer.Reset();" line 158 by "session->m_WardenTimer.SetCurrent(0);"
didn't help, I will try to increase timer
-
Can you please check if the client did stop to reply to cheat-check? I let the client 2 minutes, which is long enough I think.
I recommend you try the new data, less duplicate page checks and new pages/lua checks.
same in new version
how to check client cheat-checks reply?
-
2011-04-06 19:44:46 Warden Manager: no Cheat-check reply received, kicking account 1568
it happens very often for different accounts, when player tries to log out to character select screen
-
I am not sure about another check, 0x987255.
Maybe it is wrong check too, maybe not =\\
-
same for some players on my test server. Seems like this check is broken
-
nope, client can load modified Spell.dbc and there is many guides how to modify some stuff like global cooldowns, etc
-
feature request
we need a locale-based MPQ checks
for example, Spell.dbc file is different for different locales, but client-side modification of this file can provide some extra stuff
-
-
Also I didn't get any cheat detection with 1 hour uptime on Linux
-
the warden daemon is working, the connection is established with the mangosd server, but the connection is lost each 10-20 seconds (and reconects instantly).
have same issue with connection between windows and linux. Firewall is disabled
-
solved by adding m_WardenClientChecks(NULL) to worldsession constructor
-
core crash in WardenMgr: SendCheatCheck at checkList->clear();
locals:
+ this 0x0000000043f57018 {m_WardenProcessStream=0x00000000323f72b0 m_WardenProcessConnection=0xcdcdcdcdcdcdcdcd m_Enabled=true ...} WardenMgr * const + session 0x00000000025acbc0 {m_muteTime=1279703127 m_timeOutTime=895093 m_nameQueryCallbacks={...} ...} WorldSession * const + data {m_opcode=52428 } WorldPacket + md5 "841EF47866310AE3D26A3D8546A4CD0D" std::basic_string<char,std::char_traits<char>,std::allocator<char> > - checkList 0xcdcdcdcdcdcdcdcd [...]() std::vector<WardenMgr::GenericCheck,std::allocator<WardenMgr::GenericCheck> > * [size] CXX0030: Error: expression cannot be evaluated [capacity] CXX0030: Error: expression cannot be evaluated nbChecks 204 'М' unsigned char m_seed1 204 'М' unsigned char m_strIndex 204 'М' unsigned char
-
WardenSocket::_HandleLoadModule, received 4096
Got 4096 bytes of data, 18160 bytes needed, waiting for next tick
Command handler failed for cmd 3 recv length 4096
Terminating connection from '127.0.0.1'
-
same issue with last version
-
no, I mean that entries in database must have different chances to execute
-
Neo2003, we need an ability to setup chances for each check defined in database
because with current count of memory checks warden needs about 30 minutes to detect weh (weh is mostly used cheating tool)
currently we have a curious situation: the more we have checks, the less we get chances to detect cheats.
-
okay, got it:
Crash at:
uint8 m_seed1 = mWardenClientSeed[accountId];
--> DEBUG_LOG("Seed byte: 0x%02X, end byte: 0x%02X", m_seed1, mWardenModuleChecks[md5][WARD_CHECK_END]);
to reproduce:
- start wardend
- start mangosd
- enter world
- shutdown mangosd
- start mangosd
-
had a crash:
can't start wardend if in debug build, sorry
this happens when mangos lost connection to wardend, but client still connected
-
is it possible to allow worldserver restore connection if connection to wardend was interrupted?
-
WEH working like without warden
-
Below something that's hopefully solve (atleast some, if not all) issues with offmesh connections.
Please do test.
seems like no more crashes, thank you!
Warden - The definitive anti-cheat system
in OldCore modifications
Posted
it always happens on my live server (*nix)