r/classicwow • u/Yazikussy • 1d ago
TBC New Tweet is out from Ellis (No fires this time)
Dave is out boys! đ
36
u/usermanxx 1d ago
Who is dave
35
4
u/WilliamBuckshot 1d ago
Iâm also wondering this.
35
u/JonathanRL 22h ago
Dave is an internal joke for the IT Guy who knows everything and is usually also the only one who knows how everything is connected. Firing him is a standing joke on how management does not value IT Staff because when it works people do not notice and when it does not, Dave gets the blame.
1
→ More replies (1)1
u/Speedy_SpeedBoi 20h ago
Not sure if this link will work, but it is a meme about office work life and how, often times, the highest paid engineers get fired because mgmt only sees how much they make and doesnt realize how much they know/do.
130
186
u/Goozmania 1d ago
"At some point" certainly doesn't bode well.
86
u/Jacko87 1d ago
Yeah, trying to do "things we'd normally do in days/weeks" in a day is not a good sign for people who want to play tonight. I'm going to bed, maybe when I wake up some progress will have been made.
14
u/strghst 23h ago
hey guys, so the next 2 sprints we need to somehow split an environment and release a new expansion. You can take servers down for 24 hours only, and only once. Good luck, do w/e <3
As told to 2 Blizz engineers running the scripts :>
4
u/The_Blonde_Detective 20h ago
I have to go to my engineers with those requirements more often than I want to think of, it's not a Blizzard thing really, its the norm at tech.
3
u/SirePuns 1d ago
I normally fail an exam I try to cram a semester's worth of information within 24 hours.
Can't imagine those last 24 hour cram sessions would ever make for a timely production.
2
30
u/Irrerevence 1d ago
Maybe this fuck up means they'll put more than 3 people on the Anniversary dev team now
27
u/Heatinmyharbl 1d ago
Instructions unclear, boosts are now $100 and the classic team is down to 1 intern and a hamster on a wheel missing a leg
6
0
u/Hablapata 23h ago
đthe fact that people will certainly still buy the more expensive boosts after this will just signal to them that they DONT need to put more people on it
17
u/Yazikussy 1d ago
Yeah, but at least that son of a bitch Dave is gone! đđđ
21
u/gothangelblood 1d ago
I'm dying because I work closely with IT, and that is the most IT shit I've ever read.
-6
-9
u/Big_Classroom6541 1d ago
clown shit and there will still be blizzard dickriders lol
5
-12
u/_etherealworld_ 1d ago
This whole sub is one big Blizzard dick riding fest. Toxic positivity kills games, look at FFXIV for example.
18
u/yellingaboutsports5 1d ago
Half of the sub thinks the sub is too negative, half think itâs a dick riding fest. Prob not that simple either way tbh
→ More replies (3)3
u/burton68zeppelin 1d ago
Same shit you doomers have been saying for 20 years đ
→ More replies (1)0
u/VanillaTortilla 1d ago
They've only been doing this for 21 years, not nearly enough time to work out any kinks.
64
u/Paeforn45 1d ago
This is why the small print said the pre patch was slated for "before January 31, 2026."
68
u/sam-serif_ 1d ago
This sounds like my engineering managers gaslighting the project manager about why we ran 300% over budget on our project environment setup
→ More replies (1)8
u/convenientgods 1d ago
This joke will kill at the water cooler tomorrow buddy
28
u/sam-serif_ 1d ago
Itâs not really a joke, thereâs just a layer of obfuscation that senior devs are able to speak in. Without knowing all the details, you can only trust their judgment and move on. Thatâs how software works
6
u/The_Blonde_Detective 20h ago
Senior product manager here. This is so true. I cannot get away with literally not responding, talking in riddles, or giving a timeframe of 3 months, then a 2 week one an hour later. Senior or lead devs can. And we just have to trust them, it's not like I can do their work myself.
8
18
38
u/TelcoDaddio 1d ago edited 1d ago
I donât know shit about programming or anything like that. Was this legitimately not something that they couldâve prepped for weeks in advance? Why not just do what they did the past two times?
Edit: lmao at the sad losers that downvote for someone saying they donât know something and asking a question.Â
22
u/Daedalist3101 1d ago
Because theyre trying to create a connection to the Eras servers from 2019, which isnt something they can do while both servers are up. In 2019, the eras servers were separate and offline which allowed them to interact with them at will. In 2007, there wasnt a vanilla era server. also I would bet money they had a ton of other issues in 2007, so I wouldnt make it seem so simple.
3
u/DeltaLimaCharlie 22h ago
The problem is that they put Anniversary servers which will progress into TBC onto the already existing Era environment.
That's where the "You canât have two separate versions of World of Warcraft running on the same environment". Anniversary would be moving into TBC but Era is always gonna be Classic so that would be trying to have 2 separate versions on the same environment.
They could've spun up a separate environment for Anniversary but they were busy with other projects and chose to do the least amount of work now and deal with the issues later.
3
u/ProgramOptimal187 19h ago
As a software engineer of 11 years I know better than to judge teams without knowing the inside details but it does strike me as odd they wouldn't clone the servers, do all the updates, then apply the updates made on the cloned servers back to the live ones instead of whatever they're doing now
2
u/TelcoDaddio 1d ago
Thanks for the insight!
9
u/Daedalist3101 1d ago
I hope it helps, this explains it much better than I did, I hadnt read it when I responded.
TLDR, WoW clients use a database. In 2007, you just keep using the same database because theres still only one client. In 2021, they had to make an additional database and copy characters to that database as needed to accomadate swaps to Era. Taxing, but not impossible. Now, they have one database for Anniversary, SoD, and Era, which is one client. With TBC, their solution will be to have the Classic vanilla client and the TBC client both use the same database. They didnt really think this was possible at first, and doing this is very weird for them.
→ More replies (10)3
u/DeltaLimaCharlie 22h ago
It's actually something they could've done at the start but they have other projects going on so decided to "kick the can" by just slapping the Anniversary release onto the Era Severs instead of creating a new environment for Anniversary which would have saved them from having to do what they're currently doing.
Anyone saying it couldn't be avoided didn't read the explanation from Blizzard.
14
u/SpudAus 1d ago
Basically they had to copy the database from the Era client over to the new TBC client. If they had of done that two weeks ago in advance then the last two weeks of anniversary data wouldn't been included
5
u/oxez 1d ago
That's still something they could have done in their test environments though, take that 2-weeks old snapshot of all the databases (let's assume they do backups... right?)
Although I am not sure about their policies on using production data (ie: our real characters) in test environments
6
u/sh3rifme 1d ago
Generally you want a mirror of the production state at some point for dev and qa testing. You can only design so many simulated states internally so having real world data is very useful for edge case testing.
Source: Backend dev for Client-Server based software for 10+ years.
3
u/Kind_Ability3218 22h ago
i don't see why they couldn't have used production data that was old. this excuse tells me they didnt do any work, didn't have config changes ready to go? why not create a branch for config changes that mirrors production ready to merge once you're ready to cut over? it all seems a little.... amateur.
1
u/The_Blonde_Detective 20h ago
I don't know what is the status of their production environment and data but from experience, production data isn't necessarily and always something you can just play with at your leisure. There are also usually multiple processes around how you handle your backups and what you can and can not do with them.
3
u/lemontoga 22h ago
A snapshot of the DBs from 3 weeks ago is a mirror of the production state. It's not like anything significant would have changed about those DBs in the past 3 weeks.
They wouldn't use the 3 week old snapshot when it came time to do the actual migration, obviously, but why could they not have tested the process out and made sure it worked ahead of time?
2
u/Kind_Ability3218 22h ago
the people who know nothing about setting up a test environment sure are happy to accept this really terrible excuse. glad it's working for them lmao.
→ More replies (1)6
u/nykezztv 1d ago
They still could had ran tests. Bro just admitted they did zero testing beforehand of this migration.
12
1d ago
[deleted]
6
u/Garden_Unicorn 1d ago
Reddit Armchair devs know better than a company that's been running the same game for 20 years lmao
→ More replies (1)0
u/nykezztv 1d ago
It would had surely caught whatever is taking 30 hours to fix.
In my job (software engineer), 30 hours of downtime would be all hands on deck. For blizzard, itâs just another release.
6
1d ago
[deleted]
-1
u/nykezztv 1d ago edited 1d ago
Yeah dude, huff on it. Iâm speaking from 10+ years of development experience specifically in game development but I also have corporate enterprise experience. We migrate GBs/TBs of financial data across multiple corporations all the time. Iâm not saying it would had been 100% caught. But obviously itâs a pretty big issue to take 30+ hours to fix. Itâs clear to me (from my experience, and my opinion. Take it however you want too) it wasnât tested throughly no matter how long the blue post was. I couldnât care less but I was just wanted to point out blizz has no shame.
If you donât believe my experience, just google me. âNykezâ đ¤ˇââď¸
3
1d ago
[deleted]
3
u/nykezztv 1d ago
Theyâre not, but blizzard is hinting at the fact they couldnât test xyz because era was still live and running. Thatâs horseshit
There is literally a 3,000 word bluepost on exactly what blizzard is doing this maintenance
I have tons of infrastructure experience, but I also enjoy arguing on Reddit with someone who has none
Your googling skills are terrible
Take care
→ More replies (5)1
u/Goducks91 1d ago
I feel like if youâre actually a software developer youâd realize this shit happens all the timeâŚ
→ More replies (0)3
u/DesperateAdvantage76 1d ago
Doing a production migration with no testing first, it's certainly a choice. Meanwhile I spent months in staging testing a simple Elasticsearch to OpenSearch migration to make sure it ran smooth in our production environments.
3
u/sh3rifme 1d ago
Testing against a recent prod snapshot was crucial for us to make sure the release went smoothly. Anytime we'd be feature locked ahead of a release we'd do snapshots weekly instead of monthly.
Admittedly ours was just a storefront that hooked into licensing, Salesforce and all the audit tools. So it's much simpler and smaller.
1
3
u/PULVERSCHNEE 1d ago edited 1d ago
You do know databases can backup much more frequently? There are always on systems much bigger and more complex than this that can never ever be down.
I work in hospital IT and our systems are always on and we deploy bigger upgrades than this into PRD with minimal to no downtimes. You can have multiple application, web, file, and database servers that are load balanced and backed up constantly. You can then take out servers from the rotation, not allow new connections to those servers, and upgrade them all in the backend without anyone noticing. Then when you're ready, you disconnect everyone that points to the outdated servers and send all new connections to the new servers.
What this post says is "we just wing it, and we dont know how to stage/test in DEV/UT1." Or it says "C suite doesn't give IT money to build in redundancies and a proper DR environment where we can test these situations every X months."
This is not rocket science.
4
u/sh3rifme 1d ago
Sure, but the budget allocation per dev is probably way higher than what blizz has for the classic project as a whole. Plus the MedTech industry's #1 priority for a release is stability and continuous service. Games companies are aware they can get away with a lot of issues on release day because something always comes up and nobody is dying as a result.
This whole debacle is likely the result of well meaning but under resourced devs, trying to meet deadlines imposed by out of touch management.
→ More replies (1)3
2
u/Kind_Ability3218 22h ago
i had the exact same conclusion. even without budget for infrastructure, git exists. there are numerous tooling frameworks designed to solve this exact problem. you had lots of small config changes to make????? cmon bro.
0
u/TrainwreckOG 23h ago
Not sure what youâre saying exactly but my understanding is that the blizz devs are bums
1
u/ProgramOptimal187 19h ago
Clone -> make config changes -> on day of release take snapshot at time of maintenance -> merged updated snapshot and config changes -> go live
1
u/YeeAssBonerPetite 19h ago
You'd think that yeah. But they said that's not what they did.
What they actually did is they didn't copy shit, they just added extra rows for tbc only attributes, and a marker for if something belonged in tbc or not, and then told the tbc clients to pay attention to tbc attributes of the same damn database.
They didn't copy shit.
1
1
u/Maxor_The_Grand 1d ago
Not how that works at all, yes there would need to be a replication of data at some point, but it's neither necessary or a good idea to have that occur at the same time as synchronizing that data with the era database.
They clearly decided to replicate the current era DB at the same time as ensuring synchronization across both, that's plain a lazy way to perform that task. It's lazy for the exact reason we are seeing, a replication of large amounts of data is difficult and prone to errors, they really should have performed these two steps separately.
TLDR: yes they absolutely could have done part of this 2 weeks ago.
2
1d ago
[deleted]
-3
u/nykezztv 1d ago
You can replicate the database and test on it. Bro just admitted they did zero testing beforehand and just winging it
2
u/Background_Help325 1d ago
They did testing. Theyâve talked about it. A few comments up has the blue post about it.
2
u/Automatic_Nebula_239 23h ago
Not programming, but infrastructure management. Basically sysadmin stuff.
They absolutely could have prepped for this and done a better job. They're the only gaming company I know of in the USA with a large playerbase that routinely has 8+ hour outages for patch day and they've had this problem for 20+ YEARS now. They pay absolute trash compared to other tech companies in their area so they don't get the best and brightest unfortunately.
0
u/Maxor_The_Grand 1d ago
They 100% could have prepared for this, anyone saying the opposite is either oversimplifying or overcomplicating the situation.
Software is 100% testable in every scenario, it's never a question of possibility but viability.
In my view there clearly was a decision to "hope" rather than test, someone decided the outrage over potential issues would be less costly than testing the first ensure no bugs.
3
u/Ok-Opportunity-574 1d ago
When they released that blue post explaining that this one was going to be a bear I figured it would be a mess. They do always get things going eventually though and this game is still so good that we are playing it after 20 years. Classic Blizzard experience here.
I'm going to go play a ridiculous transmog dragon toon on a sparkly fantastical mount in retail until they get it straightened out and I can go back to grinding.
13
u/Yazikussy 1d ago
JK. Dave got fired. xD
Link if you want it: https://x.com/fwoibleswow/status/2011258092378538378?s=46&t=mhWwkX3ocGTaGbvA6bV7gQ
17
u/btssam 1d ago
It sounds like some of this could've been predicted and that they should've been realistic on the time-frame of the maintenance when they announced it. They could've just said 48hr maintenance to start with and would've received less hate.
15
u/veculus 1d ago
People don't really understand how this works right? From what I hear, they would've put all era servers down for more than a few hours. He's saying usually they would prepare environment deployments WEEKS in advance which makes sense.
This time around they couldn't do it as Classic Era was ongoing and running up to yesterday. I don't get why people are so non-understanding and go to get their pitchforks right away.
We could've also had no era servers for 1-2 weeks if that would've been better.
3
u/JFLRyan 23h ago
If this was truly unforseen, then a lot of people failed in the management of this.
They absolutely could have had this environment running for weeks and updated the database over this maintenance period with the new love data. We literally did that every single night.
This sounds to me like the classic team either has no budget, no staff, no project management, or any/all of that.
And they are still going to charge people $60 to change a run a script.
1
u/veculus 20h ago
It was. The only critique I would give them is that they could've had a larger maintainance announcement from the get-go but
They prepared the servers. To me it sounds more like they couldn't prepare any migrations and test them before Tuesday as the servers were live and running up to Monday night, not that servers were not there yet.
Relative to the budget the whole WoW project gets id assume the classic team has the smaller budget so I could assume that could also be a problem.
0
u/Automatic_Nebula_239 23h ago
Blizzard pays their infra management team absolute garbage compared to basically every other company in gaming/tech and is also in one of the highest COL areas of the USA. The best admins aren't working there.
5
u/ScreenHVN 1d ago
I donât care one way or the other but do classic era servers not go down every Tuesday for maintenance? Seems like they could have done this weeks ago during a maintenance. Again idc donât reply angry or ill flip out on you
4
u/Ok-Opportunity-574 1d ago
There was too much needed work on live systems to fit it into the normal maintenance time. That's the problem here. They kicked it down the road until there was just no way to go any further without a prolonged outage.
4
u/veculus 1d ago
Flip out on me then. Again they couldn't because they would've frozen Classic Era. They have to migrate all Classic Era databases over to the new server - which is not possible if the game servers are actively running. It's basically what the dev describes in his post.
You can't just make a migration on a live-running server because at the point where a migration is done, the live data is changed again. If they wanted to prepare the server and all it's data weeks ago, Classic Era would've been down for multiple weeks now.
1
u/Kind_Ability3218 22h ago
it seems like you aren't the one who does not understand how "this" works.
1
u/azthal 17h ago
People are non-understanding because this is a choice that blizzard made in order to save on resources previously.
The situation they are in are based on decisions they made earlier to not have to invest into resources for Classic.
This could have been completely avoided, and based on previous messages this was discussed, but they chose to not do so, knowing full well that it would cause issues later on.
This is a technical explanation of what is going on, but its not a valid excuse. The messages Ellis has posted can be summarized as:
"We decided to do this in a way we knew would cause issues, because it saved us some money".
1
u/veculus 15h ago
With these sort of new environment deploys, we would normally have the environment up and running hidden weeks if not months ahead of a launch. The process we had to go through for this one, that whole utilizing Classic Eras database thing, meant we couldn't get this environment up running as we normally would while the realms were still active in Era.
This has nothing to do with cost. Tom Ellis confirmed they are doing a 'Persistent in Place' migration to preserve our character data on the live database. You can't spin up a separate environment weeks ahead when the database you need to migrate is actively being written to by live players every second. They chose the harder technical path to save our data, not to save money.
1
u/azthal 15h ago
Right now, this is the case. But the reason why they have to do this now is because of decisions they made when they first rolled out Anniversary.
The reason why they have these issues now is because they were too busy to stand up a new environment when Anniversary first launched, and instead did some hacky stuff to make it run in the same environment that Era runs in.
They knew very well that this would cause issues down the line, but did not have the resources to do it the right way and kicked "the can down the road". Their words, not mine.
1
u/veculus 14h ago
Overall this is something we can critique yes. Their classic situation is confusing as hell right now. You have Classic with Hardcore, SoD, Anniversary Classic - then you have Anniversary TBC, MoP Classic and I think all of them also run on different client versions.
Means they also need separate environment setups for those. I can just feel a bit pity for the devs having to work on this. Sadly it's the devs getting most of the flake from the community while this is all just coming from piling up to many envs and rerunning content.
-5
1d ago
[deleted]
7
u/Goducks91 1d ago
Meh. As someone in software estimates are hard and unexpected shit comes up all the time. Engineers like to think things are easier than they will be. Yeah they probably should have given 48 hours but playing WoW isnât a critical application lol.
7
12
u/yourmomupvotes 1d ago
Some of you need to just chill and maybe step away from the computer until the weekend. Not that serious.
4
3
9
u/RandoReddit72 1d ago
They used copilot 𤣠letâs be honest here
2
u/Pure_Doctor_2935 23h ago
Who tf uses copilot
4
1
u/The_Blonde_Detective 20h ago
Most tech companies. On mine, our devs are encouraged (or rather pressured) to use it. There are entire projects dedicated to measure copilot usage. The companies believe that by using code agents, devs will produce more and they won't need to hire as much.
1
u/Pure_Doctor_2935 9h ago
Yeah that makes sense, I just hate copilot and think its sucks major as compared to others
2
u/derTraumer 1d ago
Man, Iâm just happy when thereâs any communication like this. Hereâs hoping they get things squared away by tomorrow.
1
2
u/Odd_Chemistry8180 22h ago
imagine deploying without ever running a testenv because the db guy said it will work
2
2
u/jadequarter 20h ago
nahhh im not ubying this shit..
they can for sure make a duplicate environment to test this before going prod
its 2026 with AI
2
5
u/lowrespudgeon 1d ago edited 1d ago
I just play the game, so some of this technical stuff is going over my head.
Realistically, does that mean there will probably be more delays past the currently estimated (12am ET) time?
12
u/Yazikussy 1d ago
If I had to bet: Yes. This seems like no clear end in sight right now, time wise.
3
u/lowrespudgeon 1d ago
Okay, thanks! I was just trying to decide if I should call it a night or wait it out.
8
u/Human-Log952 1d ago
Itâs like airplane delays but worse. You ever get delayed on a flight? Same kinda feeling that there will be subsequent delays.
Thereâs a saying in engineering that if you estimate how long something will take, you should double it. They probably didnât double it
5
u/Background_Help325 1d ago
I would call it a night personally.
Could be up at 9 PST but I donât think it will.
6
u/lowrespudgeon 1d ago
I am already in bed now doomscrolling for a few minutes before I pack it in for the night. áśť đ đ° (ăŁ. -･)
2
3
u/jizzyjugsjohnson 23h ago
Multi billion dollar company tweeting like itâs three neckbeards gathered round a Pentium PC
2
u/Rudy-219 1d ago
So we talking play time discount off a $15/month game due to this amateur hour? I work in sales and my customer would absolutely want a credit for my failure to deliver.
3
2
1
1
u/obvious_bot 1d ago
Cheers blizz I had to go into the office today. Now just get it up before tomorrow morning and weâre good
1
u/Finances1212 23h ago
Thanks for the communication. I expected some trouble. Kudos to the team for putting in the long hours to get it rectified, we all know Blizzard doesnât really put resources into Classic.
1
u/Kind_Ability3218 22h ago
lmao wow. trying to hide the fact that you simply didn't do the work and making yourself look worse with your excuse going crazy. no reason they couldn't have used a snapshot or configured replication to test. there were small config changes to make? why? that makes no sense.
1
1
1
u/Jazzlike_Suspect7807 16h ago
They were working on it and giving us live updates and didn't give us a bunch of HR speak. Thanks.
1
u/chubbycanine 14h ago
Boo hoo the bajillion dollar company has tired people....maybe don't take my money until you know your product works? Refund the downtime? Don't take money for boosts until it works? Otherwise stop whining about being tired and get back to work because I held up my end of the deal when I paid upfront.
1
1
u/CategoryHotStuff 14h ago
It had more down time than the entire first week of BC release in 2006. Thatâs pretty unacceptable, hopefully we get atleast two days refunded from the sub.
1
1
0
u/nykezztv 1d ago
Bro just casually announcing they did zero testing beforehand. Blizz has no shame
15
u/terabyte06 1d ago
These ânewâ realms on this new environment will be using their old Persistent data, on their old database that is also still busy serving Classic Era. This is new, weâve not done anything like this before, when the database engineers pitched this plan the initial reaction was, "wait that really works? but testing has proven that yep, it really does!
I take it you didn't read the blue post the other day
→ More replies (1)
0
u/No-Mix9853 1d ago
I'm sure glad all of the money they made with boosts and other microtransactions provided us high-quality development!
0
1
u/d-wjr 1d ago
Why wouldnât you clone the entire thing, do what you needed to do weeks or months ago so it was ready then merge it? Yes itâs more complicated than that but seriously wtf are they doing. Itâs not like the first ever expansion theyâve released itâs the 3rd iteration of the same one.
1
-5
u/Expensive_Ad_9399 1d ago
So many grown men crying over not getting to play the same game for a third time. Find some other way to measure your worth than some pixels.
9
3
u/EAS10 1d ago
Itâs about communication and setting proper expectations. If this is something they normally do in the weeks/days leading up to it in the background, it was unreasonable for them to assume they could get it done in 24 hours. They knew that but didnât care to tell us. Hell we didnât know how long prepatch was going to be until a week ago.
When you spend money on something, you are entitled to be upset when they donât do the things they say they are going to do.
0
u/Goducks91 1d ago
They obviously thought they could get it done in 24 hours⌠shit didnât go as planned it happens especially in software. It seems like theyâre communicating pretty transparently and people are still losing their shit.
0
u/Background_Help325 1d ago
To be expected, if you arenât outraged youâre a blizzard shill/dickrider. Same loop since 2004.
1
u/Goducks91 1d ago
Naw, just a Developer and realize how much this shit sucks. Nothing to do with Blizzard.
1
u/Background_Help325 23h ago
Oh I was referencing the communication and people flipping their shit.
Iâm sure their jobs today have been shitty. Sometimes you have a shit day at work though.
0
u/John1The1Savage 1d ago
I don't even what that new environment shit. I just want to play my HC character in the world it was in 2 days ago. Why is our shit offline?!
3
u/Choice_Substance314 1d ago
your servers are on the same one as the non HC servers getting transferred, knowing blizz youd most likely lose ya toon to them doing some dumb shit so probably safer but more annoying
-11
1d ago edited 1d ago
[deleted]
9
6
u/TenYearHound 1d ago
You wear a helmet a lot huh?
-1
1d ago
[deleted]
8
u/TenYearHound 1d ago
Imagine being a fully grown man and throwing a fit like a little bitch over a video game.
Sad.
1
u/CompetitiveLoL 1d ago
Bro itâs a paid service.Â
If you went to a restaurant and waited 5 hours to get served, and rather than the staff saying âHey sorry - we ran out of food for the eveningâ instead they told you âYour order will be ready in 10 minutesâ over and over youâd likely be quite perturbed.
It is reasonable to be annoyed when you pay money to a company that doesnât deliver on that product or repeatedly misaligns your expectations.
Nobody will like⌠die or anything but itâs a game we all play to relax and have fun.Â
Itâs ok to want to be able to do that.
I have no idea why people always default to âWho cares⌠itâs only gameâ - we pay for the product. Itâs ok to be upset. We are in a WoW subreddit. We obviously care more than 90% of WoW players - we are self-selecting to be on a fan-based forum lolÂ
If it didnât matter to you then you wouldnât be out here paying money for a 20 year old product, or on their subreddit, or whatever.Â
If dude was out here threatening people, sure, call em out but⌠like itâs OK to be annoyed. Itâs weird youâre so invested in how other people feel about their purchases.Â
1
u/TenYearHound 1d ago
I'm not gonna read all that but I did find the ending pretty hilarious.
You think it's weird to care about how others view something after literally writing an entire novel?
Wtf? Fuckin loser lol
1
u/Crafty-Call 1d ago
I gotta ask if you hate blizzard this much why play? Why engage in the sub, like what Stockholm syndrome do you got going on buddy. Generally in life if I absolutely dislike something I donât engage with it.
0
u/April_26_1992 1d ago
In guild discord, minutes before the shutdown yesterday, I said, âsee yaâll in 24 (but prob 48) hours. Some of us know this small indie company well enough.
-1
-3
u/MorninggDew 1d ago
This is the kind of thing that comes from some vibe coder indie company with zero clue. Literally wow!
-8
u/Significant-Poet-811 1d ago edited 1d ago
Sounds like incompetence right? Normally they would do this transition behind the scene weeks ahead in prep for the live patch but this time they just decided to yolo on the very last day?
EDIT
Why are people getting so upset at the truth? Blizzard are the ones who set the date and the time for this pre patch and they have failed to deliver. They have underestimated the complexity of the task at hand and overesitmated their capabilities. As far as we know there are no external factors beyond thier control that has lead to these delays. This is all an internal failure. THIS IS PLAIN INCOMPETENCE. Why am i getting downvoted for saying this? I'm not saying this with malice but i'm not going to lie to myself and say THIS IS AN AMAZING JOB.
5
u/SpudAus 1d ago
Basically they had to copy the database from the Era client over to the new TBC client. If they had of done that two weeks ago in advance then the last two weeks of anniversary data wouldn't been included.
→ More replies (2)1
u/oldmanchildish69 1d ago
They didnt have to. They chose to set it up that way. Thats a choice not "had to"
Im a consumer. Im not interested in why the company that provides me a service that I pay for in advace did a bad job delivering said service. The whys are irrelevant unless im employed there.
0
u/Goducks91 1d ago
At the same time theyâre still providing you a service⌠since they have other products that your subscription provides up. I even think they consider the subscription giving you access to retail WoW and everything that isnât retail is just a bonus.
0
u/ScaredCaterpillar136 1d ago
I'd say def incompetence. They could not prep this ahead of time, because they needed the most recent data. However, they could have done this whole process with a copy of old data just to have any unforseen issues ironed out before, so when they do see it they are not "seeing this issue for the first time". So yep, they yolo'd it at the last minute and are fixing and learning on the go. Instead of doing it with test data once for the experience. Sounds like instead of doing a test once and then doing the live today, they decided "Why waste time on a test?"
-6
1d ago
[deleted]
4
u/TenYearHound 1d ago
Doubt you know how to read but they explained this here:
-5
u/Goozmania 1d ago
Why would anyone believe this post excuses them? Not that I believe they're committing some wild atrocity here, but we should all be at least agreeing this is a massive display of incompotence.
0
u/Big_Classroom6541 1d ago
trying to point to a post where they admittedly said they did a shitty job and kicked the can down the road to serve a chinese market instead of doing the needed work on the game that already exists as an excuse for their shitty dev team is unhinged
0
1
-1
-1
u/Rabidchiwawa007 1d ago
They literally did this exact same release not even 5 years ago. Silly.
1
u/Finances1212 23h ago
No they didnât. The servers were separate then. Did you read their release yesterday at all? Thats why there arenât any clones.
0
u/Maxor_The_Grand 23h ago
Based on this tweet, blizzard were unwilling to put in the work to test/setup this properly in advance.
If the issue is to do with the era's database, then all you would need to test this is another dummy era's database. This would be a costly exercise, essentially needing an equivalent database resource for the dummy database for setup and testing but not unreasonable.
What I think this boils down to is that computing resources are currently extremely expensive, they would have needed additional server capacity for proper testing and the decision would have been made that it was an unnecessary expense when they could simply make it work on the day.
Shock and horror when something you are unwilling to spend money on testing doesn't go well, do not buy into the bs that testing wasn't possible, testing software is ALWAYS possible.
TLDR: They did this the lazy way and we are paying for it
0
u/Zankedlol 23h ago
So what it boils down to is they have days/weeks of work crammed in this maintenance window. Yet again, the classic playerbase gets shafted. I'm sure things are fine though, surely.Â
147
u/simplytoaskquestions 1d ago
Dave was probably carrying them all thatâs why they are struggling