The good news is people who maintain private servers will be updating their servers with WoW Classic values so if Blizzard fails, more private servers will spring up with extremely accurate values since they will have WoW Classic to test by.
You must have missed the thorough and what I found to be informative explanation on how they will be getting shutdown once Classic releases. I didn’t read or understand all of the info but it is worth a read. Scroll up
If you’re referring to my post, that is true for some servers, but I can almost guarantee you if Blizzard messes up, many more people will spring up. Not only will they have the latest code, but also the ability to test values. I think it is a good thing. It keeps Blizzard in line, if they screw up, private servers will gladly take their place.
Edit: This forum is garbage, I hit reply to @Normathord and it doesn’t show.
I hope you’re aware that “retail scrub” is right… Blizzard will be 100% shutting down all private servers around the world. They are a business. They are protecting their I.P. simply by feeding peoples demands to create Classic. as soon as any private servers get big enough to be any fun, Blizz would be issuing cease and desist letters to them and shutting them down. People will stop playing on Private servers simply because there’s a very very high chance all your data and progress will be lost as soon as Blizz shuts them down, so why not just play classic.
Yeah there was lots of people who play on Pservers who helped make Classic happen. But now that it’s here. Blizzard will be keeping their I.P. safe, and ordering shut down of all Private servers. If you don’t think this will happen and Private servers will stay alive and on going… you’d be wrong.
No, if that’s the case which it is, you’re blatantly ignoring what I’m saying and rewriting my words to continue your argument.
The beta code was not incorporated into any Private Server codebase. It simply was used as a guide to mechanics implementation.
I’m not ignoring what you’re saying. I quoted you earlier today in response to derived works, regarding the server and the client. See the earlier post, if needed.
I was then quoted about the release of beta code, which I stated I was unaware of, and don’t find it likely. I still don’t, but I’m willing to concede it as it was merely support to the derived works post, and immaterial to the conclusion.
In other words, it isn’t worth it to argue whether a very small subset of back-end code was stolen and used as a guide, because at the end of the day, even if it was, the gap had to be closed through packet sniffing–which could also have also been used at the onset, still getting to the end, which is a “blizz-like” server.
I’m happy to concede the server leak, as we still arrive at the same place, which is that the server code is “blizz-like.” We can debate whether that makes it a derived work or not, but I don’t believe there is a need, as we’ll end up at the same place.
Friends?
I’ve never claimed otherwise. The entire basis for the Private Server’s claims to legitimacy stem from the fact that their servers never use anything of Blizzards, and the only elements are naming in the database. If they actually had real blocks of Blizzard’s code in their open source product, then Blizzard would have strung every one of them out to dry years ago.
They live on the legal fiction that the Client is configured by the user, and the user has the right to the client, so the fact that the client connects to a non-Blizzard server is immaterial.
In the original ruling for the Rebirth case on WoW Bots in Germany, the judge’s ruling was based on the fact that the bots contained zero code from Blizzard and therefore were not infringing copyright.
The superior court’s ruling was that that ruling was in error because without the Blizzard servers, the bots were rendered effectively useless, and the bots were causing material harm to Blizzard’s business.
Private Servers claim that they have zero Blizzard code and therefore hide under the same umbrella. They claim they are emulating abandoned IP with their own work and the fact that they don’t constrain what client connects to them, means that a user using the Blizzard 1.12 client is not the Private Server’s issue.
Once Classic is up and running, the supposed abandonware claim under the Orphan Works Directive is no longer legitimate, and Blizzard can show material harm to its business because they can claim its detracting from Classic subscriptions.
Orphan Works has never been tested against Abandonware however, so Blizzard needs Classic up and running first, to present the strongest case they can. A rushed judgement with a negative ruling would set a dangerous precedent for the gaming industry, and justify private reuse of pretty much any MMO client prior to the current one. A positive ruling would ease the way to reducing their legal burden by sending a C&D with an attached copy of the ruling to every Private Server and waiting for them to cave.
1 Like
I did like the world channel.
also a /who gave you a total of online players.
One thing I disliked about certain undocumented servers was how a majority of the population didn’t speak english. It will be nice to be able to communicate with almost everyone.
We’re talking past each other, but let’s continue. The servers themselves are not open source. I don’t think Nos or any of the others ever released their changes to mangos. But I haven’t looked.
The MDY case which predates Rebirth by… a decade? Showed that merely making a copy of the client in memory against the EULA was an infringement. Which is what anyone with a client does when connecting to a private server.
I’m not arguing the legitimacy of private servers, though. Or bots. I’m saying that I’m not aware of any release of source code related to server side. And that the umpteen early emulators wouldn’t have needed it anyway. They needed a client. Which they got.
The Nost core is open-source. It was leaked publicly in W 2017, and the Ely devs decided to just make it open source in response. I believe you can view all their commits since then on their git.
ya didn’t he say auto-loot alone could save like 2 hours or something
Nost is based on Mangos. Elysium used the Nost code but after their discussions with Blizzard, Nost issued a C&D to Elysium for that code.
In America. Precedent in Germany applies to French private servers, because the EU recognizes all constituent country’s rulings. They don’t recognize US precedent.
And I never claimed they had it, and you misread the guy who said that it was “used”.
Never knew, thanks for the update.
Has anyone ever told you that you are just absolutely the best at pointing out people’s flaws. Now do you.
I don’t believe that I misread it–this is my first language. But I am making a semantics argument that one cannot use something that has not been obtained.
I am not allowed to use a F-22. Which is good, as I don’t have one.
If the private servers do not have Blizzard code… they aren’t using it. Again, we can discuss derivative works. But it won’t matter. Maybe something is getting lost in translation.
Someone did, years ago. Since then it has been dissected analyzed and set aside. I have no idea if even the Mangos team saw the code.
Hell, someone leaked a copy of the Alpha client in Jan 2004.
But it’s all irrelevant because no modern and active private server contains real Blizzard code.
Blizzard isn’t actively pursuing the private servers like they did with honorbuddy. Probably because of the ridiculous amount of resources they had to use to shut honorbuddy down.
Also private servers are staying up for the time being because of how god awful wow currently is. The decisions being made are absolutely face palm head exploding stupid that there is a good chance they could screw classic up.
“Yet”.