• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EST 22:56
CET 04:56
KST 12:56
  • 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 #2312[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 over6Dark 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
Weekly Cups (Nov 9-15): Clem and herO take over SC4ALL: II Indiegogo Campaign Announcement No more SC2 streamers on team liquid? Team Liquid Map Contest #23 StarCraft open world shooter announced at BlizzCon
Tourneys
RSL goes to London! 2026 Offline Finals Nov 21-22 soO & FanTaSy return! SC2 Kevin Scrim 4v4 (Nov 16) Sparkling Tuna Cup - Weekly Open Tournament 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 Shield Battery Server New Patch SC4ALL: II Indiegogo Campaign Announcement Light introduces ShieldBattery on his YouTube Practice Partners (Official)
Tourneys
[BSL23] Ro16 Group B - Saturday 21:00 CET 2v2v2v2 Tournament Stage 2: Players KCM Race Survival 2026 Season 4 SC1 Kevin Scrim hosted by SOOP (Nov 18-19)
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
Nintendo Switch Thread Stormgate/Frost Giant Megathread The PlayStation 5 Warcraft III: The Frozen Throne Free Space RTS Game, optimised f. Phone/Tablet etc
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 Russo-Ukrainian War Thread Artificial Intelligence Thread The Big Programming Thread
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: 19277 users

Battle.net down for a few days - Page 4

Forum Index > SC2 General
Post a Reply
Prev 1 2 3 4 5 6 Next All
ymirheim
Profile Joined April 2010
Sweden300 Posts
Last Edited: 2010-05-24 03:13:03
May 24 2010 03:11 GMT
#61
The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs.

Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard

There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"

The only thing you should feel when you shoot someone... is the recoil
arb
Profile Blog Joined April 2008
Noobville17922 Posts
May 24 2010 03:16 GMT
#62
Aslong as they fix this shit, heres to hoping
Artillery spawned from the forges of Hell
cloudJR
Profile Blog Joined April 2010
United States266 Posts
May 24 2010 03:18 GMT
#63
On May 24 2010 09:06 eXNewB wrote:
Show nested quote +
On May 24 2010 08:54 Gamer0ne wrote:
Nobody is taking the beta seriously anymore



IT'S BETA!!!!! omg what is wrong with you people! seriously the replies in this thread seem like a bunch of babies crying

A) THE GAME IS NOT EVEN OUT YET
B) be happy bliz let you play it in the first place
C) you have not paid a dime yet for this game

so sick of people cussing Blizzard when really you should be thanking them for the opportunity to play "the next big competitive game"

User was warned for this post


False sir. I'm sure a large percentile of us have already paid the full payment to pre-order it such as myself. It could come out in November and that wouldn't bother me. I just want the game to be running 100% before it's released. I say take your time Blizzard and get it right.
All I can hear are thousands of children screaming imbalance.......
NuKedUFirst
Profile Blog Joined March 2010
Canada3139 Posts
May 24 2010 03:19 GMT
#64
Well, my last 20~ games have been problem less *knock on wood*, anyone else?
FrostedMiniWeet wrote: I like winning because it validates all the bloody time I waste playing SC2.
Design
Profile Joined April 2010
17 Posts
May 24 2010 03:22 GMT
#65
On May 24 2010 12:11 ymirheim wrote:
The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs.

Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard

There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"



So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it.
Holcan
Profile Joined April 2010
Canada2593 Posts
May 24 2010 03:26 GMT
#66
"just gonna fix this here, whoops, all well, have fun on wc3 and sc1 for the next couple days xD"
Reference The Inadvertant Joey, Strong talented orchastrasted intelligent character.
ymirheim
Profile Joined April 2010
Sweden300 Posts
Last Edited: 2010-05-24 03:31:27
May 24 2010 03:29 GMT
#67
On May 24 2010 12:22 Design wrote:
Show nested quote +
On May 24 2010 12:11 ymirheim wrote:
The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs.

Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard

There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"



So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it.

