Rootware

Unfortunately, I can't put the skills of logical thinking into your head so that you can use my Java code. The hardest thing I gave you in code form.

I remember what on Innova L2OFF last hit in party always made player with premium account. It means, drop rates and experience was relative with killer's account status. You made madness implementation. Premium user does not need be activity in a party for getting benefits.

All L2J packs have the same quality. Difference only in customization level. If you interests about L2OFF implementation then they are have common bugs for all L2J projects.

http://rootware.ru/lineage-2-interlude-client/

All actions in CharacterCreateScreen it's client related issues. Server sends only race info packet.

Try to use clear client pack.

Don't wasting your time for nothing. Try to use IP for determine a players. HWID as vulnerable as IP address.

So, these projects are different based?

Hire developer for fix all exploit in Frozen is much cheaper than adding all Frozen's addons to aCis. In the end you get the same quality a pack because 99% players don't knows how is looks L2OFF gameplay.

Try to use yGuard. It's The only one tool (actual for 2016 year) who don't brokes a jar package overall.

If you have no plans weekly/daily updates of client side then not need to waste a money for pointless tools.

All these issues related with geoengine and movement systems. And never be fixed because L2J developers don't understand how it must work properly. This problem is due to the fact that need to have some basic mathematical knowledge and knows what client and server it's one whole and ignore some client/server data the big mistake. No one don't tries perceive an object movement as a vector that has a direction, velocity and acceleration. All developers write a code imagine what an object moves by horisontal surface with constant speed. For this model he can't falling or slide with acceleration on inclined. About validation position it's really magic in L2J. Server side have absolute data and this is uses as true position. And "насрать" what client sends to server. LMAO Only newbies tries to fing "better" geodata for resolving this issues but geodata related only with elegant final pathways for pathfinding's result (from point A to point B) and correct detecting objects behind an obtacles. That's all. As @Trancesaid if you need actual geodata for your maps you can hire @deMEVfor this job. If you have some stuck places you can edit this places manually because any builder will produce conflict cells. If you have any other issues just use L2OFF platform. In next 5-8 years L2J don't resolve it. Have a nice day.

By what criteria do you determine the quality of geodata?

Exists the easy way: Download Eclipse. Unpack Eclipse in separated folder. In side this folder make new folder with name "jre". Download OpenJDK 17 or another version. Unpack OpenJDK into this folder. All Java projects what will added into workbench in future will use this Java version as default. In profit you can use separated Eclipse version for any Java version and not need to install into the system Java.

Yes.

That's means what it HARDCODED and can't be edited via edition another files. Only DIRECT or HOOK changes.

This text hardcoded in Window.dll. (c)

Bad code. What happen if HTML tag have no custom size params - window size 0, 0 or previous size? Window in interface don't destroying anfter closing. It's just hidding.

This solution helps you in this issue and many others.

Just add in the end of experience array new values for levels above 80. That's what you need to edit on the server side.

Use seatch tool on the forum. Already shared.

Maybe better use retail "fix" and use swimming speed for run/walk mode from PC_paramaters.txt? moving_speed_begin FFighter={80; 115; 50; 50; 0; 0; 0; 0} MFighter={80; 115; 50; 50; 0; 0; 0; 0} FMagic={78; 120; 50; 50; 0; 0; 0; 0} MMagic={78; 120; 50; 50; 0; 0; 0; 0} FElfFighter={90; 125; 50; 50; 0; 0; 0; 0} MElfFighter={90; 125; 50; 50; 0; 0; 0; 0} FElfMagic={85; 122; 50; 50; 0; 0; 0; 0} MElfMagic={85; 122; 50; 50; 0; 0; 0; 0} FDarkelfFighter={85; 122; 50; 50; 0; 0; 0; 0} MDarkelfFighter={85; 122; 50; 50; 0; 0; 0; 0} FDarkelfMagic={85; 122; 50; 50; 0; 0; 0; 0} MDarkelfMagic={85; 122; 50; 50; 0; 0; 0; 0} FOrcFighter={70; 117; 50; 50; 0; 0; 0; 0} MOrcFighter={70; 117; 50; 50; 0; 0; 0; 0} FShaman={70; 121; 50; 50; 0; 0; 0; 0} MShaman={70; 121; 50; 50; 0; 0; 0; 0} FDwarfFighter={80; 115; 50; 50; 0; 0; 0; 0} MDwarfFighter={80; 115; 50; 50; 0; 0; 0; 0} FKamaelSoldier={87; 122; 50; 50; 0; 0; 0; 0} MKamaelSoldier={87; 122; 50; 50; 0; 0; 0; 0} moving_speed_end where, {ground_walk; ground_run; swim_underwater_walk; swim_underwater_run; fly_walk; fly_run; swim_surface_walk; swim_surface_run}. Or continue make shitcode on previous shitcode, aka Shitcode Dev?

No way. No reason for correcting X,Y coords under water. Swimming is very slow for making async and exploits.

Maybe because it means what in water zone you can't falls down and no point to correct from server side the Z height, except the cases where position definely out of water zone? What kind of logic would you assume if you were a client developer?

You got info where you need to dig. But the major problem not in us. The problem is your "low qualification" for this job.