an ez fix woul be: if you are in town, it's impossible for you to harm anyone. or, have a 10 second delay between going hostile and actually being able to hurt anyone.
tppk is the reason i refuse to play bnet hardcore anymore|||Oops, can someone change the title to A tppk free 1.13?
It really feels like tppk is something that should've been removed a long time ago. If it's fixed in 1.13 i'm going straight back to hc though I havent played in a while|||I doubt blizz will fix it, but who knows. And even if they do i'm affraid the script kiddies will find another way around it.
If not you can simply fix it by playing with trusted people only though.
*cough come play in gauss cough*
|||Given Blizzard's (abysmal) past track record of malign neglect of this issue, I'm anything but optimistic on the chances that 1.13 can rid us of TPPK (and associated cheats and hacks, such as the one where the cheaters can hostile and kill a victim right by the Stash in the middle of the Rogue Encampment), for anything more than a few weeks at best.The basic problem here is that it is too easy for cheaters to hack the Diablo II client (e.g. GAME.EXE), and / or hack the Battle.Net data stream that travels between the client and whatever Battle.Net server that you happened to associate with, when you started your Diablo game session. To the best of my knowledge, neither of these is encrypted, meaning that whereas you, as an honest player, are using the software that Blizzard intended you to use, so that you stay within the rules of the game, the griefer can hack the client and the PC-to-Battle.Net traffic so that he can, basically, use any software he wants.
The number of "creative" bypasses of game rules that can be engineered by this kind of malicious hacking are potentially endless. I would hope that Blizzard would try to implement some simple server-side controls, e.g. the above-noted timer before hostility can be triggered, but this will just cause the cheaters and hackers to move on to other tricks, for example the "drop hacks" that were popular a few years ago (e.g., sending corrupt packets to another user's computer or the server, causing the server to think that the victim was still in the game, while the victim's PC shows a blank screen; this would defeat the timer by allowing the griefer to simply wait until the timer runs out, then attack the victim's helpless character), or... who knows what.
The pricks who use TPPK will work around the clock to ensure that they can keep on ruining the D2 playing experience for the other 99.9999999999% of Battle.Net players who want to honestly adventure and not duel. There are only 3 things that really will stop them:
(1) Robustly encrypted client software and data streams, so they can't hack or modify the protocol (would require a major re-engineer of the client; good luck getting Blizz to spend the development dollars for that, for an 8 year old game);
(2) Find some way to break the anonymity behind which the griefers always hide, track them down at home and have each of these "tough guy" little 13 year olds served with a ($ U.S.) 50 million dollar lawsuit (gee, Daddy, I didn't think...);
(3) Same as (2), but when you find them, physically beat the @#$#% out of them
, so that they can feel what it's like to be bullied (I can dream, can't I?);Bottom Line : Don't get your hopes up, and find some friends with whom you can play safely.
Cheers
Mr. Bill|||Quote:
Given Blizzard's (abysmal) past track record of malign neglect of this issue, I'm anything but optimistic on the chances that 1.13 can rid us of TPPK (and associated cheats and hacks, such as the one where the cheaters can hostile and kill a victim right by the Stash in the middle of the Rogue Encampment), for anything more than a few weeks at best.
The basic problem here is that it is too easy for cheaters to hack the Diablo II client (e.g. GAME.EXE), and / or hack the Battle.Net data stream that travels between the client and whatever Battle.Net server that you happened to associate with, when you started your Diablo game session. To the best of my knowledge, neither of these is encrypted, meaning that whereas you, as an honest player, are using the software that Blizzard intended you to use, so that you stay within the rules of the game, the griefer can hack the client and the PC-to-Battle.Net traffic so that he can, basically, use any software he wants.
The number of "creative" bypasses of game rules that can be engineered by this kind of malicious hacking are potentially endless. I would hope that Blizzard would try to implement some simple server-side controls, e.g. the above-noted timer before hostility can be triggered, but this will just cause the cheaters and hackers to move on to other tricks, for example the "drop hacks" that were popular a few years ago (e.g., sending corrupt packets to another user's computer or the server, causing the server to think that the victim was still in the game, while the victim's PC shows a blank screen; this would defeat the timer by allowing the griefer to simply wait until the timer runs out, then attack the victim's helpless character), or... who knows what.
The pricks who use TPPK will work around the clock to ensure that they can keep on ruining the D2 playing experience for the other 99.9999999999% of Battle.Net players who want to honestly adventure and not duel. There are only 3 things that really will stop them:
(1) Robustly encrypted client software and data streams, so they can't hack or modify the protocol (would require a major re-engineer of the client; good luck getting Blizz to spend the development dollars for that, for an 8 year old game);
(2) Find some way to break the anonymity behind which the griefers always hide, track them down at home and have each of these "tough guy" little 13 year olds served with a ($ U.S.) 50 million dollar lawsuit (gee, Daddy, I didn't think...);
(3) Same as (2), but when you find them, physically beat the @#$#% out of them
, so that they can feel what it's like to be bullied (I can dream, can't I?);Bottom Line : Don't get your hopes up, and find some friends with whom you can play safely.
Cheers
Mr. Bill
haha, #2 is nice (gee daddy i didnt think)
"THATS RIGHT U DIDNT THINK, SON"|||Quote:
Seeing as how TPPK is a big issue in hardcore, does anyone seeing them fixing it by adding a 5-10 second wait time to pvp damage in hardcore (dont know alot of people who duel)?
I do not think so. The time i most intensly played this game public was HCL3. A german TPPK "explained"(after he failed to autokill my anti TPPK build) to me that the victim is hostiled looong before he realises it. It is this client/server mechanic problem which the creators of 3rdparty programs abuse. A victim plays with a TPPK for a couple of minutes and he is constantly hostiled. The TPPK just waits for the right moment, ..client sends packages to server.. and bang...deeds. I assume that the script creators will find a way to bypass wait times always, except...the hostile system changes completely.(consensual PvP button)
Quote:
How do you guys think it will affect they game if they fix TPPK? Alot more public games? Public runs?
Definately there will be more games. This madness is going on for four years now, i still do not understand why Blizzard ignores it and does not take action, but who knows. 1.13 is the last hope. In order to get fans back and to make them spend $$ for D3 there could be changes.
- Larger stash
- Respecing
have been on the suggestions list and seem to be implemented, TPPK was mentioned repeatedly, it will be hard for Blizzard to ignore it this time.
Nilaripper|||Quote:
I do not think so. The time i most intensly played this game public was HCL3. A german TPPK "explained"(after he failed to autokill my anti TPPK build) to me that the victim is hostiled looong before he realises it. It is this client/server mechanic problem which the creators of 3rdparty programs abuse. A victim plays with a TPPK for a couple of minutes and he is constantly hostiled. The TPPK just waits for the right moment, ..client sends packages to server.. and bang...deeds. I assume that the script creators will find a way to bypass wait times always, except...the hostile system changes completely.(consensual PvP button)
If I understood you correctly, I don't think it's the case. I never experienced anything like that, nor did I have "anti-TTPK chars" to survive from script kiddies' attempts. Back when I played a lot and had a few high levels, TPPKs were easy to spot from gear and their movement pattern. But that was HCL2 I guess, don't remember anymore.
This season no experience from TPPKs, as I pretty much played only in gauss games for the short while it lasted.
|||Quote:Given Blizzard's (abysmal) past track record of malign neglect of this issue, I'm anything but optimistic on the chances that 1.13 can rid us of TPPK (and associated cheats and hacks, such as the one where the cheaters can hostile and kill a victim right by the Stash in the middle of the Rogue Encampment), for anything more than a few weeks at best.
The basic problem here is that it is too easy for cheaters to hack the Diablo II client (e.g. GAME.EXE), and / or hack the Battle.Net data stream that travels between the client and whatever Battle.Net server that you happened to associate with, when you started your Diablo game session. To the best of my knowledge, neither of these is encrypted, meaning that whereas you, as an honest player, are using the software that Blizzard intended you to use, so that you stay within the rules of the game, the griefer can hack the client and the PC-to-Battle.Net traffic so that he can, basically, use any software he wants.
The number of "creative" bypasses of game rules that can be engineered by this kind of malicious hacking are potentially endless. I would hope that Blizzard would try to implement some simple server-side controls, e.g. the above-noted timer before hostility can be triggered, but this will just cause the cheaters and hackers to move on to other tricks, for example the "drop hacks" that were popular a few years ago (e.g., sending corrupt packets to another user's computer or the server, causing the server to think that the victim was still in the game, while the victim's PC shows a blank screen; this would defeat the timer by allowing the griefer to simply wait until the timer runs out, then attack the victim's helpless character), or... who knows what.
The pricks who use TPPK will work around the clock to ensure that they can keep on ruining the D2 playing experience for the other 99.9999999999% of Battle.Net players who want to honestly adventure and not duel. There are only 3 things that really will stop them:
(1) Robustly encrypted client software and data streams, so they can't hack or modify the protocol (would require a major re-engineer of the client; good luck getting Blizz to spend the development dollars for that, for an 8 year old game);
(2) Find some way to break the anonymity behind which the griefers always hide, track them down at home and have each of these "tough guy" little 13 year olds served with a ($ U.S.) 50 million dollar lawsuit (gee, Daddy, I didn't think...);
(3) Same as (2), but when you find them, physically beat the @#$#% out of them
, so that they can feel what it's like to be bullied (I can dream, can't I?);Bottom Line : Don't get your hopes up, and find some friends with whom you can play safely.
Cheers
Mr. Bill
While option 3 seems a little excessive I would like that to be my first choice
But alas' that is not an option so lets go with #2 that would be great.
What about account banning? like if someone is a tppk would it be possible to ban their accounts? I am sure people have thought of this but I just want to know the reason for why it would not work
Thanks|||I'm being optimistic. I think they will fix tppk in 1.13. They can't possible ignore the massive number of requests for it. They've tried before. They failed, but they did try. This time around theres alot of time being spent on 1.13 and i expect they may well get it done right this time. The way i would do it is just make it so that you have to be in town for 30 seconds before you can declare hostility. Sorts the porblem fine if you ask me.
No comments:
Post a Comment