Public Engine3 without time restrictions

[acidanarchy]

So entitled.

Same mindset that made things like Bloodfin happen. A group of entitled people using SWGEmu code close sourced, trash talking SWGEmu in the process, especially about how closed the engine is and how it's time locked, then using Emu code to pretend to have JTL working, etc, etc. In the end people legit thought Bloodfin was some kind of emulator, lol, competing with SWGEmu, and now believe SWGEmu is trying to steal them contents/codes, cause SWGEmu could never do it themselves and are stuck.


SWGEmu has every right to control their engine, the terms aren't even evil and as it's been said before, if you can't deal with it, just wait for 1.0.

Since the elephant in the room is finally out....

Why not just deal with that server directly instead of strong arming the rest of the servers and developers who
1) Support the project
2) Don't claim ridiculous things
3) Are willing to work with the SWGEmu team in a fair and balanced manner

Seems like the rest of us are going to suffer because of 1

[duffstone]

Since the elephant in the room is finally out....

Why not just deal with that server directly instead of strong arming the rest of the servers and developers who
1) Support the project
2) Don't claim ridiculous things
3) Are willing to work with the SWGEmu team in a fair and balanced manner

Seems like the rest of us are going to suffer because of 1

I think that's a bit strong given what little we know so far. WORST case, you have to open your Core3 specific source... If you're good enough to code "specialized functionality", specific for your community inside core3, then you're good enough to code an interpreter (API, whatever you want to call it) into Core3 that will read your "custom" code outside of the core3 AGPL license. It's just another manager. even if the rest of the world gets access to your new "Manager", they might see that you're interacting with the Jedi manager, the player manager, the tangible object manager, etc... but they won't be able to see WHAT you're feeding them in the outside process. Plus, it's highly doubtful that SWGEmu's staff will ever publish anything like that to the public GIT since it's so specific.

so really, it's NOT the end of the world. and it finally allows more communities freedom to expand into viable 24/7 online services. I think you'll see a treasure trove of goodness from this. Although, I highly doubt it helps 1.0 come about any quicker.

-Duff

[nee2earth]

I highly doubt it helps 1.0 come about any quicker.

If more people report un-discovered bugs and help contribute reliable patches, it most certainly will.

[Vlada]

Which in my previous post and example I had clearly laid out a case where "if" I paid someone to develop a giant pink dinosaur with a laser beam that fired on players and turned them into little fuzzy bunny rabbits, how could that possibly be of ANY value at all to the 1.0 roadmap?

It doesn't need to be, but if its a change made to the core then it has to be open source. Its not really our problem you just thrown your money away on something useless, its your money, you decide how you want to waste it. If you don't want to share, don't make changes to the core before 1.0.

[acidanarchy]

Its not really our problem you just thrown your money away on something useless, its your money, you decide how you want to waste it. If you don't want to share, don't make changes to the core before 1.0.

I'm not saying you guys need to be concerned with how other people spend their money. It isn't anyone's concern at all, that's obvious and it isn't even about money as that was simply an example. I was actually raising more concern over protection of people's original creations and work than anything and just seeking clarification on the SWGEmu staff's position on the extremely vague information that was been released to date regarding this issue.

I'm sorry if my posts come across as negative or beating the dead horse but this has quickly developed into a very disheartening and disappointing situation to say the least. I was hoping for more support towards the community than this but I suppose I will take the "don't let the door hit you on the way out" vibe as a hint.

[duffstone]

I'm not saying you guys need to be concerned with how other people spend their money. It isn't anyone's concern at all, that's obvious and it isn't even about money as that was simply an example. I was actually raising more concern over protection of people's original creations and work than anything and just seeking clarification on the SWGEmu staff's position on the extremely vague information that was been released to date regarding this issue.

I'm sorry if my posts come across as negative or beating the dead horse but this has quickly developed into a very disheartening and disappointing situation to say the least. I was hoping for more support towards the community than this but I suppose I will take the "don't let the door hit you on the way out" vibe as a hint.

../horse/beating/begin.sh

I gave a great example how to get around the AGPL license issue above. it's not hard to write a plugin / API / manager / whatever you want to call it that specifically relates commands / communications / etc to an external to core3 binary or library that can do whatever you want it to do, without being required to share that library. At least how I understand it. I'm sure if it's THAT big of a deal, you'll see some sort of universal (or otherwise easy to use) plug-in / add-in type module written for Core3 that all will be free to use, THANKS to the switch to AGPL.

Realistically speaking, this is the only way to ensure your code stays yours, and secret, even in a GPL environment. It's what the TA and Oru did for Engine3, and it's what I do at work all the time (just not in C, mostly vb.net).

and before the flames start: Easy is a relative term I understand. I couldn't write it in C, but I could in vb.net (or rather using the VS20xx interface to write .net code, it's just super simple and you don't have to be an uber geek to do big things).

killall begin.sh

[Vlada]

I'm not saying you guys need to be concerned with how other people spend their money. It isn't anyone's concern at all, that's obvious and it isn't even about money as that was simply an example. I was actually raising more concern over protection of people's original creations and work than anything and just seeking clarification on the SWGEmu staff's position on the extremely vague information that was been released to date regarding this issue.

I'm sorry if my posts come across as negative or beating the dead horse but this has quickly developed into a very disheartening and disappointing situation to say the least. I was hoping for more support towards the community than this but I suppose I will take the "don't let the door hit you on the way out" vibe as a hint.

Like i said, if you make changes to the core then your original content needs to open source, even if its a pink bunny, of you want it protected don't make those changes before 1.0.