If it is a beta test then ofcourse yes, if it was running on internal testing which I bet you it was because issues like the ones we are seeing now are usually the stuff you only notice once you get enough data going through the infrastructure. In a beta test there is no reason whatsoever to hold stuff back because you are on a really tight schedule and on the off chance that shit hits the fan, it was still worth the risk.

Obviously if this was a retail patch then you wouldn't ever put in a patch of any kind on a friday evening unless you got maintenance people working on weekends but this is not the case.
The only thing you should feel when you shoot someone... is the recoil
Design
Profile Joined April 2010
17 Posts
May 24 2010 03:35 GMT
#68
On May 24 2010 12:29 ymirheim wrote:
Show nested quote +
On May 24 2010 12:22 Design wrote:
On May 24 2010 12:11 ymirheim wrote:
The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs.

Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard

There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"



So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it.

If it is a beta test then ofcourse yes, if it was running on internal testing which I bet you it was because issues like the ones we are seeing now are usually the stuff you only notice once you get enough data going through the infrastructure. In a beta test there is no reason whatsoever to hold stuff back because you are on a really tight schedule and on the off chance that shit hits the fan, it was still worth the risk.

Obviously if this was a retail patch then you wouldn't ever put in a patch of any kind on a friday evening unless you got maintenance people working on weekends but this is not the case.


Why does it matter if it is a retail patch or not? It is just bad policy. Not that hard to wait til Monday, when you have people on hand that can go through and find the issues and fix them as fast as possible. Would definitely save the company a lot of the abuse that has been hurled at it these past two days.
OptimoPeach
Profile Joined July 2009
United States137 Posts
Last Edited: 2010-05-24 03:44:11
May 24 2010 03:43 GMT
#69
On May 24 2010 08:49 NuKedUFirst wrote:
Show nested quote +
We have a repair utility in testing internally right now and we're also going to shut the beta down for a few days. With luck, it'll be in the next time the Beta is brought up.

6. Re: Patch issue 05/23/2010 01:45:10 PM PD
Source: http://forums.battle.net/thread.html?topicId=25026564212&sid=5000&pageNo=1#6

Can someone decipher this gibberish for me? Does this mean it's official that the beta will be shut down sometime before the planned date of May 31st, or what? If so, why is this information being posted in some totally random thread instead of being announced? This was posted 7 hours ago?
RageOverdose
Profile Blog Joined December 2009
United States690 Posts
May 24 2010 03:43 GMT
#70
On May 24 2010 09:01 Two_DoWn wrote:
Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?

Or does my analogy not make sense and I should stick to writing.


Unfortunately, in a paper, you can do that.

In software, there are concepts called cohesion and coupling. Coupling is a problem, cohesion is not. Coupling causes certain classes (basically what your software runs with) to be dependent on each other, while cohesion is classes working well with each other, but still independent of each other (meaning that one class can work in other systems).

In designing a large system, you are going to have a lot of information sharing, as software is built upon many classes and interfaces. Where as your words depend on each other, you can just mark out a word and a person will see that, and ignore the mark out and fix the issue in the brain. A computer won't. If you take something away that software looks for, without any logic that tells it to handle that, then it can (probably will) break down. They may not have expected something to happen when they finally implemented all these new features. Perhaps there was a conflict somewhere. Who really knows (I'm sure R1CH has an idea)?




peachsncream
Profile Joined April 2010
United States289 Posts
May 24 2010 03:51 GMT
#71
the games running for me fine if anybody doesnt notice i haven't read most of the posts, but 6 games so far not a single problem/trace of lag
I Micro I Micro - PLZLEAVEDUCK
Niteo
Profile Joined April 2010
United States28 Posts
May 24 2010 03:53 GMT
#72
On May 24 2010 12:43 OptimoPeach wrote:
Show nested quote +
On May 24 2010 08:49 NuKedUFirst wrote:
We have a repair utility in testing internally right now and we're also going to shut the beta down for a few days. With luck, it'll be in the next time the Beta is brought up.

6. Re: Patch issue 05/23/2010 01:45:10 PM PD
Source: http://forums.battle.net/thread.html?topicId=25026564212&sid=5000&pageNo=1#6

