Jump to content

Recommended Posts

Posted

Using stable H5 server pack.

 

I made a sub class and killed a mob to level it but it now says 899.73% on level 40. What is this ?

 

*Edit - I noticed when editing a character that has this problem it has only 67 for the XP count. Is this normal?

Posted

Update with L2jServer BETA 8693 on February 25

Fixed in this BETA:   

- BETA: Datapack part for ​[L5192]

    Added gameMasterSkillTree.xml

    Added gameMasterAuraSkillTree.xml

    Added heroSkillTree.xml

    Added nobleSkillTree.xml

  This unhardcodes this skill trees and allows easy update/customization.

- BETA: Removed duplicated spawns.

- BETA: More Rainbow Springs Chateau fixes:

    RainbowSpringsChateau? cleanup and fixes.

    Implemented Messenger's retail HTMLs and AI.

    Implemented Caretaker's retail HTMLs and AI.

    Datapack part for ​[L5190].

  Note: Rainbow Springs Chateau clan hall siege is still unfinished, this is just some work to get it closer to retail and closer to be finished.

- BETA: Removing Kasha Bear's duplicated spawn, thanks Loup_Solitaire.

- BETA: Removing duplicated spawn for Yetti Messenger (35604), thanks tukune for report.

- BETA: Adding all missing Territory Managers spawns.

  Thanks malyelfik for report and first fix implementation.

- BETA: Fix ClassMaster? error

- BETA: Improving UseItem?'s log and avoiding flood in logs.

        Unmanaged Item handler: means there is an item handler defined in XML, but doesn't have a Java counterpart.

        No item handler registered: means the items doesn't have an item handler defined in XML, yet the client request it's use.

- BETA: Adding a config for maximum adena. Better throw all those gold bars to the trash because now you can set values as big as this: 9 223 372 036 854 775 807 - nine quintillion two hundred twenty three quadrillion three hundred seventy two trillion thirty six billion eight hundred fifty four million seven hundred seventy five thousand eight hundred seven.

If your server reach this value, you really have to lower the rates :)

- BETA: Implementing more skill trees:

    Removed hardcoded GMSkillTable.

    Removed hardcoded HeroSkillTable?.

    Removed hardcoded NobleSkillTable?.

    Implemented support for XML new skill trees.

  This represents a cleanup and unification of core functions.

- BETA: Fix for for Hero diary from [5145], thanks Vulcan and tukune for report.

- BETA: Fixing few methods naming:

        getHasFort() to getFortId()

        getHasCastle() to getCastleId()

        getHasHideout() to getHideoutId()

        setHasFort(..) to setFortId(..)

        setHasCastle(..) to setCastleId(..)

        getHasHideout(..) to setHideoutId(..)

        Fixed JavaDocs? related to those methods.

- BETA: NullPointerException? fix, thanks tukune for report.

Posted

Update with L2jServer BETA 8699 on February 27

Fixed in this BETA:   

- BETA: Help for telnet packetsend

- BETA: Removed isCrystal boolean from enchantData.xml, enough using successRate (thanks Starter).

- BETA: Missing Door Radius for H5 Olympiad Stadiums Doors, thanks VlLight?.

- BETA: AdminSkill? update:

        Added give_all_clan_skills command, it will reward the target's clan will all available skills for that clan level.

        Added some JavaDocs?.

        Rewritten some parts of previous code.

- BETA: Fix for Path To Orc Shaman(416) quest by Tavo22.

        Missing from [8509]

- BETA: ECJ Lib Update.

- BETA: Fixing some typos in SystemMessageId?.

- BETA: Sysmsg for safe enchants failed, also code format/cleanup, thanks nonom for test.

- BETA: More NPE fixes for [5185] , thanks Tavo22 for report and skyshadow for fix.

- BETA: Updated Copyright info a bit and code format/cleanup.

- BETA: Minor typo fix in TownManager?.java, thanks _Blade_.

- BETA: Moving ClanWarehouse? to proper package.

- BETA: Listeners fixes:

        NPE Fix for ClanWarehouse?, thanks Starter and Tavo22 for report.

        Fix for typo on Item Tracker, thanks Starter for report.

- BETA: A little more info for the MaxAdena? config that some of you asked me for.

- BETA: Fix ClassMaster? error

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Posts

    • Lineage2 Freya High Five @ Reshade with fog and rain etc @ Gracia final epilogue atmosphere   this reshade will eat lots of GPU power 50% or more of an RTX 3060 so be carefull depending on what effects are activated and their settings will eat even more GPU recomended 60hz monitor settings and via nvidia panel in Lineage2 game profile vsync settings to on effects are set up till film deck and the rest are not used but still working again this can eat alot of GPU Don't overheat GPU this is for freya high five but might work on others too copy in the  System  folder the folder  reshade-shaders  and the files  d3d9.dll  ReShade.ini  ReShadePreset.ini  ReShade.log  CccDddCcc.ini insert opens the menu and delete is on and of some settings need  ctrl + left click  to be changed   making another profile will reset the not activated effects to their default values so just copy the profile  CccDddCcc  and rename if needed also something needs to be closed from settings in game menu, the blur at distance and advanced shaders but keeping the advanced water effects all reflections   for those that don't like the h5 look of the sky and the red fog and rain and ambien red at night on all maps well if we want the cool gracia final epilogue back then we need to do this rename the  Maps  folder to Mapsretail or whatever copy the  Maps  folder from gracia final epilogue to h5 also we need the  L2_Skies.utx  from gracia final epilogue  Textures  folder to be replaced and also we need to do the same to the files  timeenv0.int  timeenv1.int  timeenv2.int  timeenv3.int  found in  system  folder   another setting that will probably be needed but not really tested out is to open file  option.ini  from  system  folder and add cachesize like this   [FirstRun] FirstRun=2   [Engine.GameEngine] CacheSizeMegs=512   also maybe is good to change those to 4.000000   [ClippingRange] Terrain=4.000000 Actor=4.000000 StaticMesh=4.000000 StaticMeshLod=4.000000 Pawn=4.000000       sorry bad english   https://mega.nz/file/aRNXxDrQ#mbxrNERBtW0XEEezK6w8-86oZWuX1k6NgtR6RZWKRVM    
    • Thanks, tho if possible let's lock the topic. I decided to finish up myself as I only created this to save up my time, but seems that while waiting for prop dev. finished myself.
    • Plus he have Discord where using Celestine, Nightwolf and others names to ensure that he is legit, what a looser, that's why mxc have bad reputation, coming here is like 50/50 get scammed.
    • Greetings, MaxCheaters community! We are the development team behind projects like AdenLand, Classic GvE, TinyEssence, PvPEssence, and several others. Over the years of managing high-traffic servers, we’ve built our own ecosystem of tools for datapack and client editing, simply because standard software often failed to meet our production needs or was too slow. Today, we are opening access to these professional solutions for our colleagues in the dev scene. You can explore our suite of editors and utilities here: 👉 https://la2.tools/ Why choose our tools? Battle-Tested: This software is used daily to maintain and update our own live projects. Efficiency: Designed to automate routine tasks that usually take hours or even days. Stability: Built to handle complex client/server structures where generic tools often crash. We are ready to provide consultations on integrating these tools into your development workflow to make your process faster and more secure.  
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..