Staredit Network

Yes! Starcraft Patch 1.11b is here. Bug fixes:


LAST EDIT: I keep getting misinformed, its the rush of the new patch I swear.

Stacking: You cannot do this anymore! It doesn't work!
Unvision: You can do this! It works!

Curse the patch for being so confusing!

That existed? They can't do crap about the ones I've seen, but they can fix the ones I never heard of. This bug probably wasn't real but they want to look like they're doing something.

no more stacking now :/ cant unvision yourself anymore.

Its probaly refering to the hack. This means great things, because now we can antihack EVERYTHING

B.net will be a less fun place to play =(

Not really, its actually for the better. We wont see as many of the same sunken D maps and whatever. I wasn't intending to use this bug for anything anyway.

Now I don't give a crap about what other people think, but this means that Blizzard still supports SC (as much as they only did it for WCG).

So what if your favorite bug became unnoticed? Who cares, really? The main point of this patch was to fix the issue with Macs that disabled StarEdit. Also, they patched up some stuff because they didn't want to look like they weren't doing anything.

The stacking is great news, really, I was surprised they could do that. However, that means that there are less tricks available in map making. All of the current stacked defense maps (correct me if I'm wrong) are now useless.

Even though this patch was primarily to fix the StarEdit issue with Macs, Blizzard was nice enough to release the other fixes (as small as they could be). Hopefully, this patch didn't add new bugs, or else my opinion of it will change... drastically... :ph34r:

Stacking was never useful, it was only used in bad defense maps.

This isn't really all that much of a BAD thing. Besides, Blizzard isn't out to take out all the bugs in the game, just the ones that effect Melee tournaments and hacking in general. Its unlikely (expecially at SC's age) they'll take out the Player 13/14 speed increase and 0 wait triggers. Things like that dont actually do anything with melee, thus, its likely most of the map making tricks we've come to love will always be there for us.

*winces*

Man that stacking fix is going to ruin a couple thousand D maps. Oh well, at least none of my maps are compromised (I think)...

:ph34r: shut up...


Here's the deal about stacking: u stack cannons so more of them shoot, and you don't lose the game by the 2nd level (high templars). But with these Defense maps, pros (like me ) don't stack too much, we make mazes (unlike some newbs that just stack 20 cannons in the center of their squares) so that the critters have to go a longer distance, during which they die! Stacking also eliminates the space, e.g. between pylons so the little zerglings or probes have to walk around as well as big ol' ultras. However, they never thought of simply putting a small unit with range (e.g. marine) inside that space, which practically acts as a cannon without the stacking.

Damn it blizzard screwed up my best map. I hate them forever, I should quit now.

Edit: yeah house of the haunted still works. It will turn the vision off.

What bothers me isn't the stacking, it's that you can't turn off your own vision anymore. Goodbye fun horror maps... Goodbye. ='(

Pfft. I liked stacking, if anything. What's easier to take out in a Melee game? 20 Sunken Colonies? Or 20 Sunken Colonies stacked on one 2x2 area. Yeah, 5 Tank shots would take out all 20. If people want to put themselves at a disadvantage, that's not my fault. I say let them stack away.

Yeah I just tested it. I can still turn vision off. Tested it again with drones on a map that isn't installation. Vision will turn off and when i tried to stack it just gives me the error sound.

Eh, you can't turn vision off for yourself I think. I don't see where other players was implied. :/

On the map I used to test, it didn't allow me to unvision. I'm attempting to find out the solution.

yes you can turn it off for yourself. Yoshi you should update the main post.

Meh, I PMed you with details and tried to post it in the tips/tricks section, but I guess it got rejected, so here's the deal with Player 13/14 speed increase:

The increased game speed happens because the game only allocates space for 12 players in arrays. So, by indicating another owner, you're basically overwriting the memory (the game doesn't know where the hell to put your unit's data). Therefore, it creates another array header (Player 13), with only the unit data that the map caused it to create. However, this comes at a cost: the "new" data that wasn't supposed to be there overwrites the section of the memory that was supposed to hold the data for the game speed. (This happens to all the clients since they all loaded the same map.) By doing this, it corrupts the game speed data that makes it go faster.

Player 13/14 units destroy some parts of your map, because not only does it corrupt game speed data, it also corrupts other game data that would otherwise be in the arrays. I'm not sure what it is though because I'm too lazy to test it out.

It would be hard for Blizzard to change the Player 13/14 unit issue, because the player arrays contain much of the data which is being recycled throughout the program. If you were to change all that, it would take a long time since you would have to sift through the thousands of lines of code, knowing that if you make one mistake, it might come up somewhere down the road and require another patch.

Another way to stop the issue would be to disallow Player 13/14 units to be rendered from the map data, but that would just ruin tons of maps out there that use the Player 13/14 units.

Some of the "map making tricks we've come to love" also affect Melee games, so not all of them are always going to be with us.

Edit: Meh, sry, I didn't bother to read the update. I must have rushed to reply
So Yoshi, could you please tell us the names of the maps that work/that don't work?

Thats not true you can still unvision yourself.

No one appears to have read my update.

Stacking has alot a problems with it though like when a noob stacks like 100 cannons on a pylon and it freezes and he leaks and we lose thats when it sucks and its really a noobs way out of making a good defense.

So what changes exactly were made to unvisioning? Can someone explain it clearly in detail?

Meh.....Blizzard may have done the right thing, ruining all those Defense Stack maps and stuff...but many people who loved those games will be mad and frusturated.....We will be seeing less and less games of "TURRET D CUM NOW"...heheh...maybe is was for the best

Hmm, maybe if there was a trigger so you could only stack like 15 in one area... That would eliminate freezing in a defense map, possibly.

No, that isn't small.


Apparantly, Blizzard once again changed the Starcraft addresses to prevent 3rd party programs, the update also rendered the following hacks useless if they were ever changed to work with 1.11b:

-SCV Repair hack
-Creep Hack(Allows you to stack buildings on top of creep and build zerg buildings off the creep as well as land terran buildings on water, etc.)


I'd say that's quite an improvement.

Hacks that work in 1.11b already:

-Kill unit hack


Hacks that could work if converted:

-3 State Maphack with antihack protection
-Ally Alert with Auto Unally
-4 Page Stathack
-In Game Timer
-Stack Hack detection
-Stay Alive
-Crash hack protection / detection
-Unit Alerts
-Game / Lobby Chat color


Hacks that could be 'remade' to work:

-Stack Hack


That's the information in the "hacking world". Well, time to update...