Can someone decipher this gibberish for me? Does this mean it's official that the beta will be shut down sometime before the planned date of May 31st, or what? If so, why is this information being posted in some totally random thread instead of being announced? This was posted 7 hours ago?


I actually just went to the battle.net thread (the source) and read the quote in context with the thread it was posted in.

The thread creator was getting an error in SC2 from the latest patch. The repair utility he is talking about is something blizzard has been adding to their new games (like WoW) where you can repair the game without uninstalling/reinstalling.

I don't think the blue post is referring to the battle.net 2.0 lag issues at all. The beta shut down he mentions is the already announced beta phase 1 end (based on the wording). When Phase 2 begins, this repair utility will be included in that latest patch.
ymirheim
Profile Joined April 2010
Sweden300 Posts
May 24 2010 04:10 GMT
#73
On May 24 2010 12:35 Design wrote:
Show nested quote +
On May 24 2010 12:29 ymirheim wrote:
On May 24 2010 12:22 Design wrote:
On May 24 2010 12:11 ymirheim wrote:
The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs.

Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard

There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"



So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it.

If it is a beta test then ofcourse yes, if it was running on internal testing which I bet you it was because issues like the ones we are seeing now are usually the stuff you only notice once you get enough data going through the infrastructure. In a beta test there is no reason whatsoever to hold stuff back because you are on a really tight schedule and on the off chance that shit hits the fan, it was still worth the risk.

Obviously if this was a retail patch then you wouldn't ever put in a patch of any kind on a friday evening unless you got maintenance people working on weekends but this is not the case.


Why does it matter if it is a retail patch or not? It is just bad policy. Not that hard to wait til Monday, when you have people on hand that can go through and find the issues and fix them as fast as possible. Would definitely save the company a lot of the abuse that has been hurled at it these past two days.

It matters greatly, if it is retail then it is a marketing and service issue, if it is a beta then it is an effective testing issue.

Maybe it is not what people want to hear and it has been said before but this is a beta and "public relations" is not a priority. While this does not mean that blizzard are intentionally being asses towards their testers, they obviously value the aid of all the beta testers it also means that they cannot put our comfort before the test. A beta test is an extremely time pressed project under huge constraints both for time and resources. A weekend is a luxury of time that is not available. Since the beta actually works in some cases they are still getting valuable testing time over this weekend regardless of the fact that a majority of people are getting freezing issues, they are both getting lots of vital data on those issues as well as on other aspects of the beta. Even if it is the case that they don't have enough people working right now to sort it, it still means that they can start to fix it instantly on monday, rather than patching on monday, seeing the issues on tuesday and having enough time to figure out what is causing it and then starting to fix it on thursday.
If a project manager of a beta test withheld a patch until monday to not risk causing bugs in the weekend and then a major breakdown happened with that patch after three days had been wasted, that project manager would be loved by the fans but still very much relocated to a different task.

Blizzard is more concerned with getting the game functioning in time than with our priviledge to play the game without issues over the weekend. Obviously though they did not expect these issues, it is always a calculated risk when doing a patch before a maintenance downtime.
The only thing you should feel when you shoot someone... is the recoil
MamiyaOtaru
Profile Blog Joined September 2008
United States1687 Posts
May 24 2010 04:17 GMT
#74
On May 24 2010 11:59 FrogOfWar wrote:
Still weird, being warned for being wrong, or for dissenting and asking people to look at it from another perspective.

NO. And for calling people babies, and for informing us this is a beta. We already know that, and during beta is the time to make complaints known. Would you rather people wait until it's final?
Design
Profile Joined April 2010
17 Posts
Last Edited: 2010-05-24 04:38:39
May 24 2010 04:28 GMT
#75
Whether Blizzard care about it or not, people will form opinions on their company based on how they run this beta. Some of these opinions will be negative, some will be positive. It is still a marketing and service issue, whether or not people have paid to play. I don't understand how waiting two days is going to effect anything substantial that it is not worth it. It's the weekend anyway right? Not many people will be at work to look at the data.

