To All no l2j projects but l2j based

[Sylar88]

Regardless of my mistake about licensing the question remains the same and stop avoiding the answering :

If you dont like others way of thought you can keep them out of your project. But you arent allowed to block their forking effort. Do you agree on that ? Simple answer, yes , no.

[BiggBoss]

and i answer again. Blocking diff view in trac is not a way to block fork sync. They can still sync us, moreover, they can still sync us in the way a svn must be synced, that there are ppl that does not know to sync without taking the diff from trac is not our problem

So, who blocked forks?

[gmakhs]

and im saying again why are you fighting? this isn't the point... the point is that ok you complain about custom shares. l2j can't crate a custom folder on svn for this shares ? and cooparate with their creator to keep them up to date ? and not up to date share be deleted or something ? so everyone will be happy

[MELERIX]

and im saying again why are you fighting? this isn't the point... the point is that ok you complain about custom shares. l2j can't crate a custom folder on svn for this shares ? and cooparate with their creator to keep them up to date ? and not up to date share be deleted or something ? so everyone will be happy

we already have dedicated areas in forum for custom shares.

[gmakhs]

so i still not get what the problem with custom shares not be accepted...

[Szponiasty]

and im saying again why are you fighting? this isn't the point... the point is that ok you complain about custom shares. l2j can't crate a custom folder on svn for this shares ? and cooparate with their creator to keep them up to date ? and not up to date share be deleted or something ? so everyone will be happy

heh. Almost all of you still miss the point (or dont understood me entirely).

1. I have nothing against L2j, or its forks (as long as they do not remove credits), or l2j/fork devs.
2. Why I do not like, that L2J not commiting customs (or features not entirely finished or not 100% retail like) to stable/beta (not saying about forum category for custom mods, but about commiting some customs into svn):
- commiting not fully done stuff improves implementation and testing of features by 10k %!
- its not difficult to make such features configurable to be disabled by default
- when they off, they do not impact game server performance, stability or ram usage in any way (unless implementation is bugged...)
- if you take a look at many customs that l2j servers had over the years, you will see that some of that customs was very similar to features that retail L2 servers obtained some time after they were introduced on l2j = allowing customs speeds up l2j upgrading when another l2 "chronicle" is introduced in retail servers
3. The biggest problem for very very slow evolution of L2J project, is that many commits stay ignored on forums for like 6 moths or forever. Not ever commited even to beta for tests, eg. cause of "no community feedback".
4. Also big problem, but maybe not so bad as one above - L2J forums currently look like "I wannna learn programming, but all I can do atm, is open web browser - still learning to use google too!" xD

Anyway nvm. I promise it was last time I was bringing that up, and won't gonna bitch any more ever about it (or reworks in L2J that I do not always find to be better solution). I will still try to help on forums wherever Ill know the solution, however I wont be posting any diffs or anything ever again. Anyway it's all useless stuff

[MELERIX]

so i still not get what the problem with custom shares not be accepted...

because atm main focus in L2J is about "Try Emulate L2 Retail Features as Possible", not modifications, NPCBuffers and related

http://www.l2jserver.com/about/

[Szponiasty]

so i still not get what the problem with custom shares not be accepted...

because atm main focus in L2J is about "Try Emulate L2 Retail Features as Possible", not modifications, NPCBuffers and related

http://www.l2jserver.com/about/

- if you take a look at many customs that l2j servers had over the years, you will see that some of that customs was very similar to features that retail L2 servers obtained some time after they were introduced on l2j = allowing customs speeds up l2j upgrading when another l2 "chronicle" is introduced in retail servers

(meaning: if there would be some customs etc commited into l2j, you would probably be long after done with implementing retail stuff, that are not implemented yet - eg. hellbound )

[MELERIX]

you know these "incomplete stuff" is rarely committed if not work as should or at least nearly how should.

for example we had Hellbound in L2J since long long time ago (on internal forums), but it was never committed to SVN until now (even the original author requested to no commit it yet) ?

why ?

because it was incomplete/custom in several things, even when we moved it to public (Hellbound v3), it still was incomplete/custom, and only after several months some of the community users decide to give a hand on it and help to finish it, not 100% ofc but now is playable, so the users don't complain a lot about it

[Szponiasty]

you know these "incomplete stuff" is rarely committed if not work as should or at least nearly how should.

for example we had Hellbound in L2J since long long time ago (on internal forums), but it was never committed to SVN until now (even the original author requested to no commit it yet) ?

why ?

because it was incomplete/custom in several things, even when we moved it to public (Hellbound v3), it still was incomplete/custom, and only after several months some of the community users decide to give a hand on it and help to finish it, not 100% ofc but now is playable, so the users don't complain a lot about it

So, you think that keeping it so long on private forums section helped developing it? Cause i think that if it has been commited from the very beginning, in stage as it was, it would be slowly developed by many more people = it would be done fully like 2 years ago. And it is still not commited elsewhere than beta branch...

[MELERIX]

well, for example about Hellbound, it was not in my hands, like I said above: "even the original author requested to no commit it yet".

so for example I can't just pickup contributions from "Core Controbutions Area" and add to SVN, because "that is not my area" (except some small fixes tested).

now, you can see my areas HTML/XML/SQL are mostly clean, due most of the things already committed.

so trouble atm is only with the areas related to coding (Core are in most of cases): Jython/Java (Quest/AI/Java Contributions and related).

[Szponiasty]

well, for example about Hellbound, it was not in my hands, like I said above: "even the original author requested to no commit it yet".

so for example I can't just pickup contributions from "Core Controbutions Area" and add to SVN, because "that is not my area" (except some small fixes tested).

now, you can see my areas HTML/XML/SQL are mostly clean, due most of the things already committed.

so trouble atm is only with the areas related to coding (Core are in most of cases): Jython/Java (Quest/AI/Java Contributions and related).

Hellbound was only an example Not saying that devs are not doing anything, or doing a bad job or anything like that. What I mean from the beginning is that maybe there should be little more loosened rules to what is commited, and for example if something looks to be something "promising" and is provided with possibility to turn that on/off eg by properties files config option, then it could be commited (and those who would want, would eg. turn that on and test it, provide feedback etc. so finally feature would be finished at some point).

///EDIT: then, in addition, would be much much lesser problem concerning often reworks with no backward compatibility. Cause now, when sth "custom" or unfinished feature is posted on forums, it very often becomes hard for people to be applied month later on reworked sources (what also might be reason for so small feedback from the community or not testing some things that are posted, at all)

[MELERIX]

about the rules of "what" and "when" is committed or not, depend of the Main Devs and Inner Circle, due is supposed that these rules are made to maintain the stability of the project.

and that is a thing that make a difference when you compare L2J with others projects (at least during this years)

[Sylar88]

bout the rules of "what" and "when" is committed or not, depend of the Main Devs and Inner Circle, due is supposed that these rules are made to maintain the stability of the project.

I think, saying that Kadar was in the inner cycle is enough to figure out lots of things ...

[ThePhoenixBird]

bout the rules of "what" and "when" is committed or not, depend of the Main Devs and Inner Circle, due is supposed that these rules are made to maintain the stability of the project.

I think, saying that Kadar was in the inner cycle is enough to figure out lots of things ...

Kadar is a former Inner Circle member, he is respected and we all thanks him for his support to the L2j Server project during years... even during on the dark ages of L2j...