If it doesnt get patched, it will definately hurt this game a lot, and this at every level
Pylon Bug to Find Opponent's Location - Page 7
Forum Index > BW General |
TornadoSteve
1006 Posts
If it doesnt get patched, it will definately hurt this game a lot, and this at every level | ||
Alejandrisha
United States6565 Posts
On October 02 2019 13:09 TornadoSteve wrote: This bug goes against everything that made this game so unique, so perfect If it doesnt get patched, it will definately hurt this game a lot, and this at every level i agree. lots of the funny bugs we find 15+ later in sc are cool but this one is very much not cool. in fact i don't even know how it was discovered how the hell would anyone.. but whatever. the archon/hallu bug proved to not be effective and was not patched though i don't think it will never come back into play. this, however, has big repercussions on people who want to maphack but can't afford to. | ||
tec27
United States3696 Posts
On October 02 2019 05:53 Freakling wrote: I think it is probably a variation of the UI refresh glitch (the same that let's you give illegal orders to units, such as the half price Archon glitch). The rest is just the same unit "slot" being occupied by different units. Not really *that* related, this is due to some code around cleaning up graphical elements when things are no longer selected that doesn't function properly when certain sprites animate (e.g. the flashing selection circle), whereas the selection desync stuff is because of how turns are processed/tricks that the UI plays to make things feel responsive. Both can result in dangling/stale data that makes the game do some weird things, but the path to getting there is pretty different. On October 01 2019 01:35 LG)Sabbath wrote: Can anyone explain this other bug as well? I've actually been meaning to make a thread about this one since it got patched. We (ShieldBattery devs) discovered this while trying to track down why pylons sometimes became unpowered during games, but it was too easily exploitable so we didn't want to spread that knowledge more widely until we had a fix in place. I'll create that thread eventually ![]() | ||
Dangermousecatdog
United Kingdom7084 Posts
| ||
stanliv
3 Posts
| ||
MeSaber
Sweden1235 Posts
On October 02 2019 11:26 RowdierBob wrote: Is this really that useful? Does building two pylons early and slowing your tech tree just to make sure you scout the right way make it worth it? I could be missing something here. It doesnt matter even if it is used.. Anyone who kills his pylon early on will be claimed cheater and banned from every competition. There is no need for patch imo. A patch will MOST LIKELY add some other bug or make the game different on some level that you will regret the patching. Edit: Oh and also.. We now have screen-view on minimap to show where people are looking. Kinda obvious if it randomly jumps to a corner on a unit/building. | ||
A.Alm
Sweden508 Posts
On October 08 2019 23:42 MeSaber wrote: It doesnt matter even if it is used.. Anyone who kills his pylon early on will be claimed cheater and banned from every competition. There is no need for patch imo. A patch will MOST LIKELY add some other bug or make the game different on some level that you will regret the patching. Edit: Oh and also.. We now have screen-view on minimap to show where people are looking. Kinda obvious if it randomly jumps to a corner on a unit/building. I agree. Good points. | ||
Qikz
United Kingdom12022 Posts
On October 02 2019 13:09 TornadoSteve wrote: This bug goes against everything that made this game so unique, so perfect If it doesnt get patched, it will definately hurt this game a lot, and this at every level The issue is, we don't know what causes this bug. It you patch it out you could patch out a TON of other bugs. Imagine if it somehow broke unit stacking? You want to take that risk? Better to just ban it at a tournament level. | ||
MeSaber
Sweden1235 Posts
On October 02 2019 13:09 TornadoSteve wrote: This bug goes against everything that made this game so unique, so perfect If it doesnt get patched, it will definately hurt this game a lot, and this at every level Exaggerating a bit sir? There are plenty of bugs in this game. Some are even banned from competitive gaming. This bug isnt game breaking by any means. If it makes games to crash it does however need to get fixed. Else people could make it a thing to crash games. | ||
outscar
2832 Posts
| ||
Qikz
United Kingdom12022 Posts
| ||
Freakling
Germany1526 Posts
| ||
Qikz
United Kingdom12022 Posts
On October 09 2019 06:38 Freakling wrote: Oh, come on, this is not some black magic. It's not even touching on game mechanics… You have no idea what's causing the bug, if you patch out the cause of it it might break some of the now game mechanics that are actually bugs. | ||
Lorch
Germany3672 Posts
On October 09 2019 06:41 Qikz wrote: You have no idea what's causing the bug, if you patch out the cause of it it might break some of the now game mechanics that are actually bugs. So they make a fix, put it on ptr, we test it and see if it breaks anything else. What's wrong with that approach? | ||
Alejandrisha
United States6565 Posts
| ||
Freakling
Germany1526 Posts
On October 09 2019 06:41 Qikz wrote: You have no idea what's causing the bug, if you patch out the cause of it it might break some of the now game mechanics that are actually bugs. The bug is created because some of the garbage is not correctly cleared when refreshing the UI under certain very specific conditions. What else do you think would changing this influence? | ||
StRyKeR
United States1739 Posts
On October 09 2019 06:33 Qikz wrote: Patching is a dangerous precedent as I mentioned before. If you patch this you risk breaking everything else. Your mentality, if generally held, is much too cautious. Many bugs have been patched in the past with no negative repercussions. Sunken colony crash bug when it initially was updated to have 300 hp -- patched with no adverse effects. The "build hatchery, cancel, then kill drone crash" was fixed -- no adverse effects. The "no pylon required to build" bug was patched early August 2019 -- no adverse effects. Most people didn't even know about the no pylon required bug, let alone the patch. | ||
Akio
Finland1838 Posts
On October 08 2019 23:42 MeSaber wrote: It doesnt matter even if it is used.. Anyone who kills his pylon early on will be claimed cheater and banned from every competition. There is no need for patch imo. A patch will MOST LIKELY add some other bug or make the game different on some level that you will regret the patching. Edit: Oh and also.. We now have screen-view on minimap to show where people are looking. Kinda obvious if it randomly jumps to a corner on a unit/building. It's definitely blatant enough for it to be easily monitored in competitive play. I would say if it's a factor in causing a crash, it would be worth trying to fix it. | ||
dUTtrOACh
Canada2339 Posts
On October 09 2019 23:49 Akio wrote: It's definitely blatant enough for it to be easily monitored in competitive play. I would say if it's a factor in causing a crash, it would be worth trying to fix it. This should be patched regardless of whether or not it factors into causing a crash, because it also affects the ladder. One race clearly has an unintended, unfair advantage, and it's easier to patch in a fix than it is to monitor and confirm or deny claims of cheating. By fixing something like this, Blizzard doesn't have to ban anybody. I think not banning your players is better than initiating some witch-hunt for the remainder (if finite) of the game's life because of laziness or ineptitude. | ||
outscar
2832 Posts
| ||
| ||