Reducing the risk of ban

[Bad_Attitude]

Hi Guys,

might be a stupid question, but can you tell me in General how high is the risk reciving a ban when playing with warpack?
Is there any Chance reducing the risk by playing only with the aimbot for example?

I am using the warpack currently on a new account, no ban so far 
Now I am thinking about to use the aimbot only on my main account, but I am not sure about how high is the risk to get banned?

Thank you in advanced for you help

[Beznosko]

-Is it possible to get banned for using Warpack?
Yeah, maybe, but only on the initiative of the end user.

For example:
Spread public access game screenshots, which show that the use Warpack.
Spread public access video game which shows that the use
Warpack.
Most of the game shoutingthat you play with Warpack.
After the release of an update without waiting for go-ahead to overwhelm developers Warpack game servers World Of Tanks and play using Warpack.
With their profile game developers to write, saying that you love Warpack
and play with them more interesting than without it.

I use Warpack more than a year and had not received any warning or ban!
Forgive me that did not answer immediately!

[Lance]

I too have used warpack for over a year and not been banned. As I understand it, warpack sits on our computers and only uses info that is normally passed by WOT. So the only ways of getting banned are by being stupid and putting images up on net showing warpack use or by boasting about it online....

[Beznosko]

I too have used warpack for over a year and not been banned. As I understand it, warpack sits on our computers and only uses info that is normally passed by WOT. So the only ways of getting banned are by being stupid and putting images up on net showing warpack use or by boasting about it online....

You are absolutely right!

[spammenot]

Basically, the risk of getting banned is minimal. There's lots of users on this forum who have been using warpack for over a year (myself included) and haven't had any problems. With that said, warpack does leave a certain "signature".

So here's how you can signififcantly increase your risk of getting banned:

a) Publishing replays, screenshots, videos or streams from your account while using warpack
- Warpack corrupts the replay files. If you try to upload a replay with warpack used during the recorded game to wotreplays.ru, you'll notice that that site fails to display the stats, instead filling everything out with zeroes.
- The work of aimbot can be seen in replays by someone who knows how it works. One user got banned after posting a video in which he is driving away, camera facing forward, but turret turned backward and obviously locked on a target
- There is evidence of warpack on screenshots. This one is kind of self-explanatory, but from a couple years of working in tech support during college, I learned to never underestimate the human stupidity. From the warpack button in the garage to red dots to tree markers on the map, warpack obviously displays things not found in unmodified game.

b) Sending files to the game developers
- During troubleshooting, game developers may ask for certain files. Some of these files may contain markers identifying the use of warpack. The most obvious example is already described above: replay files contain evidence of warpack use, both direct (files are corrupt) and indirect (observable from gameplay). python.log contains a log of information related to what the pythin engine did, and since it is responsible, among other things, for handling modifications, it may contain identifying information. Warpack developers would have to step in here to explain where else such evidence can be found, but the basic rule of thumb is do not send anything.

Now, as to how warpack cannot be detected: those observing you in game (spectating) do not get 'target locked' messages when you lock on a target with warpack. It goes without saying that the game's own locking function should be bound to a different key, since that one they can in fact see. They also won't see any visual modifications such as fallen tree markers or transparent bushes.

This, in a nutshell, is it. Remember, the best idea is to use common sense, avoid attracting attention (especially of the administration, if you see someone with one of the Wargaming clan tags, be careful in that battle.

That's pretty much it, the best idea is to use common sense and avoid attracting attention (especially if you see one of the WG clantags, popular streamers or mods in your battle). And remember: Don't. Share. Anything.

p.s. quick disclaimer: of course, any of this can change at any moment. So far, WG hasn't really gone after warpack users, but one day they may decide to. Never start a game with warpack after an update before getting a green light from warpack developers (you might need to monitor the russian forum for it, look for posts from Sherman and use google translate).

[Beznosko]

Basically, the risk of getting banned is minimal. There's lots of users on this forum who have been using warpack for over a year (myself included) and haven't had any problems. With that said, warpack does leave a certain "signature".

So here's how you can signififcantly increase your risk of getting banned:

a) Publishing replays, screenshots, videos or streams from your account while using warpack
- Warpack corrupts the replay files. If you try to upload a replay with warpack used during the recorded game to wotreplays.ru, you'll notice that that site fails to display the stats, instead filling everything out with zeroes.
- The work of aimbot can be seen in replays by someone who knows how it works. One user got banned after posting a video in which he is driving away, camera facing forward, but turret turned backward and obviously locked on a target
- There is evidence of warpack on screenshots. This one is kind of self-explanatory, but from a couple years of working in tech support during college, I learned to never underestimate the human stupidity. From the warpack button in the garage to red dots to tree markers on the map, warpack obviously displays things not found in unmodified game.

b) Sending files to the game developers
- During troubleshooting, game developers may ask for certain files. Some of these files may contain markers identifying the use of warpack. The most obvious example is already described above: replay files contain evidence of warpack use, both direct (files are corrupt) and indirect (observable from gameplay). python.log contains a log of information related to what the pythin engine did, and since it is responsible, among other things, for handling modifications, it may contain identifying information. Warpack developers would have to step in here to explain where else such evidence can be found, but the basic rule of thumb is do not send anything.

Now, as to how warpack cannot be detected: those observing you in game (spectating) do not get 'target locked' messages when you lock on a target with warpack. It goes without saying that the game's own locking function should be bound to a different key, since that one they can in fact see. They also won't see any visual modifications such as fallen tree markers or transparent bushes.

This, in a nutshell, is it. Remember, the best idea is to use common sense, avoid attracting attention (especially of the administration, if you see someone with one of the Wargaming clan tags, be careful in that battle.

That's pretty much it, the best idea is to use common sense and avoid attracting attention (especially if you see one of the WG clantags, popular streamers or mods in your battle). And remember: Don't. Share. Anything.

p.s. quick disclaimer: of course, any of this can change at any moment. So far, WG hasn't really gone after warpack users, but one day they may decide to. Never start a game with warpack after an update before getting a green light from warpack developers (you might need to monitor the russian forum for it, look for posts from Sherman and use google translate).

The answer is

[Beznosko]

Problem solved, topic closed.