who alpha tested the employees ?
1 Like
Those content stages are purely omitted content. They are not using different patch versions as they go. They are not using a mix of 2+ patches. They are taking 1.12 patch and disabling access to content.
That’s not Franken anything.
Also, patch progression hardly requires a beta. Specially when it’s something like disabling Dire Maul portals.
What is not happening is franken client or franken server. Unless you have some major drive to beta shader changes so Classic lighting is correct. I support launching the game and tune that while the game is live.
Dude you’re just being picky about my way of describing it. I’m not going to go back and forth with you just because you want to be picky.
The “Frankenstein” part is the fact that we aren’t getting true Vanilla, but a modified version.
I’m leaving it at that.
I don’t have a care in the world about what you call it. That was some poster(s) above.
What I am pointing out is the very clear fact that the server and client are not being hit with some major overhaul. As they said in the dev watercooler, that is why they went with the modern code and not the vanilla code.
How they roll out the database changes is not what I was pointing out in the first place.
Your response indicates you do care, or you wouldn’t have said anything about it.
I understand that you have your own way of thinking about it.
However, when I think of only being able to do Molten Core at the beginning but with 1.12 itemization and game balance, it’s not Vanilla to me, it’s a Frankenstein-esque resurrection of the game.
I do not care that you and some other person are unreasonably offended by my use of that term - this is my way of describing it and it’s not going to change.
Also you keep blabbing about the client but it seems like you aren’t really keeping up with recent developments.
I framed my response that way based on illustrating the difference between content progression and piecemealing server/client code.
Does 1.12 itemization and talents in MC require a beta? I might be going out on a limb here but I think it’s safe to safe, Blizzard is OK with 1.12 changes in MC at launch.
Waiting for a blue post about itemizations to see if I should change that position. Not expecting one though.
Just like everyone else here is. Only difference is I am not applying pserver terminology to the process and confusing the mix.
Main thing to take away from this. Beta for database changes is very minor on the list compared to server and client changes.
I mean they will decide if they need to do a beta or not. What’s your actual question here?
Okay so it’s “private server” terminology that is bothering you. I get it now. But let me ask you this: is it true Vanilla we’re getting?
Is it exactly like Vanilla or is it different?
There’s only one correct answer to that.
We knew we were not getting vanilla from day one.
Only thing I care about is delaying a launch due to some people wanting to beta test and see if oddball things like demon summoning is the way they remember it .
If health regens are wrong, or crit rates are too high, some ability does(n’t) stack, the name of a razor blade axe is not the original. All can be addressed once the game is live.
If we Blizzard has crashes or performance spikes they need to hunt down. I expect a beta.
Franken - that’s just a label to describe where changes happen. Change isn’t in question.
1 Like
Correct. And I can use whatever terminology I please to describe that.
Thank you.
Any data miners on here?
I literally have no clue when it comes to these type of things but I remeber seeing someone said they were constantly putting up new builds after we heard about the CDN.
Anyone still watching that? I’d assume the less they put up, the less they are changing, and the closer we are to the next phase, what ever that might be.
Which rolls us back to the origin of my first post. It has nothing to do with the label of choice. It has everything to do with where the changes happen and why type of changes.
Server and client isn’t getting a ton of changes. Beta becomes less and less important due to the fact that those had a beta already.
The database, could warrant a beta but my position is much of the possible errors in the database are going to be the players disagreeing with versioning.
Launch the game and sort that stuff out live.
It doesn’t matter how much is being changed, just that it’s different.
They were dropping builds until it was working in deployment. They only took 4 builds. Now that’s stopped so we’ll probably only see the occasional build there. It won’t be a the standard location for testing, as it seems to have been a phase testing the deployment which now works.
1 Like
This just breaks my heart. Unless i can play threw summer it feels like its going to be a fall releases.
1 Like
A “Classic Summer” is unlikely to be only a week long.
2 Likes
What’s different vs how much. Spelling errors don’t make for a good reason to beta.
Oh so you can link their changelog for 1.13 and prove that it’s just spelling errors?
Almost as if you think I am saying “no we shouldn’t have a beta” vs we shouldn’t have a beta for spelling errors.
There is no burden of proof in what I am saying. It’s a position. Even more to the point, it’s me illustrating a reason why they wouldn’t have a beta.
Spell errors are important.
I don’t want to be told to go to Red Ridge as a Horde player. I’ll die. ![:disappointed_relieved:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/disappointed_relieved.png?v=6" ":disappointed_relieved:")
Nah, it’s more like you can’t prove it. But I don’t know why you keep arguing this ridiculous thing with me, it’s like you think you’re going to change my mind or something.
Pulling things out of thin air like “it’s just spelling errors” doesn’t help your case.