They are actually wasting more time by releasing a patch on Friday. Why is that? Well, let's just hypothesize that it will only take one day to rectify the issues. In the case that they release the patch on Friday, they won't be able to fix it til Monday, which means that it will be Tuesday before a stable version is out. That is 3 days they lost in their beta testing phase. Now if they released the patch Monday, found the issues then and fixed the issues by midday Tuesday, that means they only lost 1 day in their beta testing phase. Also, it has the added benefit of not annoying those people who are helping test the game for them. The risk far outweighs any potential benefits.

Just want to add, I do believe in most circumstances it would be fine to release a patch on Friday. But that is only if that patch didn't include modification to the network architecture that the game relies on to run.
stroggos
Profile Joined February 2009
New Zealand1543 Posts
May 24 2010 04:30 GMT
#76
may 24th, will now be known as "fffffuuuuuuu" day.
hi
Mojawi)SoJu
Profile Joined April 2010
Korea (South)259 Posts
May 24 2010 04:32 GMT
#77
The 31th the beta will be closed right?
#1 김택용 팬 | #1 화승 오즈 프로게임단 팬 | 스타2 하자! | 나를 찢어갈겨 이 씨발놈아 왜 나를 미치게 만들어 니가 뭘 아는데?
myopia
Profile Blog Joined June 2009
United States2928 Posts
May 24 2010 04:37 GMT
#78
I hate to imagine the hours per week the Blizzard staff will be pulling from now until the end of July.
it's my first day
Ighox
Profile Joined July 2009
Norway580 Posts
May 24 2010 04:50 GMT
#79
On May 24 2010 12:53 Niteo wrote:


I don't think the blue post is referring to the battle.net 2.0 lag issues at all. The beta shut down he mentions is the already announced beta phase 1 end (based on the wording). When Phase 2 begins, this repair utility will be included in that latest patch.

That's exactly what I thought when reading it as well, with luck the repair utility will be added by the time bnet gets back up after the shutdown on the 31st.
And I really doubt they would take down the beta even earlier because the new patch would also need some public testing before the beta shuts down.
cowkid
Profile Blog Joined April 2010
United States28 Posts
May 24 2010 04:55 GMT
#80
I have a theory as too why Bnet was having the problems, i think its beacuse as soon as they let maps be published the server(s) became to flooded, to many people, to many maps being uploaded etc... i could be wrong, but i really do hope it is fixed realtively soon
"The game isn't imbalanced, it is fundamentally flawed."
Prev 1 2 3 4 5 6 Next All
Please log in or register to reply.
Live Events Refresh
PSISTORM Gaming Misc
09:00
FSL s12 week3: POG vs ST
Liquipedia
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
RuFF_SC2 197
PiLiPiLi 12
StarCraft: Brood War
sOs 34
Icarus 7
League of Legends
JimRising 635
Counter-Strike
taco 464
Other Games
summit1g9005
gofns5632
PiGStarcraft251
Maynarde114
Livibee23
Models3
Organizations
Other Games
gamesdonequick1154
[ Show 12 non-featured ]
StarCraft 2
• davetesta19
• practicex 3
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• RayReign 25
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
League of Legends
• Lourlo377
Upcoming Events
RSL Revival
7h 5m
AI Arena Tournament
13h 5m
BSL
16h 5m
eOnzErG vs StRyKeR
Cross vs JDConan
RSL Revival
1d 8h
OSC
1d 9h
IPSL
1d 13h
Ret vs ggnore13
nOmaD vs Aether
BSL
1d 16h
Bonyth vs Doodle
Kyrie vs Jimin
Replay Cast
1d 19h
WardiTV Weekly
2 days
Kung Fu Cup
3 days
Solar vs Classic
ByuN vs SHIN
[ Show More ]
PiGosaur Cup
3 days
The PondCast
5 days
KCM Race Survival
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
RSL Offline Finals
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

Upcoming

Sector 591
YSL S4
SC4ALL II: Brood War
CSL 2026 Winter (S23)
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
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.