Avaliação do Tópico:
  • 0 votos - 0 Média
  • 1
  • 2
  • 3
  • 4
  • 5
Novo hack
#1
Nossa, to mto puto!

Quem anda jogando viu o novo hack que os cara tao usando ? O game começa e fica um lag violento pra vc...mas é aqueles lag de placa de video, como se o seu pC tivesse rodando o War3 com 10 fps. Daí, do nada para e fica normal...passa 1 minuto e o War3 fecha sozinho. Vai tomar no cu, tomei 2 desse em 2 dias...ta uma merda jogar na b.net, essa é a real. Se foder...
Responder
#2
Estava pensando em voltar a jogar, mas depois dessa foi pra acabar de vez com o peão mesmo.
Responder
#3
Eu e meu parça estavamos jogando at x2 e levamos uns 4 quithack >_<.

Tirado do forum de war 3 da Blizzard:



Q u o t e:

--Technical aspect: Why/How does this crash the game?---

Everytime you press the F2 hotkey the hack will issue another 500 build orders on an impossible location.

Now if you do that many times your worker will have as example 10000 buildings queued.

As soon as the worker tries to construct the first building of the queue the game will notice the job is not executable and recursively check all others in queue

until it finds an executable one. Because all 10000 buildings are at unbuildable locations the function will call itself 10000 times.. which simply results in a stack overflow.

Around 9000 buildings are required to fill the stack.



This can also be done without any hack, just hold shift and place 9000+ buildings really really fast on the same location. (You probably still need any kind of click tool for this)

When the worker finishes construction of the first building the crash will happen.

It may be also possible with any unit and not using build commands, I have not checked that yet.





For Blizzard there are multiple easy ways to fix this, the easiest is to simply don't allow more than 500 queued jobs per unit (or better, 2000 globally for each player).

Another one would be to don't check jobs recursively, but that still would leave the possibilty of an "laghack" open because adding endless number of jobs will also consume endless memory/cpu.



Q u o t e:

---How to run---

*****.exe is a 'loader', this means it must be placed inside the Warcraft directory.

It is designed to run only with official ROC or TFT version 1.24.2.6378 on official realms.



---MH---

You cannot turn the maphack part off. You also cannot combine this hack with any other hack.



---Crashhack---

Follow these steps to crash your enemy(s):



1) Select any of your workers (say workerA)

2) Right click any other worker (workerB) - workerA should now follow workerB.

3) Keep workerA selected and press F2 multiple times till a message says "total amount 10000"

From now on you must not issue any new order to workerA or you have to return to step 1 again. Or in more simple words: Do not touch workerA till game is over.

4) Wait till all orders are sent (Best way to check this is to see if you are able to move rally point for example, just dont do anything with workerA)

5) Now kill workerB *

6) Wait till workerB is gone. Everyone not using ***** 1.02 should now crash.





*Since every F2 press will spam a lot of "place building" orders any new order will not take effect instantly. It will appear is if you are having a very high ping.

For all 10000 orders it will take 1-2 minutes(!) to be sent over the net. So step 3-4 take some time



To avoid getting disconnected make pauses between every few F2 presses. (Do the rally point check, but dont forget to reselect workerA for next few F2 presses)

Also don't press F2 while game is paused or the "Waiting for players..." window is open.

Its also very important that workerA does not die, else it will not work.



Have fun destroying Battle.net!



---Technical aspect: Why/How does this crash the game?---

Everytime you press the F2 hotkey the hack will issue another 500 build orders on an impossible location.

Now if you do that many times your worker will have as example 10000 buildings queued.

As soon as the worker tries to construct the first building of the queue the game will notice the job is not executable and recursively check all others in queue

until it finds an executable one. Because all 10000 buildings are at unbuildable locations the function will call itself 10000 times.. which simply results in a stack overflow.

Around 9000 buildings are required to fill the stack.



This can also be done without any hack, just hold shift and place 9000+ buildings really really fast on the same location. (You probably still need any kind of click tool for this)

When the worker finishes construction of the first building the crash will happen.

It may be also possible with any unit and not using build commands, I have not checked that yet.





For Blizzard there are multiple easy ways to fix this, the easiest is to simply don't allow more than 500 queued jobs per unit (or better, 2000 globally for each player).

Another one would be to don't check jobs recursively, but that still would leave the possibilty of an "laghack" open because adding endless number of jobs will also consume endless memory/cpu.


[center][center][Imagem: HragUvF.gif][/center][/center][center] [/center]

Responder
#4
ouvi boatos, mas jogando nunca levei isso nao
Responder
#5
Pesquisei sobre o assunto e é novíssimo esse hack....galera tudo discutindo e os post's sao tudo de ontem / antes de ontem. Tem um programa que dizem que é do mesmo criador do executável que do crash-hack, só que é um anti-crashhack



Galera falou que funciona...mas tao com medo de levarem ban da B.net, mas eles acreditam que nao vao levar. Eu to usando tbm porque ja to puto o suficiente por ter perdido 2 jogos assim.



Upei um rep. aqui do Ciara ( Se é o gosu EG.Ciara eu nao sei, talvez seja ) matando um desses xiters apenas usando o sistema de PAUSE do War3. Com o PAUSE, da pra anular o processo de click do xiter e ele tem que começar tudo de novo. E upei tbm o Anti-crash, pra quem quiser usar.



Vlwww, flw!
Responder
#6
eu nem me presto a baixar isso, deixa que a blizzard resolve...
Responder
#7
[quote name='WoK.batAtA' post='1998515' date='Jan 8 2010, 12:56 PM']eu nem me presto a baixar isso, deixa que a blizzard resolve...[/quote]Ja reclamaram no fórum da Blizzard e parece que não deu em nada. O prox. patch de correção falaram que vai sair em 2011. Até lá, esses caras vão fazer a festa com esse crash-hack. Por isso baixei o programa, mas nao peguei nenhum 'crasher' até entao.



Pra ele funfar, tem que por na pasta de instalacao do War3 e dar um clique duplo no .exe. Sao 2 arquivos, um pro TFT e outro pro RoC.
Responder
#8
ja fui vitima desse crash-hack 3x consecutivas VS players diferentes

eu suspeitava disso antes mais como eu estava no play game e jogando com pessoas sempre diferente custou a acreditar

fiquei puto ja somo +/- uns 20 eu acho de crash-hack


Antigo novo membro
Responder
#9
ja utilizei esse sistema de pause quando li lá no forum da blizzard e pans mas... joguei recentemente x um undead que upava as torres , fazia heroi e dai começava o hack. Nao achei o replay aqui pq quando o cara te crasha, o replay não é salvo infelizmente. Se alguem cagar de torre e for hackear, vá direto para um tower rush seguido de siege units e vá controlando as pausadas.


[center][center][Imagem: HragUvF.gif][/center][/center][center] [/center]

Responder
#10
se voce viu que o cara ta usando hack..ja desiste da aprtida por que nao vai ganha..





jogue em Custom game..falei isso em outro topico e é sério..eu vivjo jogando em custom game ph..onde tem1 cara que hosteia o mapa e varios obs..la ninguem tem moral de usa hack e voce tem chance de fica famoso em 1 dia jogando..



joguei no east até que 1 gring me convenceo de ir pro west..agora jogo la em Custom game pg!



meu nick no east é gtbk



no west..nao adianta eu dizer por que esta 0/0/0..entao nao aparece..mas dequalquer maneira





GTB]kZeal


HUEHUEHUEHUE
Responder


Saltar Fórum:


usuários a ver este tópico: 1 Visitante(s)