L2J Server

For live server use? From the looks of it, it doesnt seem to have any major issues atm. Maybe a developer can clear this up?

It's something you will truly know after running some tests, there are some issues with targetting system, which may PVP a bit harder, and some other minor problems.

What kind of targeting system problems?

The shitty, annoying kind. Locked target and stuff.

- Monsters give buffs to players instead to yourself.
- Some knownlist problems (invisible monsters attack you)
- Memory leaks (after 24hours server has "little lags"
- Some skills are not working correctly.
- Bugged some extractable items (you can open some boxs, got reward but extractable item won't disappear.)
- ...
Lazy to think what next. Choice if its stable enough or no.

In my experience, you should use stable version. I haven't had a nice month with unstable

So what to add from unstable to stable? Because I see in BETA fixed double login problem and I think it have a lot of more problems fixed, when stable don't have it... What you think?

Core - stable updated after 4 months
Datapack - stable updated after 12 months

And they are stable enough?

It's all an illusion. Both stable and beta have their problems, it's just that the problems on stable are considered not so important. But, of course, nobody knows ALL the problems. Syncing is fucked up because l2j team initially wanted to sync trunk with beta in whole chunks, not part by part, even if some of the parts would be extremely simple to port to trunk (e.g. quests).

jurchiks wrote:It's all an illusion. Both stable and beta have their problems, it's just that the problems on stable are considered not so important. But, of course, nobody knows ALL the problems. Syncing is fucked up because l2j team initially wanted to sync trunk with beta in whole chunks, not part by part, even if some of the parts would be extremely simple to port to trunk (e.g. quests).

Quests, AI's pretty much anything DP sided that doesn't require core side changes.

Some small method changes in core have been made, but nothing that complex.

Maybe it wouldd be better once new features or reworks have been proven stable on beta to be ported on stable. This way there wont be those big delays between stable releases and users will feel more confident to start using l2j again.

JMD wrote:Maybe it wouldd be better once new features or reworks have been proven stable on beta to be ported on stable. This way there wont be those big delays between stable releases and users will feel more confident to start using l2j again.

Big +1, because stable now "dead", no one use it, because some problems don't fixed, example double login issue and so on. It will be very good if needed fixes will be moved into stable version

Agreed

Stable has been synced 2 weeks ago, in what exactly do you agree? :/