|
On September 08 2010 14:12 Rifty wrote:Show nested quote +On September 08 2010 14:09 Half wrote:The people bashing Blizzard's coding obviously has no clue what its like to actually develop a game from scratch. Bugs happen no matter how much internal QA is put in to it, you need a huge amount of users testing before everything gets exposed, for any game and any application. Think of all the little things that people didn't find out in BW until years after it's been released.
Saying the whole programming team doesn't know how to code properly is just ignorant, i mean they make games that sell millions of copies worldwide, i think they know what they are doing...
Blizzard will fix this... This post is just ignorant. It has nothing to do with the programming team (which was pretty well done), rather, the developers in charge of compiling data. [ Um, if you actually read my post instead of assuming, i am defending the programming team... The dev's compiling the data and resources are engineers too on the team....
Then what was this whole rant about?
The people bashing Blizzard's coding obviously has no clue what its like to actually develop a game from scratch. Bugs happen no matter how much internal QA is put in to it, you need a huge amount of users testing before everything gets exposed, for any game and any application. Think of all the little things that people didn't find out in BW until years after it's been released.
All I'm saying is that this mistake was pretty stupid imo, and the in game databases are just really sloppy to begin with,
|
On September 08 2010 14:14 Half wrote:Show nested quote +On September 08 2010 14:12 Rifty wrote:On September 08 2010 14:09 Half wrote:The people bashing Blizzard's coding obviously has no clue what its like to actually develop a game from scratch. Bugs happen no matter how much internal QA is put in to it, you need a huge amount of users testing before everything gets exposed, for any game and any application. Think of all the little things that people didn't find out in BW until years after it's been released.
Saying the whole programming team doesn't know how to code properly is just ignorant, i mean they make games that sell millions of copies worldwide, i think they know what they are doing...
Blizzard will fix this... This post is just ignorant. It has nothing to do with the programming team (which was pretty well done), rather, the developers in charge of compiling data. [ Um, if you actually read my post instead of assuming, i am defending the programming team... The dev's compiling the data and resources are engineers too on the team.... Then what was this whole rant about? Show nested quote +The people bashing Blizzard's coding obviously has no clue what its like to actually develop a game from scratch. Bugs happen no matter how much internal QA is put in to it, you need a huge amount of users testing before everything gets exposed, for any game and any application. Think of all the little things that people didn't find out in BW until years after it's been released.
Rant? Did you even read the earlier posts? People are bashing Blizzard's programming team saying they have no clue what they are doing... I am merley pointing out that bugs will occur regardless of the amount of internal testing you do...
You may want to re-read the thread?
|
Assuming you need a 3rd party hack to do this, it was not any individual programmers fault as he just develops what the design says for it to pass the end user testing.
Fault is with the designers and lead programmers for designing a game that is so easily exploited. Or it is the management for not wanting to fork out the budget for server hosted games which cannot be hacked from the client.
You would think at least they have learned from mistakes from their past games?
|
On September 08 2010 14:17 Rifty wrote:Show nested quote +On September 08 2010 14:14 Half wrote:On September 08 2010 14:12 Rifty wrote:On September 08 2010 14:09 Half wrote:The people bashing Blizzard's coding obviously has no clue what its like to actually develop a game from scratch. Bugs happen no matter how much internal QA is put in to it, you need a huge amount of users testing before everything gets exposed, for any game and any application. Think of all the little things that people didn't find out in BW until years after it's been released.
Saying the whole programming team doesn't know how to code properly is just ignorant, i mean they make games that sell millions of copies worldwide, i think they know what they are doing...
Blizzard will fix this... This post is just ignorant. It has nothing to do with the programming team (which was pretty well done), rather, the developers in charge of compiling data. [ Um, if you actually read my post instead of assuming, i am defending the programming team... The dev's compiling the data and resources are engineers too on the team.... Then what was this whole rant about? The people bashing Blizzard's coding obviously has no clue what its like to actually develop a game from scratch. Bugs happen no matter how much internal QA is put in to it, you need a huge amount of users testing before everything gets exposed, for any game and any application. Think of all the little things that people didn't find out in BW until years after it's been released. Rant? Did you even read the earlier posts? People are bashing Blizzard's programming team saying they have no clue what they are doing... I am merley pointing out that bugs will occur regardless of the amount of internal testing you do... You may want to re-read the thread?
Look thats exactly what I thought you were doing on all accounts. Let me rephrase it.
And as I said, it has nothing to do with internal testing nor the programming team or w/e. This isn't OMG OBSCURE UNFORSEEABLE BUG, I'm surprised this isn't happening more frequently with the way SC2 gameplay databases are set up (very sloppily).
I can give you a lot of examples with really stupid setups. Basically because I've been working with the editor a lot recently :/.
Fault is with the designers and lead programmers for designing a game that is so easily exploited.
See, this isn't some fundamental flaw with the game, nor is it unforseeable QA mistake. Its basically "Hey lets just go around removing units, and instead of thoroughly removing them and taking an extra minute, just edit one data feild instead".
Basically, under the "Gateway Warp" skill, there are a few subcommands. 5. And when they removed 1, instead of actually removing it, they just removed the UI command in the "command card" field. And they do this a lot too. Pretty sloppy imo.
|
I think people need to chill out. Remember float a drone? Stacked Hydras?
We're not even 3 months into this game's release
|
wow i think this is very cool and ya needs to be fixed asap
|
I'm curious as to how long it will take blizzard to patch this out. It would be fairly easy to fix i imagine, so i wouldn't be surprised to see a "bug fix" patch soon.
|
On September 08 2010 14:21 Half wrote:
Look thats exactly what I thought you were doing on all accounts. Let me rephrase it.
And as I said, it has nothing to do with internal testing nor the programming team or w/e. This isn't OMG OBSCURE UNFORSEEABLE BUG, I'm surprised this isn't happening more frequently with the way SC2 gameplay databases are set up (very sloppily).
I can give you a lot of examples with really stupid setups. Basically because I've been working with the editor a lot recently :/.
See, this isn't some fundamental flaw with the game, nor is it unforseeable QA mistake. Its basically "Hey lets just go around removing units, and instead of thoroughly removing them and taking an extra minute, just edit one data feild instead".
Basically, under the "Gateway Warp" skill, there are a few subcommands. 5. And when they removed 1, instead of actually removing it, they just removed the UI command in the "command card" field. And they do this a lot too. Pretty sloppy imo.
Yeah, the ability lists are so full of holes and old, unused stuff. +2 immortal range, anyone? All you need is a robotics bay...
|
Assuming the hacker doesn't make his hack public Blizzard should be able to patch it before it becomes a problem, hopefully.
|
wow...that's a really annoying hack to deal with probly. =_=
but then again, if you spam zealots, then I don't think that you should have any problems vs the immortals =P
|
|
|
On September 08 2010 14:52 Inori wrote:
Tidings of doom are upon us!
This hack proves that Blizzard doesn't check anything that is sent/recieved in-game. This means that this is just a tip of an iceberg if they don't react soon enough (and 99% that they won't, that guy won't even be banned for another 2-3 months at least). Theoretically a hacker can do whatever whenever as long as the packet recieving game client eats it. And if it doesn't.. that's just another drop hack right there.
Jeesh. Can't wait for ICCUP 2.0.
Except they're limited to things that are possible within the game client for a ladder game. The immortal warp-in is just old data that was overlooked in the game client and can be quickly patch out.
Also, nice advocating piracy there.
|
This hack proves that Blizzard doesn't check anything that is sent/recieved in-game. This means that this is just a tip of an iceberg if they don't react soon enough (and 99% that they won't, that guy won't even be banned for another 2-3 months at least). Theoretically a hacker can do whatever whenever as long as the packet recieving game client eats it. And if it doesn't.. that's just another drop hack right there.
Jeesh. Can't wait for ICCUP 2.0.
Actually, thankfully, this isn't really 100%, all this hack does is send action commands bypassing the command card, which I'm pretty sure is 100% local.
Its definitely not actually hacking the host servers and changing shared data.
|
Despite it beeing a hack and frowned upon, warping in immortals is totally badass =P
|
On September 08 2010 14:59 banana wrote:
Despite it beeing a hack and frowned upon, warping in immortals is totally badass =P
totally, they should be warpable with robo bay or sth x) and enable +2 range upgrade while were at it, yay!
|
The guy is probably banned already. I wanted to add him to check his build order but I can't. "Unable to add this friend".
|
The ability to warp in immortals would definitely make protoss WAAAYYY too good at breaking sieges (just get more gateways to warp in stuff instead of even needing to make more robo facs!)
Still, the idea is completely hilarious, and the fact that this was even possible is definitely an indication of sloppy cleanup on Blizzard's part.
If there was a +2 range upgrade enabled for immortals....man......that would make the things actually useful against marauders instead of getting kited all day long.
|
|
|
On September 08 2010 15:05 Adonisto wrote:
The guy is probably banned already. I wanted to add him to check his build order but I can't. "Unable to add this friend".
If you tried from a NA account i think i found your problem.
|
On September 08 2010 15:12 Naoko wrote:Show nested quote +On September 08 2010 15:05 Adonisto wrote:
The guy is probably banned already. I wanted to add him to check his build order but I can't. "Unable to add this friend". If you tried from a NA account i think i found your problem.
Make sense I didn't realise it was from another server. Oh well.
|
|
|
|
|
|
EPT
