# Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Printable Version +- The Lurker Lounge Forums (https://www.lurkerlounge.com/forums) +-- Forum: Lurker Games (https://www.lurkerlounge.com/forums/forum-6.html) +--- Forum: Diablo II (https://www.lurkerlounge.com/forums/forum-8.html) +--- Thread: # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: (/thread-276.html) |
# Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Taem - 12-10-2009 EDIT: Decided to post what is already available on the Battle.net forums: Link Quote: âWe traveled for an eternity...â - Marius # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Taem - 12-11-2009 Quote:NT Does the test realm only have parts of the patch Blizzard is currently testing, or is this "the" patch? Because if TPPK, the Barbdrop exploit, and the aura-stacking exploit are not fixed in the new patch, then Blizzard has failed miserably! Their top priority should have been fixing "bugs" and "exploits", then after that rebalancing skills and items, and finally adding new content. Their priorities, if this is "the" patch, are seriously illogical, even if this is a 10-year old game. I don't know what to think as of right now. EDIT-afterthought: I should add that I greatly appreciate the respec ability. To be honest, I just like playing the game and if *no* new content and *no* rebalancing occurred, I would be fine with that so long as the exploits were fixed so I could play this game past normal in public games without getting killed by some hacker. That is really what is ruining this game and driving people away from it, not the lack of new content! We'll see how it all pans out in the end. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - vor_lord - 12-11-2009 Quote:Their priorities, if this is "the" patch, are seriously illogical, even if this is a 10-year old game. I don't know what to think as of right now. Look at the list of changes, and count how many of them required that someone make changes in the underlying program code. There are quite a few, but most of them are at a system level (video changes etc). Compare that to the list of changes that are simply adjustments in the mpq files. Those are changes that any experienced modder could make. Adjusting balance and adding new content requires a different skill set than trying to plug exploits. I think if it was easy to fix such exploits, they would do it. But a game this old... I'm glad they are still doing anything for it. I love the removal of Iron Maiden. If I play again, that is enough to finally move me into hardcore beyond dabbling. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Taem - 12-12-2009 Quote:Look at the list of changes, and count how many of them required that someone make changes in the underlying program code. There are quite a few, but most of them are at a system level (video changes etc). Compare that to the list of changes that are simply adjustments in the mpq files. Those are changes that any experienced modder could make. While I do agree with what your saying in regards to it being a 10-year old game, you'd think Blizzards continued maintenance of Battle.net, not to mention their TOS about using hacks on their restricted realms, kind of go hand-in-hand with fixing game-breaking exploits. What kind of message are they [Blizzard] sending by not fixing an exploit that allows you to kill any player anywhere any time [TPPK]? Where you aware that there are roughly 3-5 Nightmare and Hell games up at any time in hardcore, and if you join any of these games, you will most likely be killed by a TPPK'er within minutes? You simply cannot advance past Normal difficulty in public games in Diablo 2 anymore! If you ask me, you can't get much more game-breaking than this. By neglecting to address game-breaking issues directly relating to play on Battle.net, this speaks volumes about Blizzards stance on the Battle.net service. If they continue to offer Battle.net free of charge, they inherit the responsibility to make sure their games are playable on Battle.net, else they might as well cancel battle.net and discontinue support for a game completely when it has aged past it's prime (to be determined by sales). By keeping Battle.net free for all players as part of Diablo, Star Craft, and War Craft, I expect Blizzard to maintain the game to standards that are playable - i.e. fix game-breaking exploits. They recently made a patch for War Craft 3 (a 7-year old game) to fix a game-breaking exploit, and I applaud them for that. [RANT] On a personal note, I could care less about any new "content", skill changes, or anything else they have planned for Diablo because I just enjoy playing the game, however I want to be able to play the game... The fact that I cannot advance past Normal difficulty in public games without being TPPK'd or drop-hacked on Battle.net is... negligent. Fixing these types of exploits should have and always should be their top priority![/RANT] # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Hammerskjold - 12-12-2009 Quote:Adjusting balance and adding new content requires a different skill set than trying to plug exploits. I think if it was easy to fix such exploits, they would do it. But a game this old... I'm glad they are still doing anything for it. Yep. Can't agree more with ya. I'm giving this one a tentative thumbs up for now. Unless they add a last minute p.s. like 'oh yeah, these are only for ONLINE only', I'm quite pleased they did what they could under the circumstances. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Taem - 12-12-2009 Quote:I think if it was easy to fix such exploits, they would do it. I searched for Drop Barb Exploit Fix and came up with this from numerous web-sites: Quote:Basic description of the 'sploit: What that means is it blocks packet 0xAA if it is corrupt and send the correct packet. How goddamn hard is that? Script kiddies figured out how to fix it without messing with any of the game code or slowing down the servers! Don't tell me Blizzard can't fix it! Pure unadulterated negligence. You have to run a 3rd party program which will most likely get you banned to protect yourself from this exploit! For something that would require a bit of coding: As for TPPK, I've read from modders that it's as simple as adding a sanity check after attacks that if target goes hostile, current attack abruptly ends. It's a simple Null modifier that can be added to every skill. Unlike the Drop Barb Exploit, this would require a bit of coding. But again, the only way to defend yourself against TPPK is with 3rd party programs - that will most likely get you banned - which leave instantly when hostiled. I don't know enough about the Aura-stacking glitch to comment on that. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - vor_lord - 12-12-2009 Those do sound easy to fix. To be honest with respect to all the myriad town portal hostile attacks... just add a 30 second timer after you go hostile before it takes effect. Nothing tricky there. That might even be enough time to get away from the Barb Drop Exploit you describe here. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Zarathustra - 12-17-2009 Hm... I may need to reinstall D2 and see the changes. I haven't played since before synergies were all the rage. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Hammerskjold - 12-21-2009 So, has anyone here actually played the test patch yet? Since I can't at the moment, new computer that I'm on has a strict NO GAMES policy, and it will take a while for me to set up my old gaming one. Just wondering if anyone has some direct practical experience of the difference between 1.12 and 1.13. I don't mean just what the patch notes says, but in a live game session. # Topic 1.13 PTR is LIVE â Patch Notes & FAQ # | 12/10/2009 02: - Archon_Wing - 03-30-2010 Only took a few years to deal with those wisps.:P Ah, actually most of these changes look decent, but of course I assume the realms are all hacked to hell. But in any case, I'm quite shocked they're still patching this |