Manually apply the patch to the core? … I’ve done that for the past 5 or 6 times and it’s worked out for me /emoticons/default_tongue.png
Cba to apply it manually, way to damn big…
I have following Problem:
-
Set banduration to 5 Minutes
-
Go ingame and use hack
-
Get Banned for 5 Minutes
-
Close all hack programs
-
Login after 5 Minutes
-
Get banned after 2 minutes
But i have no hacks running and got banned one time.
Is this usually?
My Config:
# WARDEN SETTINGS
#
# Warden.Enabled
# Description: Enable Warden anticheat system.
# Default: 0 - (Disabled)
# 1 - (Enabled)
Warden.Enabled = 1
#
# Warden.NumMemChecks
# Description: Number of Warden memory checks that are sent to the client each cycle.
# Default: 3 - (Enabled)
# 0 - (Disabled)
Warden.NumMemChecks = 6
#
# Warden.NumOtherChecks
# Description: Number of Warden checks other than memory checks that are added to request
# each checking cycle.
# Default: 7 - (Enabled)
# 0 - (Disabled)
Warden.NumOtherChecks = 14
#
# Warden.DebugLogFile
# Description: Debug log file for Warden, ClientCheckFailAction will be sent to regular
# server log.
# Default: "" - (Disabled)
# "Warden.log" - (Enabled)
#
Warden.DebugLogFile = "wardenn.log"
#
# Warden.ClientResponseDelay
# Description: Time (in seconds) before client is getting disconnecting for not responding.
# Default: 600 - (10 Minutes)
# 0 - (Disabled, client won't be kicked)
Warden.ClientResponseDelay = 600
#
# Warden.ClientCheckHoldOff
# Description: Time (in seconds) to wait before sending the next check request to the client.
# A low number increases traffic and load on client and server side.
# Default: 10 - (30 Seconds)
# 0 - (Send check as soon as possible)
Warden.ClientCheckHoldOff = 50
#
# Warden.ClientCheckFailAction
# Description:
# Default: 0 - (Disabled, Logging only)
# 1 - (Kick)
# 2 - (Ban)
Warden.ClientCheckFailAction = 2
#
# Warden.BanDuration
# Description: Time (in seconds) an account will be banned if ClientCheckFailAction is set
# to ban.
# Default: 86400 - (24 hours)
# 0 - (Permanent ban)
Warden.BanDuration = 300
You can close all you want, if you inject your wow.exe then it stays injected even if you have the hacks turned off.
So to avoid this.
close hacks and wow.exe then fire up wow.exe again.
Okay, thank you.
Warden anticheat patch from TOM_RUS and leak for TrinityCore
To apply use git:
-to check if it runs without errors:
git apply --check warden_anticheat_leak_tom-rus_for_tc_c62a82c674.diff-to apply it:
git apply --whitespace=fix warden_anticheat_leak_tom-rus_for_tc_c62a82c674.diff[/code]xyz hack - working cheat, that does not catch Warden
Need help in creating a signature for him.
if i knew how to catch a signature, then i would gladly help, so sognfinder, how to get that data then?
XYZ and the THHH both use dynamic memory writing ($playerbase + offsets) and are currently uncatchable. We’ll need a piece of code in order for it to work. This has already been discussed on page 9.
Warden cannot scan addresses that can be changed by the legit wow functions
If that is so, then how does blizzard do it on retail? xyz hacks and the likes are instantly detected there afaik.
They do not only rely on warden, they have server-side checks too, because its just stupid to be in x=8 at one moment, and then in x=900 at the other with normal speed, thats what they check for
basicly AC1 and warden together to get a better overal protection asfar as it goes offcourse…
Yeah that’s weird. Maybe it need some response to the opcode. or something.
trust me i run wow on a macbook pro and have warden now for months more then half a year… even before this thread was announced, and never ever had a crash due macosx cliets.
its disabled… and thats what it does…nothing…
i have had crashes of warden itself ( the core > wardenwin.cpp ) but we found nothing special in that core that should cause the crash.
and even then the crash is rare, once in 2 weeks or so or maybe less.
Yeah, because it happens only with older PPC macs. I have made an OS attribute in worldsession, and tried to bypass any opcode handling if the OS is not Win.
maybe because the code only checks for osx and not mach?
Never bothered to check out the Warden patch in its current state, and I have to say it looks great. Good job guys. /emoticons/default_smile.png