Close
Page 2 of 4 FirstFirst 1 2 3 4 LastLast
Showing results 11 to 20 of 32

Hybrid View

  1. #1

    Default

    Wow that sucks , sorry to hear this .... I myself don't pvp it just draws way to much attention from the peeps around you.I just stick to pve and most people who see me say nice set-for multi boxing or something along that lines.

  2. #2

    Default

    Interrupt bots are the work of the devil or some really lazy person.

    Not sure if that was one of them but it honestly wouldn't surprise me from the crowd.

  3. #3

    Default

    Technically the "one button pressing multiple buttons in a long line of buttons" that some people use via ISboxer can be equated to what the bot did (pending you set it up to do that). The only thing that ISBoxer does not do that things like the bot did is allow for if-then statements which were removed from the API (think of feral druid's WTF JOHN MADDEN style going in one macro again much like it could be made in early WOTLK when cast random existed) or any memory reading for auto-interrupts.

    I'm not talking about things like having it mash 4 buttons at once in a "priority" rotation via more buttons set to one ability than others (like most enhance shaman/dk teams use)... I'm talking about things like

    Step 1: press 1 + 2
    Step 2: press f2 + 2 - Do not continue for 5 seconds
    Step 3: press 3 + 2 - Do not continue for 2 seconds
    Step 4: ... etc

    That some might use for setting up "automation" of their DPS rotations... even if not optimized.

    As long as we are using one button = 1 action then we should be more than fine. Or sticking to workarounds to DPS like is posted on lazy macro websites and how we originally maintained DPS rotations.

    Be it a false positive... or technology that picks up what ISBoxer actually allows people to accomplish with its functionality (though not exactly the same as the rotation bot). Still sucks that people are getting banned and i feel that if you did get caught up in a false positive banwave that you'll get back rolling in no time.

    But I wouldn't be surprised if the "step" functionality of ISBoxer is the problem and that possibly anything more than 1 = 1 on all clients is going to be the extent of multi-boxing once more.
    Last edited by MiRai : 01-24-2014 at 02:43 AM Reason: Removed Names Of Bots
    The Internet: We Know Drama
    If you're gona screw with my sig at least leave the thing bolded :P

  4. #4

    Default

    As a reminder since I've now removed bot names from this thread twice -

    Discussion of bots is not allowed on this site. This includes the naming of bots. We have a hard enough time distancing multiboxing from botting, we don't need searches for bots directing people here, even if its a post against botting. We are not free advertising for programs that violate game rules.
    Blog : Herding Khats
    Team : Kina - Çroaker - Messkit - Lìfetaker - Wìdowmaker
    Newbie Guides : Multiboxing Vol. 1 - Multiboxing Vol. 2 - HotKeyNet - Jamba
    The Almighty Lax made a liar out of me, apparently I DO get prizes for it.
    *Commences Wielding the Banhammer like there's piñatas up in here and I'm Lady Thor*

    _ Forum search letting you down? Use the custom Google search _

  5. #5
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6815

    Default

    First, (to everyone) I just don't understand how hard it is to not mention specific bots by name. People are posting names of bots like it's pertinent information when it isn't. It's always been a rule on this site to keep the names of bots off of this forum and that rule hasn't changed. It's honestly becoming tiresome continuously having to edit out the names of bots in other peoples' posts and I'm just going to start completely deleting entire posts because people can't follow the rules.

    EDIT: Apparently Khatovar was reading my mind. o.O


    Second, (to Shodokan) the bots in question that were mostly targeted in this banwave read the game's memory and unlock Lua code that Blizzard has specifically and purposely protected -- All of which ISBoxer has absolutely nothing to do with, so you can stop your comparison right there. Programs like HotKeyNet and AutoHotKey have much more "functionality" in this department than ISBoxer ever has, but both of those programs are viewed as legitimate multiboxing programs on this forum.

  6. #6

    Default

    Quote Originally Posted by MiRai View Post
    First, (to everyone) I just don't understand how hard it is to not mention specific bots by name. People are posting names of bots like it's pertinent information when it isn't. It's always been a rule on this site to keep the names of bots off of this forum and that rule hasn't changed. It's honestly becoming tiresome continuously having to edit out the names of bots in other peoples' posts and I'm just going to start completely deleting entire posts because people can't follow the rules.

    EDIT: Apparently Khatovar was reading my mind. o.O


    Second, (to Shodokan) the bots in question that were mostly targeted in this banwave read the game's memory and unlock Lua code that Blizzard has specifically and purposely protected -- All of which ISBoxer has absolutely nothing to do with, so you can stop your comparison right there. Programs like HotKeyNet and AutoHotKey have much more "functionality" in this department than ISBoxer ever has, but both of those programs are viewed as legitimate multiboxing programs on this forum.
    Actually it did not unlock LUA code after the second iteration to my knowledge, there was an original banwave for it in 2010 which did that after which it moved to memory reading and external if/then statement coding.

    I don't use AHK or HKN so I only draw comparisons to how i have seen people set things up and how people have helped others set things up.

    SOMETHING is setting off a false positive, because these bans were NOT done by gms watching accounts/players they were automated bans. My bet with ebony's case is that a GM was making sure that one didn't fall through the cracks that showed similarities to functionality it provided after she was possibly reported. (I've also been contacted by gms in the past two days while leveling new dks and know i've been reported multiple times in the past week while leveling characters up.). Hell I didn't even know there was a banwave for those bots until i read that people got banned for boxing apparently here.

    I love ISBoxer and what it has allowed me to do but I'm not going to sit here and say that there is absolutely zero similarities between the bot's functionality and that of ISBoxer's (And AHK/HKN for that matter now that you mention it).

    ISBoxer is NOT a bot, we all know this... but is auto-reconfiguration of buttons pressed in an order via a single button(step 1: 1, step 2:2, step 3:3 all while pressing 1) really not the least bit of the grey area we all knew it was from the beginning? I mean we have had that discussion here before no?

    Just some food for thought and nothing more.

    Example of a macro
    /castsequence reset=0.5 0,0,0,0,0,Judgment
    /castsequence reset=0.5 0,0,0,0,Crusader Strike
    /castsequence reset=0.5 0,0,0,Exorcism
    /castsequence reset=0.5 0,0,Judgment
    /castsequence reset=0.5 0,Divine Storm
    /castsequence reset=target/15 Crusader Strike,Judgment,Inquisition,Exorcism,Templar's Verdict,Word of Glory,Crusader Strike,Judgment,Divine Storm,Exorcism,Templar's Verdict,Divine Storm
    /cast Avenging Wrath
    /cast Execution Sentence
    /cast Guardian of Ancient Kings
    /startattack
    Last edited by Shodokan : 01-24-2014 at 03:24 AM
    The Internet: We Know Drama
    If you're gona screw with my sig at least leave the thing bolded :P

  7. #7

    Default

    Quote Originally Posted by Shodokan View Post
    Actually it did not unlock LUA code after the second iteration to my knowledge, there was an original banwave for it in 2010 which did that after which it moved to memory reading and external if/then statement coding.

    I don't use AHK or HKN so I only draw comparisons to how i have seen people set things up and how people have helped others set things up.

    SOMETHING is setting off a false positive, because these bans were NOT done by gms watching accounts/players they were automated bans. My bet with ebony's case is that a GM was making sure that one didn't fall through the cracks that showed similarities to functionality it provided after she was possibly reported. (I've also been contacted by gms in the past two days while leveling new dks and know i've been reported multiple times in the past week while leveling characters up.). Hell I didn't even know there was a banwave for those bots until i read that people got banned for boxing apparently here.

    I love ISBoxer and what it has allowed me to do but I'm not going to sit here and say that there is absolutely zero similarities between the bot's functionality and that of ISBoxer's (And AHK/HKN for that matter now that you mention it).

    ISBoxer is NOT a bot, we all know this... but is auto-reconfiguration of buttons pressed in an order via a single button(step 1: 1, step 2:2, step 3:3 all while pressing 1) really not the least bit of the grey area we all knew it was from the beginning? I mean we have had that discussion here before no?

    Just some food for thought and nothing more.

    Example of a macro

    Nah, for the simple fact that regular players use such macros as a convenience to actually piano mashing their fingers into cripple status.

    WoW is overly complicated in the toolbox for every character and those macros save us from crippling ourselves. I see them as accessibility for if they didn't exist, I surely wouldn't be playing the game.

    When I do box, my characters use those kind of ingame macros. You can't put interrupts in them and expect to do very well. Interrupts fall outside of the rotation and as such, remain outside of those macros for maximum effectiveness.

    Even if you had say, a 5 box with an interrupt chain you would find that it'd rarely if ever be effective in combat with other players. For the simple fact that it isn't on demand but queued. I can't tell ya the number of times queuing things like spell interrupts has been a really bad idea. I've done it, wiped because of it. It works in rare occasions where the clock strikes 12 and doesn't work anywhere else.

    These guys are no doubt using some kind of memory reading bot to read when cast events are taking place. Think about it. It'd be very easy for Blizzard to detect who is calling protected functions outside of protected scope. Simple by recording stack calls for players at random when reports happen.

    As some others have said, I take it with a pinch of salt whenever someone says they weren't doing anything against the ToS or 'I was just multiboxing.' Sorry, I don't buy it. I do multibox on and off but more than enough to where if multiboxing was a bannable offense I'd be long gone.

  8. #8

    Default

    Quote Originally Posted by Shodokan View Post
    ISBoxer is NOT a bot, we all know this... but is auto-reconfiguration of buttons pressed in an order via a single button(step 1: 1, step 2:2, step 3:3 all while pressing 1) really not the least bit of the grey area we all knew it was from the beginning? I mean we have had that discussion here before no?
    Steps are no different than using Swapactionbar. I can throw all my spells/macros on slot one of every bar in game and tack /swapactionbar on and 1 is suddenly hitting a different macro every time.

    As far as the "do not advance for" thing, I'm not particularly for the ISBoxer version of it, but you can still duplicate a version of it using armor slots via the ingame macros or by using nulled castsequences with a reset conditional that you call in another macro further down your sequences such as -

    Macro 1

    Code:
    /castsequence reset=target Corruption, nil
    /swapactionbar 1 2
    Macro 2 {or 8 or whatever}

    Code:
    /target pet
    /targetlasttarget
    /cast Shadow Bolt
    /swapactionbar 1 2
    Easy-peesey.

    Having used these setups on solo toons that I didn't want to set up a HKN script for, the only difference is it's way easier and more elegant to do it externally, especially with multiple toons. All things considered, I don't find those actions grey at all since they are functionally identical to actions I can take with the ingame tools.

    People get caught up in banwaves and people get it cleared on appeal. Some people also assume that multiboxing is a get out of jail free card for breaking other rules, but they never want to admit that.

    You yourself claim that you've been contacted recently by GMs after you've been reported all week, so I'm far more of the mind that a ban wave was in the works and GMs trying to rush through confirming or clearing the who-knows-how-many reported and/or flagged as hacking/botting accounts {which we all know is what multiboxing gets reported as} and slack-assed the check so they could move on to the next ticket.

    It's not "people got banned for boxing" it's boxers getting caught up in a banwave. That doesn't instantly equate to us doing anything that is automatically flagged, it could just be manual reports and lazy or uninformed GMs, like it usually is.
    Blog : Herding Khats
    Team : Kina - Çroaker - Messkit - Lìfetaker - Wìdowmaker
    Newbie Guides : Multiboxing Vol. 1 - Multiboxing Vol. 2 - HotKeyNet - Jamba
    The Almighty Lax made a liar out of me, apparently I DO get prizes for it.
    *Commences Wielding the Banhammer like there's piñatas up in here and I'm Lady Thor*

    _ Forum search letting you down? Use the custom Google search _

  9. #9

    Default

    Well the players i saw that got banned was not using isboxer one was still on keyclone and one was on pwnB (2 was not using the same battlenet).

    I use steps all the time and i do press more then one key at the same time! and i been doing bg's. To be fair every time blizzard does big ban waves like this boxers all ways get mixxed up in them.

    As a few off the wow blackmarket used mutiboxing to get "round bans" opening tickets saying they was boxing and then botting ontop off it a few years ago kinda made it hard for blizzard to work out who was doing it not doing it.

    All i can say is don't yet them talk you out saying you was doing something wrong it be hard to get info out off them as they (software devs try to get a work round for them) but your looking a long Time, if it was a under 72 hour ban then it was a automated ban, still open the ticket/email so you can it cleaned off your file as a few automated bans can lead to a full ban next time. This is information i have been given in the past when i was targeted by some automated software.




  10. #10

    Default

    Just a consideration, if x% of the total wow population was using that bot, why would that number be less for boxers? The boxer I know that got banned in this wave admitted eventually he was using it. Always possible some got banned for no reason, but I after all these years I tend to be rather sceptic about those stories. I guess the good thing for those boxers that got banned is that they probably know themselves what they did wrong, and once their 72 hours are over, they know what not to do again.
    Everything that is fun in life is either bad for your health, immoral or illegal!

Posting Rules

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