Idea for devs regarding legitimacy.

[Docholy]

That is some insight, but I still can't give two fu*ks. Blizzard needs to get off their butts and start legacy servers. Otherwise we have no choice but to play on our own legacy servers.

I'm not defending them, since they should have listened a long time ago. I'm just offering information.

They aren't going to open themselves up like that though, so is there a way around it?

Yeah the way around it is to play on private servers that are outside the reach of Blizzards lawyers.

[Hydra9268]

You know what is a 100% easy fix. License the server out and make the Servers use Battle.net to login to verify everyone has an active wow account.

EVERYONE WINS!

That's one of the challenges Brack was talking about in his letter. According to Mark he believes Bnet2 integration could happen within 6 month; which would also include misc polish. J Allen Brack could proudly announce a January 2017 launch of Legacy servers during Blizzcon.

[Docholy]

You know what is a 100% easy fix. License the server out and make the Servers use Battle.net to login to verify everyone has an active wow account.

EVERYONE WINS!

That's one of the challenges Brack was talking about in his letter. According to Mark he believes Bnet2 integration could happen within 6 month; which would also include misc polish. J Allen Brack could proudly announce a January 2017 launch of Legacy servers during Blizzcon.

That's assuming it's just a bnet integration and the archivist did his job. Blizzard has to know any game is going to die and should've made this contingency a lot sooner to reduce the natural progression of cost.

[theluda]

Apparently, one of the big problems with this idea is that nost's work is a derivative work of mangos. It would bound Blizz to the mangos license, which would require them to release their source code, the person from WoW's tech forum said, and that this would be a field day for bot makers and hackers and other unscrupulous types.

a) MaNGOS license also forbids running public servers.
b) MaNGOS is open source and the fact that it is allows people to actually cut down on hacks.
c) Nostalrius can not make any deal regarding their server code with Blizzard, because the MaNGOS team owns the rights to it. Unless they rewrite all copyrighted parts they can't legally do anything.
d) why not hire the MaNGOS developers instead? It would be possible to talk to them, e.g. change license with their agreement to something like MIT which is business compatible.

The biggest problem is IMHO not wanting to solve the issue, and also talking to the wrong people.

MaNGOS developers talked about this yesterday, and if Blizzard would talk to us, we surely would be willing to make it legally possible. But they don't.

[ponyboy]

way back when was there not some private server using blizz code? I thought thats why they made emulators to begin with?

[r00ty]

way back when was there not some private server using blizz code? I thought thats why they made emulators to begin with?

None of the private servers use "Blizzard code". The emulation software is written from reverse engineering and generally coded from scratch. Blizzard IP is required to make one work properly though.

Since all private servers start with a base of one of the emulation open source cores, all of which have a similar/the same license as the original Mangos, while Blizzard could license a server to run their own vanilla (or any other expac) core and database, they couldn't license them to use an open source core. Well they could, but the now legitimate with Blizzard hosting group would be infringing on the core license.

Of course the way round it would be to produce an SDK along with a binary distribution of the old Blizzard core. But, producing the API for such an SDK would also take Blizzard time, and even then there's no way they'd want to release their actual core, even in binary form to outside organizations I'd wager.

So it is a problem for sure. Of course the solution is to get all parties involved in the communication. Clearly Blizzard aren't trying to do that. So, it's of course going to go nowhere.

[theluda]

So it is a problem for sure. Of course the solution is to get all parties involved in the communication. Clearly Blizzard aren't trying to do that. So, it's of course going to go nowhere.

That I can confirm. Blizzard has the contact info for MaNGOS and did not make any use in the last weeks of it.

[r00ty]

So it is a problem for sure. Of course the solution is to get all parties involved in the communication. Clearly Blizzard aren't trying to do that. So, it's of course going to go nowhere.

That I can confirm. Blizzard has the contact info for MaNGOS and did not make any use in the last weeks of it.

Well if they used cMangos as a base it gets even more complicated due to the history of that project. Actually maybe now this statement that they couldn't find a legal way forward has some merit.

[theluda]

Well if they used cMangos as a base it gets even more complicated due to the history of that project. Actually maybe now this statement that they couldn't find a legal way forward has some merit.

Well, all MaNGOS projects are connected, we talk to each other If they contact one of us, we all will know.

[Uidrae]

So it is a problem for sure. Of course the solution is to get all parties involved in the communication. Clearly Blizzard aren't trying to do that. So, it's of course going to go nowhere.

That I can confirm. Blizzard has the contact info for MaNGOS and did not make any use in the last weeks of it.

You actually made some sort of proposal to them and they didn't respond?

Why wait for Blizzard? Why don't you and Nost work together to come up with something to present to them? I just don't see Blizz getting in a hurry to do anything about this without a nudge.