I havnt heard of anyone using maphack getting banned.
Only botters
I havnt heard of anyone using maphack getting banned.
Only botters
I'm very puzzled by the criteria for banning. I was using the map hack and sometimes scumming areas based on various preload alerts all the way up to the news breaking on the anti-cheat code. I stopped using the active hacks, but kept using the read-only features of PoeHUD from i2um1's branch. I was just starting to look into disguising/hiding the PoeHUD process when HvC decided to make it easy for me.It seems that I ought to have been flagged and possibly banned for past actions, but I haven't noticed anything at all.
HvC, do you know if your banned friends were supporters? Maybe they only ban supporters for botting (and bot-like activities) and not for map hacking. It's really the only factor besides luck that I can think of would make a difference - and given how detectable PoeHUD was up until your contribution, I don't much believe in luck, hehe.
All my banned friends that have maphacked have done it after the update, some are supporters, some aren't. I have non-banned friends that have maphacked after the update, of those all were supporters, they might have a less tight ban policy towards supporters but i've seen them ban a master supporter.
Tbh it comes down to them being lucky I think.
Last edited by HvC; 01-19-2015 at 04:26 PM.
got a new frozen again.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at PoeHUD.Hud.Health.HealthBarPlugin.Draw()
at PoeHUD.Hud.Plugin`1.Render()
at PoeHUD.Hud.ExternalOverlay.<OnRender>b__15(IPlugin x)
at System.Collections.Generic.List`1.ForEach(Action`1 action)
at PoeHUD.Hud.ExternalOverlay.OnRender()
at PoeHUD.Framework.Helpers.ActionHelper.SafeInvoke(Action action)
at PoeHUD.Hud.UI.Graphics.RenderLoop()
at PoeHUD.Hud.ExternalOverlay.<OnLoad>b__e()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotificat ion(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at PoeHUD.Hud.ExternalOverlay.<OnLoad>d__f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(Object state)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
prototype
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Danny/Downloads/prototype.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
SharpDX
Assembly Version: 2.6.3.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Danny/Downloads/prototype.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Newtonsoft.Json
Assembly Version: 6.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Danny/Downloads/prototype.exe
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
SharpDX.Direct3D9
Assembly Version: 2.6.3.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Danny/Downloads/prototype.exe
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I haven't been banned yet and haven't really been playing for a few day, safe to think I'm ok for now?
I would think that you're most likely safe for now. I'm in the same boat as you, though, hehe.
I would expect that their procedure goes something like:
1. Automatic detection of "illegal" behaviour (botting, RMT'ing, map hacking, etc.). Previously just through analysis of behaviour, but now also featuring the anti-cheat detection.
2. Possibly automatic banning depending on what was detected.
3. If user complains about automatic ban or if the account was only flagged for something serious: Manual investigation by an admin who has final say.
If there is a manual investigation before banning then the ban could be somewhat delayed. I suspect that they auto-ban a lot, though, and then launch investigations only when people complain. That would seem like a lot less work - at least if the detection has few false positives. I would expect that most botters know the risk and accept their fate when caught in the ban trap.
I've also seen forum posters stating how they got off with a warning after an initial ban. This would support the above assumption.
I do also imagine that they have a bunch of different flags that are placed on accounts depending on what the automatic analysis (and now anti-cheat detection) tells them. Most of them are probably just informational for use in later investigations. Some of them might have an impact on game play, e.g. the no currency drop flag.
Latest patch 1.3.0k I got a message when I logged in that I had been detected using maphack/hacks, and any continuation will end of with my account being banned. I'm sure this is because my account was flagged for using the full maphack.zoomhack, fullbright version after the patch. I have been using the alert only version but I am afraid to use it now on my account as I have been playing since closed beta have multiple supporter packs, and my account is worth thousands of dollars in gear..
So until I can hear they can not detect at all the alert version I will not be using it. Sucks because it is a real QOL!!!
Aw shit.
DIS SHIT JUST GOT REAL!!
or its a bluff...