"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." - Martin Golding
"I cried a little earlier when I had to poop" - Sku
Blizzard don't IP ban, otherwise I wouldn't be able to keep a main for longer than a week.
I always do stupid shit like going to GM Island and opening tickets, screwing around in BGs, etc. And have only ever been banned on the account that was directly involved.
Well, they might if you're running some bot farm, but at that point its obvious all the toons are directly related anyway.
Obviously nothing is certain, but based on my experiences (which are numerous and time-tested) you're safe to hack and bot on one account without your other account(s) being compromised.
No one cares if you use it trust me i flew through orgrimmar lol, ive been useing since it came out and no problems yet, well there is one once your flying and you walk you cant stop walking. but other than that its excellent for gathering herbs and ores +Rep
Positive feedback! +rep
(lol, i didn't know how to say this is awesome)
i get unhandled exceptioneven when i run as admin but i hit continue and then when i log in hit load/refresh i get an unhandled exception and hit continue again but the start/stop keys are grayd out or w/eu wanna describe that as and all i can click is load/refresh
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'WoWBotFramework, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'WoWBotFramework, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at skUywalker.Form1.button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
skUywalker
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/andrew/Desktop/joey%20music/skUywalker.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
************** 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.
IFE YUO CNA READE THSI YUO HVAE DWON SNYDREOM
IFE YUO CNA READE THSI YUO HVAE DWON SNYDREOM
Doubt it unless all the accounts were involved in the rule breaking. If you break the rules on ONE account you won't get banned on other uninvolved accounts under your name.
Like I said, if that were the case my main would've been banned a hundred times over.
Yes they might investigate other accounts with the same details, but I've never had them ban them.
They don't ban all accounts linked to the same credit card, neither do they ban all accounts with the same email address if your account violates the terms, as long as not every account was involved. ( That was atleast like this 1-2 years ago :P (personal experience -.-) Might have changed, but I recall reading something like "Actions are always taken against accounts, not persons." in the terms )
xkisses: Please don't tell me on what OS you encountered this exception.
haha people see my rep and think they know more, i think i've glided around 20 accounts and had 5 banned, on the 4th and 5th ban notification emails, they specifically said that this account and all other accounts with the same email and/or credit card are also being closed. Not gonna lie though I figured someone with 889 rep would know a little more. As far as the OS i encountered this on assuming youre being sarcastic it would be vista home 32 bit or 64 im not sure
IFE YUO CNA READE THSI YUO HVAE DWON SNYDREOM
You are an idiot. This has absolutely nothing to do with rep. So you say you glided with around 20 accounts, and then they were chainbanned. This does not mean that they ban every account with the same email address / creditcard in every case. You were just a special case (I mean 20 accounts, wtf?)
Again, this has nothing to do with rep but experience. I was banned once and no other account was touched by blizz (exact same account data).
The fact that you base opinions/intelligence on reputation tells us enough.
So one could, theoretically, use this to explore on a level 1 toon without getting aggro?
EDIT: I'm getting the same error as xkisses when I try to run the app. I'm on XP, ran as admin, and have the latest .NET, and all the DLL files are together.
Last edited by _duracell; 04-13-2009 at 12:46 PM.
If ur not doing this yet, you should just have it making a new thread inside of wow that checks the current value of the movement state and overwrites it if it changed. would probably be faster and less CPU intensive. just have the autoit app allocate some memory for the code and for the var containing the desired movement state. createremotethread and voila, it's running in a loop.
Just a thought =/
Got nothing to do with your rep, I stated multiple times my opinion was based off personal experience. You're a dipshit.
Also, if you WERENT a dipshit you might have realised that that may have happened given the extreme circumstances. It's called discretion, they're well within their rights to do it, but in normal cases its not something they do.
Also, 20 accounts? You're a small fish, sorry, doesn't mean a thing. Do a large scale test, THEN try and flaunt your numbers, until then it just makes you look stupid.
+Rep. Going to try it when I am going on my pc (Mac now).
Another reason why Blizzard wouldn't ban IP's is because on university's/schools/public places their could be more then 1 player. So let's take 10 players are playing WoW under the same IP. 1 player uses a cheat, the 9 others are responsible for it?
IP-banning is not likely going to happen at blizzard :-)![]()