Close
Page 2 of 2 FirstFirst 1 2
Showing results 11 to 16 of 16
  1. #11

    Default

    Quote Originally Posted by Apatheist View Post
    Warden process detection is designed to detect cheats. Both ISBoxer and AHK are legitimate software that many people use for many reasons. I can't imagine Blizzard banning people simply for having those processes running in the background of a single client.
    The jury is out on this.

    There are multiple people in the ISboxer discord who have stated that after the ToS change they have only used WoW under InnerSpace/ISboxer without multiplexing/broadcasting (like just logging in alts to burn passive crafting cool-downs) yet have received warnings... There are others who have run WoW under InnerSpace just like normal (with broadcasting/multiplexing) and not received warnings (yet). There are others who are being very explicit with their testing of using InnerSpace with no multiplexing/broadcasting and no users around and so far have had no warnings...

    I agree they shouldn't but Blizzard is lazy and it is far simpler to just warn/ban based on process scanning and the presence of the programs. More testing will give us more data points to get stronger correlation but Blizz can purposefully be selective in the warnings or the timings of their warning to try to hamper any analysis...

    All that being said Bizz can change their methodology and/or enforcement at anytime without warning so I would act accordingly.

  2. #12

    Default

    Quote Originally Posted by nodoze View Post
    it is far simpler to just warn/ban based on process scanning and the presence of the programs.
    Possibly, but even if that's the case the ban won't stick, right? Since the actionable offense is key broadcasting and if there's no evidence of key broadcasting then no rules have been broken.

  3. #13

    Default

    Quote Originally Posted by Apatheist View Post
    Possibly, but even if that's the case the ban won't stick, right? Since the actionable offense is key broadcasting and if there's no evidence of key broadcasting then no rules have been broken.
    That is assuming they have an easy enough way to analyze the interactions across all your clients in a manner that is definitive AND are going to take the time to review and "clear you".

    Blizzard can be inept, inconsistent, & lazy so I would not bet on it nor risk anything you don't mind losing.

    If I continue any 5boxing, until we learn more, I will likely be not doing any broadcasting nor multiplexing (neither hardware nor software) nor have any software like ISboxer installed & active anywhere and will likely be separating my activity as follows:

    • - Main WoW Account with my Collector's Editions on Primary PC on my regular network going out through my primary ISP connection; I will not log my main account on with any overlap with any boxing accounts and will avoid sending gold or items for awhile (consoldating now so won't need any for awhile).
    • - Separate 5box WoW accounts on my 2nd PC / Kid PCs going out over my Guest network over my backup ISP connection (my kid's friends always want to get on our wifi or on ethernet when here so I have a Guest network already). I may just start a new 4hunter+healer team on a new server for testing purposes for now and to add further sepration... I am also glad that all of my accounts are already on separate battlenets already.

    I already have 6 accounts active (actually 7 but I was thinking of stopping 1) so no extra cost/pain there. My characters are not setup exactly the way I would want as my main has been used in/with multiple teams so that kinda points me to a new team if I want to totally separate for now and go down to 6 accounts.

    Currently my 2 ISPs are in more of a A+B fail-over configuration and/or a load-balancing configuration for both my networks in my Security Gateway... I will just need to configure the Guest network to always go out through the "B" ISP connection and and may add a persistent VPN tunnel to another geographical location for the B connection just to add another layer of separation. I already have a VPN subscription but currently just turn it on when I want/need to so I just need to set it up to be persistent upon restart.
    Last edited by nodoze : 11-06-2020 at 06:12 PM

  4. #14

    Default

    Warden is loaded on login.
    Once a minute (ish) the game server pings Warden to quickly scan inside the executable memory to make sure things haven't been altered.
    Early bots would always unlock the LUA in order to run blocked functions. So Warden now naturally scans to make sure some idiot isn't just overwriting the bytes for the lock. Nahmeen.


    You can grab whatever debugging tool you want and poke around. Make sure you use a VM, not your own account yadda yadda. You tweak anything protected (Warden) by mistake and BOOM. Insta ban.

    To repeat; Warden gives 0 fucks about anything outside the memory space WoW takes up. It doesn't scan and report your taskbar, window titles, porn habits e t c.

  5. #15

    Default

    Quote Originally Posted by Apatheist View Post
    Blizzard doesn't detect the software you're using (outside of known cheat processes.) They look at the behavior of your characters.

    If you have multiple characters on follow, performing actions in a way that could potentially be key the result of any type of key broadcasting you're likely going to be banned.

    Just using AHK/HKN for whatever reason on a single character won't be an issue (assuming whatever you're using them for wasn't an issue prior to the rule change.)
    I used AHK for years on a single toon, one day i switched the version to the latest and banned in 24 hours, same for my son.
    I had a complex rotation function in my script with also key repetition
    This was 6 months ago

    Probably at some point the started checking how the keypresses are coming to the WOW client
    Last edited by spacer2 : 11-07-2020 at 05:35 PM

  6. #16

    Default

    Quote Originally Posted by nodoze View Post
    The jury is out on this.

    There are multiple people in the ISboxer discord who have stated that after the ToS change they have only used WoW under InnerSpace/ISboxer without multiplexing/broadcasting (like just logging in alts to burn passive crafting cool-downs) yet have received warnings... There are others who have run WoW under InnerSpace just like normal (with broadcasting/multiplexing) and not received warnings (yet). There are others who are being very explicit with their testing of using InnerSpace with no multiplexing/broadcasting and no users around and so far have had no warnings...

    I agree they shouldn't but Blizzard is lazy and it is far simpler to just warn/ban based on process scanning and the presence of the programs. More testing will give us more data points to get stronger correlation but Blizz can purposefully be selective in the warnings or the timings of their warning to try to hamper any analysis...

    All that being said Bizz can change their methodology and/or enforcement at anytime without warning so I would act accordingly.

    I used Isboxer till this morning for my boost and stratholme rep farm (on classic - with broadcast on). I have not a single warning yet.
    What I think is, those who recieved a warning are maybe those who were reported by players... it is the same scheme as bots. They can't prove broadcast and I think they can't even legally strike an exe like Isboxer. So why would you have more multiboxers banned than bots ? => because of players reports.


    Don't you remember when they did their bots ban wave ? it was the same thing, players were active on reports because everyone was talking about that (like this week with assmongold).
    [x5] Classic Team - Horde
    [Mage x4] [Priest] :
    Main 60
    [War][Mage x3]
    [Priest] : Mixed 60
    [5x Sham lv 20]





Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •