They stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
11/03/2018 05:18 PMPosted by Renewnthe moment they decided NOT to use the 1.12 source code.
The fact that you can whisper members of the opposite faction through BNET while chilling in your faction's capital is heartbreaking to me.
It’s not just support for new systems, it’s security issues, and as they said in the Blizzcon panel even if they go through and apply fixes for every hole they know about, there’s going to be a long, long list of holes and problems that just go completely unnoticed until several hundred players get robbed of their gold or half a guild gets locked out of their accounts.
Classic, no matter which route they took, is going to be something of a Frankenstein’s monster sort of beast. The only difference is what’s getting patched in and where the patches are applied. Given that, it’s really stupid to not err on the side of better security at a very small deficit to authenticity.
Militant dogmatic purism isn’t helpful here.
Classic, no matter which route they took, is going to be something of a Frankenstein’s monster sort of beast. The only difference is what’s getting patched in and where the patches are applied. Given that, it’s really stupid to not err on the side of better security at a very small deficit to authenticity.
Militant dogmatic purism isn’t helpful here.
11/03/2018 05:18 PMPosted by RenewnThey stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
I'm not so sure. I think it was going to be a clunky mess, regardless.
Authentic and extact dont have the same definition
11/03/2018 05:43 PMPosted by MicroAuthentic and extact dont have the same definition
You're right.
Authentic: of undisputed origin; genuine.
Tell me how genuine this project is. The origins will be anything but undisputed.
11/03/2018 05:18 PMPosted by RenewnThey stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
They stated on the classic panel they found an exact 1.12 final vision backup to base Classic off, lmao
loooooong beta ahead11/03/2018 05:18 PMPosted by RenewnThey stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
I really think you shouldnt post at all if you hadnt watched the Classic Panel discussion at Blizzcon via the vticket. Youre spreading rumors and conjecture that are absolutely false.
11/03/2018 05:18 PMPosted by RenewnThey stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
Did your coding experience ever get past "hello world" printing? 1.12 source will literally not be recognized as computer instructions by some machines at this point. It's not in any way compatible with current server communication drivers or, likely, the launcher itself. It's probably also full of ugly hacks prone to breaking down in uncertain conditions that modern systems will provide.
From a programming perspective it's much easier to get the new systems to read copies of the old spells and talents, and just have the classic servers hold those tables and their clients mask systems that don't belong. If we're very very lucky, it'll bleed back into retail and we'll get old school talent trees again.
11/03/2018 05:58 PMPosted by Provengreil11/03/2018 05:18 PMPosted by RenewnThey stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
Did your coding experience ever get past "hello world" printing? 1.12 source will literally not be recognized as computer instructions by some machines at this point. It's not in any way compatible with current server communication drivers or, likely, the launcher itself. It's probably also full of ugly hacks prone to breaking down in uncertain conditions that modern systems will provide.
From a programming perspective it's much easier to get the new systems to read copies of the old spells and talents, and just have the classic servers hold those tables and their clients mask systems that don't belong. If we're very very lucky, it'll bleed back into retail and we'll get old school talent trees again.
The biggest challenge was never a programming issue. It was breaking up Vanilla and translating them into tiny Retail pieces. So while we were seeing the monstrosity that is now Classic, it's actually Retail behind the scenes.
How they actually use the old numbers, i don't know. It could be thrown into a retail combat calculation service for all we know. Which could explain why fighting mobs and damage was wonky in the demo.
11/03/2018 05:48 PMPosted by SmorkThey stated on the classic panel they found an exact 1.12 final vision backup to base Classic off, lmao
11/03/2018 05:56 PMPosted by HonorI really think you shouldnt post at all if you hadnt watched the Classic Panel discussion at Blizzcon via the vticket. Youre spreading rumors and conjecture that are absolutely false.
Please go back and watch the panel again. There's the 1.12 database, the 1.12 assets and the 1.12 source code. They explicitly said they're only using the 1.12 source code as a reference.
11/03/2018 06:03 PMPosted by Xanthak11/03/2018 05:58 PMPosted by Provengreil...
Did your coding experience ever get past "hello world" printing? 1.12 source will literally not be recognized as computer instructions by some machines at this point. It's not in any way compatible with current server communication drivers or, likely, the launcher itself. It's probably also full of ugly hacks prone to breaking down in uncertain conditions that modern systems will provide.
From a programming perspective it's much easier to get the new systems to read copies of the old spells and talents, and just have the classic servers hold those tables and their clients mask systems that don't belong. If we're very very lucky, it'll bleed back into retail and we'll get old school talent trees again.
The biggest challenge was never a programming issue. It was breaking up Vanilla and translating them into tiny Retail pieces. So while we were seeing the monstrosity that is now Classic, it's actually Retail behind the scenes.
How they actually use the old numbers, i don't know. It could be thrown into a retail combat calculation service for all we know. Which could explain why fighting mobs and damage was wonky in the demo.
That's definitely what's happening in the demo. But ultimately that's a tuning issue, and tuning comes later. Their goal for having the demo released was making sure a stable, useable client with the authentic class abilities working as intended. Not one of them has time to give a crap that the hunter pets are doing too much auto attack damage when the hunter bow requires ammo but you have to recode the entire item class.
I bet every single class gave someone a major headache trying to bring back one or more mechanics dummied out a decade ago.
11/03/2018 06:26 PMPosted by Provengreil<span class="truncated">...</span>
The biggest challenge was never a programming issue. It was breaking up Vanilla and translating them into tiny Retail pieces. So while we were seeing the monstrosity that is now Classic, it's actually Retail behind the scenes.
How they actually use the old numbers, i don't know. It could be thrown into a retail combat calculation service for all we know. Which could explain why fighting mobs and damage was wonky in the demo.
That's definitely what's happening in the demo. But ultimately that's a tuning issue, and tuning comes later. Their goal for having the demo released was making sure a stable, useable client with the authentic class abilities working as intended. Not one of them has time to give a crap that the hunter pets are doing too much auto attack damage when the hunter bow requires ammo but you have to recode the entire item class.
I bet every single class gave someone a major headache trying to bring back one or more mechanics dummied out a decade ago.
I hope you're right about tuning. If they don't that would make a bad situation even worse. The hp and mana regen were crazy. I saw a duel, between a mage and a priest. And the mage was able to get mana back in no time. Against, a priest as a mage, you don't just go OOM and somehow manage to get enough mana to start sheeping and throwing fireballs again.
...
That's definitely what's happening in the demo. But ultimately that's a tuning issue, and tuning comes later. Their goal for having the demo released was making sure a stable, useable client with the authentic class abilities working as intended. Not one of them has time to give a crap that the hunter pets are doing too much auto attack damage when the hunter bow requires ammo but you have to recode the entire item class.
I bet every single class gave someone a major headache trying to bring back one or more mechanics dummied out a decade ago.
I hope you're right about tuning. If they don't that would make a bad situation even worse. The hp and mana regen were crazy. I saw a duel, between a mage and a priest. And the mage was able to get mana back in no time. Against, a priest as a mage, you don't just go OOM and somehow manage to get enough mana to start sheeping and throwing fireballs again.
Im not in the demo, but I heard players aren't getting rez sickness either. The regen and the sickness immunity both have the same purpose: players literally only have an hour, lets not make them waste it. I'm not bothered by that stuff in the slightest because making everything work in the first place is far more important. It's like teaching someone to shoot a gun: make sure he knows how not to give himself Beretta Bite before working on the bull's eye.
blizzard created wow11/03/2018 05:46 PMPosted by Modelcitizen11/03/2018 05:43 PMPosted by MicroAuthentic and extact dont have the same definition
You're right.
Authentic: of undisputed origin; genuine.
Tell me how genuine this project is. The origins will be anything but undisputed.
blizzard is creating wow classic
they are have the exact same origin
private servers while trying to be exact to vanilla are not authentic
I am actually baffled by how some people actually accept sharding at launch and other qol garbage they added. Must be bfa players.
11/03/2018 05:21 PMPosted by Burlyqt11/03/2018 05:18 PMPosted by Renewnthe moment they decided NOT to use the 1.12 source code.
The fact that you can whisper members of the opposite faction through BNET while chilling in your faction's capital is heartbreaking to me.
They said they where going to put in things to prevent whispering people who are playing as an opposite faction but Bnet is used more for security reasons then anything else.
11/03/2018 05:18 PMPosted by RenewnThey stress wanting to provide us an "authentic experience", but this ultimately was never going to happen the moment they decided NOT to use the 1.12 source code.
They proceed to talk about "patching" things one by one, which as any software developer knows is an absolutely terrible idea. How did this make it past their "senior" software engineers? I'm just imagining the source code right now being a mass amount of commented out code and fix commits, and that's just an attempt at giving us 1.12. This game is going to be released with SO many things wrong (people have already started threads on this), and it's just completely unacceptable considering their number one goal is providing an "authentic experience". Surely adding support for your new systems on top of the 1.12 source code would have been a simpler task than doing mass comparisons and code changes (what they've clearly proved they are doing, and why we can't go outside the demo zones).
Disappointing really.
The issue is they lost all the coding of the authentic 1.12 patch and have no way of getting it back )just like private servers) so assuming that it's not 'authentic' 100% when even the best of private servers are not.
This however does not mean the experience will not be similar in all regards though.
Now how they are going about making Vanilla wow to me seems redundant and they could have easily used someone from the best classic private server to help speed things up and then use the old information on their servers to get better values for items and ability's. But what do I know lol
Undisputed origin = made by Blizzard.11/03/2018 05:46 PMPosted by Modelcitizen11/03/2018 05:43 PMPosted by MicroAuthentic and extact dont have the same definition
You're right.
Authentic: of undisputed origin; genuine.
Tell me how genuine this project is. The origins will be anything but undisputed.
People still in denial. Authentic means not pirated in Blizzard terms.
11/03/2018 06:54 PMPosted by Microblizzard created wow11/03/2018 05:46 PMPosted by Modelcitizen...
You're right.
Authentic: of undisputed origin; genuine.
Tell me how genuine this project is. The origins will be anything but undisputed.
blizzard is creating wow classic
they are have the exact same origin
private servers while trying to be exact to vanilla are not authentic
The classic demo has base 200% spell crit damage, which is a mechanic added in Mists. There are lots of similar other things technically wrong.
Classic private servers get these things right, they have the correct base 150% spell crit damage. At the moment, good classic private servers are more authentic.