If you mean differences between :
- L2J IL regular sources (as they are currently commited)
- L2JFrozen
- aCis
I simply can repeat what I said higher.
GENERALITIES
L2J IL is outdated (end of developement in 2007). Zoey76 made 2 commits for IL (warnings cleanup and MMOCore rework), which, when it fixes some critical issues is clearly not enough. L2JIL should be used as a base for a pack if you haven't any other alternative (as I did it myself, 18 months ago).
aCis is based on "latest" L2JIL (Zoey commited since that time so I can't use "latest" word anymore, but I made those changes (MMOCore + warning cleanup) before him so,
stricto sensu I can't use "latest" but the finality is the same), then used L2J postIL chronicles. Which means, many refactors such as :
- zone system (1011 zones overall instead of... 150 ?)
- AI system (mobs use their skill list and got an AI based on fighter/mage/archer/balanced system)
- scripts in Java and not on Jython anymore
- partymatching system.
- skills refactor
- items refactor (SA on dual, extractable items,...)
- many static data ported to XML rather than keeping SQL.
- many others, fixing shitload of stuff : doDie, summons avoid system,... Read timeline, I could write a book simply writing fixes.
A lot of things looks like Freya/hi5 (but IL behaviors have been kept), so ppl coming from those chronicles aren't really lost.
L2JFrozen is based on a Scoria leak (which is a russian private fork from dunno what other fork). It was kinda old leak as they didn't have partymatching for example (they used my own work to implement it). I never took time to check L2JFrozen (nor Scoria) sources, but russians are known to make shitty code, and some parts of Scoria are sometimes lol (when I take time to read L2JFrozen timeline).
I dislike how L2JFrozen work, and it's the main reason the fusion between projects never gone better than an pre-alpha version. It's as simple as it is.
POINT OF VIEWS
This is where you can choose one side or the other.
- L2JFrozen code mostly for fun, adding a lot of customs = fast configured server.
- aCis clean all custom I considered as useless and aim retail/L2OFF behavior = you add whatever you want and don't have to clean ugly-coded customs yourself. Which make config files and some parts of code easy to read.
L2J tends to be between both.
WORD OF THE END
My PoV can be considered biased about L2JFrozen (as we are "concurrent" - at least on chronicle), so make your own opinion.
There are way too much differences between projects, both about coding style, implication && goals.
L2J should be used as emergency, giving the fact some packs made a lot of works (mine included), it's kinda pointless to use it, until you want to show to everyone you got a big e-penis as I did with aCis. But the finality is one day or later you will do the same as I did (except the custom cleaning... near all was needed).