• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EST 02:49
CET 08:49
KST 16:49
  • Home
  • Forum
  • Calendar
  • Streams
  • Liquipedia
  • Features
  • Store
  • EPT
  • TL+
  • StarCraft 2
  • Brood War
  • Smash
  • Heroes
  • Counter-Strike
  • Overwatch
  • Liquibet
  • Fantasy StarCraft
  • TLPD
  • StarCraft 2
  • Brood War
  • Blogs
Forum Sidebar
Events/Features
News
Featured News
Team Liquid Map Contest #238[ASL22] Finals Preview: Sweet Victory!12[ASL22] Ro4 Preview: Mirror Mirror6[ASL22] Ro8 Preview: Within Reach5[ASL22] Ro8 Preview: In A Tizzy11
Community News
Weekly Cups (Nov 9-15): Clem and herO take over4Dark completes military service, returns to SC217[BSL23] RO16 Group Stage20Weekly Cups (Nov 2-8): herO back on top?2Weekly Cups (Oct 26 - Nov 1): MaxPax, herO, Solar win0
StarCraft 2
General
No more SC2 streamers on team liquid? Weekly Cups (Nov 9-15): Clem and herO take over Team Liquid Map Contest #23 Dark completes military service, returns to SC2 StarCraft open world shooter announced at BlizzCon
Tourneys
soO & FanTaSy return! SC2 Kevin Scrim 4v4 (Nov 16) Sparkling Tuna Cup - Weekly Open Tournament RSL goes to London! 2026 Offline Finals Nov 21-22 Sea Duckling Open (Global, Bronze-Diamond) Dark returns! GSL CK #7 4v4 Team Battle (Nov 19)
Strategy
[H] ZvP Mid-Late Game: Stalkers Collossi HT
Custom Maps
[G] How to playtest arcade maps Starcraft 2 Advance [D] the control group Simple Questions/Answers
External Content
Mutation # 552 Secret Storm The PondCast: SC2 News & Results Mutation # 551 Robotic Revival Mutation # 550 Graveyard Shift
Brood War
General
List of top players active on ShieldBattery Light introduces ShieldBattery on his YouTube BGH Auto Balance -> http://bghmmr.eu/ BW General Discussion NaDa's Body
Tourneys
SC1 Kevin Scrim hosted by SOOP (Nov 18-19) [Megathread] Daily Proleagues [BSL23] Ro16 Group D - Sunday 21:00 CET [BSL23] Ro16 Group B - Saturday 21:00 CET
Strategy
Pluto's TvP 5Marine 2Medic Push Simple Questions, Simple Answers Infested Terran strategies in 2026 Nuke strategy worked in K-League 2026-11-09
Other Games
General Games
Warcraft III: The Frozen Throne Nintendo Switch Thread Stormgate/Frost Giant Megathread Free Space RTS Game, optimised f. Phone/Tablet etc List of Game Threads
Dota 2
League of Legends
[TL LoL EUW IHs] Teemo shall perish
Heroes of the Storm
Heroes of the Storm 2.0
Hearthstone
Deck construction bug
TL Mafia
TL Mafia Community Thread
Community
General
US Politics Mega-thread Trading/Investing Thread Artificial Intelligence Thread Russo-Ukrainian War Thread Things Aren’t Peaceful in Palestine
Fan Clubs
Fan Club Resource Thread Reynor Fan Club The Flash Fan Club
Media & Entertainment
Movie Discussion! Anime Discussion Thread [Manga] One Piece
Sports
Football (Soccer) Thread TeamLiquid Health and Fitness Initiative For 2023
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Recent Gifted Posts
Blogs
The time I organised my…
AssyrianKing
Why I built Repalyzer (1.1.…
BlueStar
Innovate or Game Over?
TrAiDoS
ShieldBattery on Mac
Kraekkling
Can Bots Beat Pros?? Starcr…
namkraft
James Bond movies ranking - pa…
Topin
StarCraft improvement
iopq
Customize Sidebar...

Website Feedback

Closed Threads



Active: 11076 users

Cyclone Fix Tomorrow - Page 2

Forum Index > SC2 General
Post a Reply
Prev 1 2 3 4 5 Next All
MockHamill
Profile Joined March 2010
Sweden1798 Posts
June 14 2016 06:39 GMT
#21
It is Tuesday on EU, the patch has been applied and the bug is still present.

Why am I not surprised.
Nazara
Profile Blog Joined May 2014
United Kingdom235 Posts
June 14 2016 08:45 GMT
#22
On June 14 2016 15:15 Cascade wrote:
Show nested quote +
On June 14 2016 13:49 ZigguratOfUr wrote:
On June 14 2016 13:36 Cascade wrote:
On June 14 2016 07:56 ZigguratOfUr wrote:
On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug.


Or they took 15 seconds to fix the bug, and then waited for the next patch.

Or people on this forum are very naive about the effort required to fix bugs.


Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe.

It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed.
actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it.
Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug.
but changing a stat is simple.
Penev
Profile Joined October 2012
28536 Posts
June 14 2016 12:07 GMT
#23
Will they fix the bug where the Cyclone isn't the Goliath?

hue
I Protoss winner, could it be?
moon1ight
Profile Joined June 2016
Iceland153 Posts
June 14 2016 13:00 GMT
#24
I wonder if I will see them in my games ?! would be fun to see a new unit after 6 months
wjat
Profile Joined August 2015
385 Posts
June 14 2016 13:14 GMT
#25
I think the community has been pretty chill about the cyclone bug. It's a big, big, big mistake... makes me wonder how they test the game.

Sapphire.lux
Profile Joined July 2010
Romania2620 Posts
June 14 2016 13:40 GMT
#26
With the fix, we might be able to put much more pressure with Cyclones.
Head Coach Park: "They should buff tanks!"
Cascade
Profile Blog Joined March 2006
Australia5405 Posts
June 14 2016 13:49 GMT
#27
On June 14 2016 17:45 Nazara wrote:
Show nested quote +
On June 14 2016 15:15 Cascade wrote:
On June 14 2016 13:49 ZigguratOfUr wrote:
On June 14 2016 13:36 Cascade wrote:
On June 14 2016 07:56 ZigguratOfUr wrote:
On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug.


Or they took 15 seconds to fix the bug, and then waited for the next patch.

Or people on this forum are very naive about the effort required to fix bugs.


Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe.

It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed.
actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it.
Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug.
but changing a stat is simple.

How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.
Quateras
Profile Joined August 2012
Germany867 Posts
June 14 2016 14:25 GMT
#28
On June 14 2016 15:39 MockHamill wrote:
It is Tuesday on EU, the patch has been applied and the bug is still present.

Why am I not surprised.

Because the patch didnt happen yet, Europe gets the patch wednesday morning as always.
"If you don't know where you are going, you can never get lost."
RoomOfMush
Profile Joined March 2015
1296 Posts
June 14 2016 15:17 GMT
#29
On June 14 2016 22:49 Cascade wrote:
Show nested quote +
On June 14 2016 17:45 Nazara wrote:
On June 14 2016 15:15 Cascade wrote:
On June 14 2016 13:49 ZigguratOfUr wrote:
On June 14 2016 13:36 Cascade wrote:
On June 14 2016 07:56 ZigguratOfUr wrote:
On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug.


Or they took 15 seconds to fix the bug, and then waited for the next patch.

Or people on this forum are very naive about the effort required to fix bugs.


Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe.

It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed.
actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it.
Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug.
but changing a stat is simple.

How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.

Because the guy who reported the bug looked it up in the editor and saw the error there. Having worked with the editor myself, I would be very very surprised to hear this took longer than 30 minutes.
404AlphaSquad
Profile Joined October 2011
839 Posts
June 14 2016 16:07 GMT
#30
On June 14 2016 22:49 Cascade wrote:
Show nested quote +
On June 14 2016 17:45 Nazara wrote:
On June 14 2016 15:15 Cascade wrote:
On June 14 2016 13:49 ZigguratOfUr wrote:
On June 14 2016 13:36 Cascade wrote:
On June 14 2016 07:56 ZigguratOfUr wrote:
On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug.


Or they took 15 seconds to fix the bug, and then waited for the next patch.

Or people on this forum are very naive about the effort required to fix bugs.


Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe.

It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed.
actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it.
Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug.
but changing a stat is simple.

How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.

Stop pretending. Everybody who did at least some data editing knows, that this particular bug doesn't take longer than 10 minutes to fix.
aka Kalevi
MockHamill
Profile Joined March 2010
Sweden1798 Posts
June 14 2016 17:34 GMT
#31
The patch has been applied to EU.

We got new emotes but no cyclone fix.

Guess the Cyclone fix will be included in the Christmas update.
FoxDog
Profile Joined October 2007
170 Posts
Last Edited: 2016-06-15 12:13:28
June 14 2016 17:52 GMT
#32
Great job blizzard, i dont know how i feel about how long it took to fix this in the first place though
Remember without fear, there is no courage!
Athenau
Profile Joined March 2015
590 Posts
June 14 2016 18:14 GMT
#33
Calm your tits people. The fix is live in the US.
MockHamill
Profile Joined March 2010
Sweden1798 Posts
June 14 2016 18:50 GMT
#34
Why not in EU? We are 9 hours ahead so the patch should be here first.
ZigguratOfUr
Profile Blog Joined April 2012
Iraq16955 Posts
Last Edited: 2016-06-14 19:34:37
June 14 2016 18:57 GMT
#35
On June 15 2016 03:50 MockHamill wrote:
Why not in EU? We are 9 hours ahead so the patch should be here first.


How exactly do timezones affect when the people at Blizzard decide to deploy the patch to your server?
Elentos
Profile Blog Joined February 2015
55594 Posts
Last Edited: 2016-06-14 19:19:59
June 14 2016 19:15 GMT
#36
On June 15 2016 03:50 MockHamill wrote:
Why not in EU? We are 9 hours ahead so the patch should be here first.

We didn't even have server maintenance yet so I have no idea why you're surprised about anything. EU never gets patches before NA.
Every 60 seconds in Africa, a minute passes.
TheWinks
Profile Joined July 2011
United States572 Posts
June 14 2016 19:45 GMT
#37
The cooldown has been fixed on NA, but the bug where it fails to autocast and decides to move to 5 range and plink away with its main weapon is still present. It would be nice to have a change log.
Cascade
Profile Blog Joined March 2006
Australia5405 Posts
June 15 2016 01:45 GMT
#38
On June 15 2016 00:17 RoomOfMush wrote:
Show nested quote +
On June 14 2016 22:49 Cascade wrote:
On June 14 2016 17:45 Nazara wrote:
On June 14 2016 15:15 Cascade wrote:
On June 14 2016 13:49 ZigguratOfUr wrote:
On June 14 2016 13:36 Cascade wrote:
On June 14 2016 07:56 ZigguratOfUr wrote:
On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug.


Or they took 15 seconds to fix the bug, and then waited for the next patch.

Or people on this forum are very naive about the effort required to fix bugs.


Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe.

It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed.
actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it.
Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug.
but changing a stat is simple.

How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.

Because the guy who reported the bug looked it up in the editor and saw the error there. Having worked with the editor myself, I would be very very surprised to hear this took longer than 30 minutes.

Oh, he actually found the bug? I thought he just patched on top of it, but I didn't read in detail and haven't worked in the editor myself. Thanks.
Loccstana
Profile Blog Joined November 2012
United States833 Posts
June 15 2016 07:32 GMT
#39
They should also fix the bug where it has only 30 hp per supply.
[url]http://i.imgur.com/lw2yN.jpg[/url]
SHODAN
Profile Joined November 2011
United Kingdom1162 Posts
Last Edited: 2016-06-15 09:26:33
June 15 2016 09:25 GMT
#40
can anyone confirm if auto-cast range is still broken? last time I checked, cyclones could manually lock-on from 7 range, while you had to move within 5 range in order to lock-on with auto-cast.
Prev 1 2 3 4 5 Next All
Please log in or register to reply.
Live Events Refresh
Replay Cast
08:00
SC2 Kevin Scrim
LiquipediaDiscussion
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
SortOf 111
StarCraft: Brood War
Bisu 848
Hyuk 142
EffOrt 53
sorry 40
Force[name] 5
Heroes of the Storm
Trikslyr33
Other Games
summit1g11575
Coldzera 1078
JimRising 382
Happy250
Organizations
Other Games
gamesdonequick604
[ Show 11 non-featured ]
StarCraft 2
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• iopq 8
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• lizZardDota2529
League of Legends
• Rush1292
Upcoming Events
Online Event
2h 11m
GSL
3h 41m
Maru vs Dark
Patches Events
6h 11m
OSC
8h 11m
Replay Cast
15h 11m
KCM Race Survival
1d 2h
Ultimate Battle
1d 4h
ZerO vs Bisu
RSL Revival
2 days
BSL
2 days
eOnzErG vs StRyKeR
Cross vs JDConan
RSL Revival
3 days
[ Show More ]
IPSL
3 days
Ret vs ggnore13
nOmaD vs Aether
BSL
3 days
Bonyth vs Doodle
Kyrie vs Jimin
Replay Cast
3 days
WardiTV Weekly
4 days
Kung Fu Cup
5 days
Solar vs Classic
ByuN vs SHIN
PiGosaur Cup
5 days
Liquipedia Results

Completed

Proleague 2026-11-17
Blizzard Classic Cup 2026
HCC Season 3

Ongoing

Acropolis #5
KCM Race Survival 2026 Season 4
International ShieldBattery League
BSL Season 23
IPSL Winter 2026-27
Calamity Cup Div. A Season 8
Underdog Cup 2026 Div 2-3
Stake Ranked Episode 6
BLAST Rivals Fall 2026
IEM Beijing 2026
PGL Masters Bucharest 2026
Stake Ranked Episode 5
1win Private Club #2
Thunderpick World Champ. '26
ESL Pro League Season 24
Stake Ranked Episode 4
1win Private Club #1
Logitech G Play Connect 2026
SL StarSeries Fall 2026
FISSURE Playground #3
BLAST Open Fall 2026

Upcoming

Sector 591
YSL S4
SC4ALL II: Brood War
NBSL 2026 Xiamen LAN
BSL 23: Non-Korean Championship
HSC XXX
Stellar Fest 2: Lunar Cup
StarCraft2 Weekly Open Tournament 2026 Grand Finals
SC4ALL II: StarCraft II
Kung Fu Cup 2026 Grand Finals
RSL Offline Finals
IEM Kraków 2027
PGL Bucharest 2027
BLAST Bounty Winter 2027
PGL Major Singapore 2026
TLPD

1. ByuN
2. TY
3. Dark
4. Solar
5. Stats
6. Nerchio
7. sOs
8. soO
9. INnoVation
10. Elazer
1. Rain
2. Flash
3. EffOrt
4. Last
5. Bisu
6. Soulkey
7. Mini
8. Sharp
Sidebar Settings...

Advertising | Privacy Policy | Terms Of Use | Contact Us

Original banner artwork: Jim Warren
The contents of this webpage are copyright © 2026 TLnet. All Rights Reserved.