A very little few of you may wonder what about even older versions of L2J? Well, by the C2-C3 era L2J were hosted using a free service (OpenSVN). Before that there were a CVS, but I’m too young in the project to provide further details about it. In the beginning OpenSVN services were good enough but our increasing traffic and bandwidth usage forced us to setup our own server (which costs us money, tnx for your donations btw ). For some reason beyond my memories, our source code were dumped from the old svn to the new one but changeset/revision numbering were set back to zero on purpose. If you’re really really interested in the code and its authors whose names should not be forgotten, here’s the SVN and its accompanying Trac. There are also some ancient binaries published in our Files section at Sourceforge.

Now switching topic, our latest release (Gracia Epilogue) won’t be added to the nightly build until it’s acceptably tested for a little while, unstable nightlies are still being built on Gracia Final. Wait a little bit for Epilogue nightlies or build GE on your own, and enjoy!

In the past, we had these groups: 

• Inner Circle
• Core and DP developers
• Core and DP initiates

but now it goes like this:

• Inner Circle
• Senior Developers
• Junior Core Developers – Junior DP Developers
• L2J initiates

Firstly, we have merged Core initiates and DP initiates to just one group, with the only pourpose to provide a richer environment for our new team members which, in the future, will become new developers with better collaborative skills.

After this (usully short) initiation period, initiates who are ready for the battle, will be promoted to either core or datapack junior developers depending on their skills or personal willing. They will be granted developer rights to public svn so they can start their career with certain autonomy.

Those team members who had spent a  succesfully period as junior developers, highly commited with project,  with excellent team skills, … will have a chance to join Senior Developers group. Despite senior developers represent the most trustable group for active coding, some members of this group are also expected to engage some executive task related to team, such initiates/jr. developers leadership or global leadership for DP or Core projects.

Why have we done this? Main target could be improve old user->initiate->dev process, taking more care of upbringing and formation process(es) so that(those) can be done more efficiently. However, we are trying to increase/improve our coding and project global leadership(s, both for core and DP) so, again, maximize performance of coding getting more organized. In other words, rather than an independent developing process for each developer, a bunch of independent coordinated tasks engaged by each developer.

Finally, Team and me are glad to announce four new skilly Junior Developers, all of them already well-known within community:

Core: _DS_, shansoft and janiii

Datapack: Sandro

I hope you wellcome them as they are worth to and wish best of lucks!

This is all for now, on next days you will probably find new blog post or forum threads with further information abut this and some new topics.

 Best regards!

PD: We hope forum/svn problems will be fixed soon, our apologies for that nasty issue.