Jump to content

Recommended Posts

Posted

 

Coded with feet, that's for sure. You can reduce code from Formulas.java to few lines (less than 10 overall). And your code is checking each type of weapon, each type of armor, and check 10+ times L2PcInstance, skill null, etc...

 

Ask to L2JReunion to learn "if / else if" at least, it exists since a while. And eventually parameterized Enum, see L2J CrystalType to get an overview of what I'm talking about.

 

And use 

code tag

This guy propably saw same config files on our free version and pointed out that we use this system in our sources.

That doesnt mean that we use it the way its coded... Also this code its for IL and our sources on H5. So its not c/p from l2jreunion!

So before talking and saying bullshits around, it would be better to ask or even dont throw ironic sayings.

 

This code is basically implemented on l2jreunion for pvp servers and owners that want to use custom items with crazy stats etc. Also as already pointed it could be useful  for owners that dont know how to edit skills etc and this way its easier to touch players damage .

 

Its on your own , if you want to use it or not.

As far as the "it is" xdem suck my balls :D

Posted (edited)

I just "trust" the sharer when it says it comes from your sources, if it is really coded like that, then you should remove it or at least rework it, because it sucks, no matter what. If you're only a user and decided to add to your sources, then the same scenario... If you're able to add that code without think about how ugly and inefficient it is, then I don't give a lot for others parts of your pack.

 

If it's not coded like that on your pack, good for you :P. And welcome to the circle of people who got a brain and simply don't c/p.

 

Whoever coded this piece of code, use it and spread it should be jailed.

 

@Intrepid, my pack uses 220mo at startup, and around 320 fully loaded. It misses around 10mo of scripts at worst, let's say. I don't know what needs so much RAM on higher chronicles. Finally you should know than an Java application tends to use a lot more RAM if the allocated RAM is big, it's right for aCis too (it can easily use 1g RAM if you set 4g max for example, it's not software which needs it as it can run with the basic 512 setting, but it's Java which does that naturally ; the only point is to space the GC cycles).

 

About thread in general, Intrepid is right saying than wepaon kind edit is inefficient, as it can impacts classes you didn't want to nerf. The thing you call "balance" should be made class by class, and you should also seek/fix synergies between classes.

Edited by Tryskell
Posted

This guy propably saw same config files on our free version and pointed out that we use this system in our sources.

That doesnt mean that we use it the way its coded... Also this code its for IL and our sources on H5. So its not c/p from l2jreunion!

So before talking and saying bullshits around, it would be better to ask or even dont throw ironic sayings.

 

This code is basically implemented on l2jreunion for pvp servers and owners that want to use custom items with crazy stats etc. Also as already pointed it could be useful  for owners that dont know how to edit skills etc and this way its easier to touch players damage .

 

Its on your own , if you want to use it or not.

As far as the "it is" xdem suck my balls :D

1st of all this code is for frozen and your code in your pack isnt the same but have the same configs and maybe isnt same coded in your pack with this code but is for same job. with this code you can change the same things with your pack. all this code is for + - the damages about classes. but i say again and again sure need make skills fix but with this you can fix more things for more balance

Posted (edited)

 

As far as the "it is" xdem suck my balls :D

 

I was refering to the code

 

 
 

i ask if team from l2jreunion is unskilled cuz he say "thats mostly a tool for the most unskilled server owners"

 

it is

 

no hardfealings <3

Edited by xdem
Posted (edited)

 

I was refering to the code

 

 

 

no hardfealings <3

 

:D mistake

sorry then, dont suck them ....

Edited by `NeverMore
Posted

I just "trust" the sharer when it says it comes from your sources, if it is really coded like that, then you should remove it or at least rework it, because it sucks, no matter what. If you're only a user and decided to add to your sources, then the same scenario... If you're able to add that code without think about how ugly and inefficient it is, then I don't give a lot for others parts of your pack.

 

If it's not coded like that on your pack, good for you :P. And welcome to the circle of people who got a brain and simply don't c/p.

 

Whoever coded this piece of code, use it and spread it should be jailed.

 

@Intrepid, my pack uses 220mo at startup, and around 320 fully loaded. It misses around 10mo of scripts at worst, let's say. I don't know what needs so much RAM on higher chronicles. Finally you should know than an Java application tends to use a lot more RAM if the allocated RAM is big, it's right for aCis too (it can easily use 1g RAM if you set 4g max for example, it's not software which needs it as it can run with the basic 512 setting, but it's Java which does that naturally ; the only point is to space the GC cycles).

 

About thread in general, Intrepid is right saying than wepaon kind edit is inefficient, as it can impacts classes you didn't want to nerf. The thing you call "balance" should be made class by class, and you should also seek/fix synergies between classes.

i cant understund good english so i cant understund what you try to say me :)

Posted

 

Coded with feet, that's for sure. You can reduce code from Formulas.java to few lines (less than 10 overall). And your code is checking each type of weapon, each type of armor, and check 10+ times L2PcInstance, skill null, etc...

 

Ask to L2JReunion to learn "if / else if" at least, it exists since a while. And eventually parameterized Enum, see L2J CrystalType to get an overview of what I'm talking about.

 

And use 

code tag

i say something about l2jreunion team cuz this project from l2jreunion is popular for now but i havent take the code from this pack. this pack have the same configs but is not same coded with this code. but in l2jreunion pack and this code do the same job. so dont say anything about l2jreunion. l2jreunion is hi5 pack and this code is for interlude

Posted (edited)

I just "trust" the sharer when it says it comes from your sources, if it is really coded like that, then you should remove it or at least rework it, because it sucks, no matter what. If you're only a user and decided to add to your sources, then the same scenario... If you're able to add that code without think about how ugly and inefficient it is, then I don't give a lot for others parts of your pack.

 

If it's not coded like that on your pack, good for you :P. And welcome to the circle of people who got a brain and simply don't c/p.

 

Whoever coded this piece of code, use it and spread it should be jailed.

 

@Intrepid, my pack uses 220mo at startup, and around 320 fully loaded. It misses around 10mo of scripts at worst, let's say. I don't know what needs so much RAM on higher chronicles. Finally you should know than an Java application tends to use a lot more RAM if the allocated RAM is big, it's right for aCis too (it can easily use 1g RAM if you set 4g max for example, it's not software which needs it as it can run with the basic 512 setting, but it's Java which does that naturally ; the only point is to space the GC cycles).

 

About thread in general, Intrepid is right saying than wepaon kind edit is inefficient, as it can impacts classes you didn't want to nerf. The thing you call "balance" should be made class by class, and you should also seek/fix synergies between classes.

 

What uses a lot of resources in l2j at higher chronicles is truly the bad coding practices for example their mmocore is by far the worst out of anything that has been used by any java based game emulator, their threadpool is outdated and messed up, their database handling is again outdated and messed up, almost all of their attempts to create a more versatile and easier to work with code failed(just compare their bunch of interfaces and holders with the global restriction of l2jfree). And thats just the tip of the iceberg, the biggest reason why l2j is as bad as it is, is their huge ego(always have been an issue). If something is good and tested for months they dont implement it just because they would need to acknowledge someone else did a good job from another team, so they rather try to implement their own version which rarely turns out to be better or even good than what they could have synced. Thats the reason why russians are ahead this much. :)

 

Ohh and memory stats doesnt matter because of l2j and therefore your pack too because you follow them on sync, tends to cheat and hide their bad practices for example the idea of deleting javolution instead of using a newer version and work around a faster and more versatile collection of classes just because it would require them to learn new things. :)

Edited by Intrepid
Posted

What uses a lot of resources in l2j at higher chronicles is truly the bad coding practices for example their mmocore is by far the worst out of anything that has been used by any java based game emulator, their threadpool is outdated and messed up, their database handling is again outdated and messed up, almost all of their attempts to create a more versatile and easier to work with code failed(just compare their bunch of interfaces and holders with the global restriction of l2jfree). And thats just the tip of the iceberg, the biggest reason why l2j is as bad as it is, is their huge ego(always have been an issue). If something is good and tested for months they dont implement it just because they would need to acknowledge someone else did a good job from another team, so they rather try to implement their own version which rarely turns out to be better or even good than what they could have synced. Thats the reason why russians are ahead this much. :)

 

Ohh and memory stats doesnt matter because of l2j and therefore your pack too because you follow them on sync, tends to cheat and hide their bad practices for example the idea of deleting javolution instead of using a newer version and work around a faster and more versatile collection of classes just because it would require them to learn new things. :)

 

 

no, they just have bigger static data to load, more managers and python which eventually will be totally removed and no they are not dead at all

Posted

no, they just have bigger static data to load, more managers and python which eventually will be totally removed and no they are not dead at all

The amount of static data doesnt matter in realtime performance only in startup time where they use an utterly useless and messed up wrapper for data loading. Tho that conversation would get pretty heavy considering 99% of the mxc community is an l2j guy coming from their hate against maven and understanding any other project.

  • 2 weeks later...
Posted

First of all the config part is wrong.

Should be:

+ DAGGER_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("DaggerVsHeavy", "2.50"));
+ DAGGER_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("DaggerVsLight", "2.00"));
+ DAGGER_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("DaggerVsRobe", "1.80"));
+
+ ARCHER_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("ArcherVsHeavy", "2.50"));
+ ARCHER_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("ArcherVsLight", "2.00"));
+ ARCHER_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("ArcherVsRobe", "1.80"));
+
+ BLUNT_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("BluntVsHeavy", "2.50"));
+ BLUNT_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("BluntVsLight", "2.00"));
+ BLUNT_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("BluntVsRobe", "1.80"));
+
+ FIST_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("FistVsHeavy", "2.50"));
+ FIST_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("FistVsLight", "2.00"));
+ FIST_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("FistVsRobe", "1.80"));
+
+ DUAL_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("DualVsHeavy", "2.50"));
+ DUAL_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("DualVsLight", "2.00"));
+ DUAL_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("DualVsRobe", "1.80"));
+
+ SWORD_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("SwordVsHeavy", "2.50"));
+ SWORD_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("SwordVsLight", "2.00"));
+ SWORD_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("SwordVsRobe", "1.80"));
+
+ POLE_VS_HEAVY = Float.parseFloat(L2JModSettings.getProperty("PoleVsHeavy", "2.50"));
+ POLE_VS_LIGHT = Float.parseFloat(L2JModSettings.getProperty("PoleVsLight", "2.00"));
+ POLE_VS_ROBE = Float.parseFloat(L2JModSettings.getProperty("PoleVsRobe", "1.80"));

Also there is missing the part about the mages but nothing fatal :)

And since there are so many replies that this code is useless or crappy well I don't think its like that ...

For sure this code will not balance your server but it will not un-balance it also (If the admin is not idiot and know's what values to put for configs).

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

    • This post originally appeared on MmoGah. Dear exiles, hot news about PoE 1! The new league, 3.27 Keepers of the Flame, will launch on Oct 31, 2025. I will share with you the top 6 league starters, and each build is chosen for its strength in early progression, affordability, and synergy with the new mechanics introduced in the Bloodline Ascendancy system and Breach rework.       1. Exsanguinate Reap Mines Trickster Overview This build combines the physical spell damage of Exsanguinate and Reap with the mine playstyle, leveraging Trickster’s energy shield and recovery mechanics for survivability and speed. It’s a hybrid between trapper and spellcaster, offering high burst damage and smooth mapping. Key Mechanics Ascendancy: Trickster (Shadow) Main Skills: Exsanguinate, Reap, High-Impact Mine Support Defenses: Energy Shield, Evasion, Ghost Dance, Spell Suppression Strengths Excellent clear speed with overlapping AoE Strong single-target burst from Reap Trickster’s recovery and mobility make it forgiving Weaknesses Mines require setup and can feel clunky for some Physical damage scaling needs investment for the endgame Playstyle Tips Use Exsanguinate for mapping and Reap for bosses Prioritize mine throwing speed and recovery nodes Utilize Bloodline Grafts to enhance ES sustain and mine damage Ideal For Players who enjoy tactical gameplay with high burst potential   2. Cyclone Shockwave Slayer Overview Cyclone Shockwave Slayer is a melee build that uses Cyclone to trigger Shockwave Support, creating massive AoE explosions. Slayer’s leech and overleech mechanics make it durable and fast-paced. Key Mechanics Ascendancy: Slayer (Duelist) Main Skills: Cyclone, Shockwave Support, Rage Support Defenses: Life leech, Overleech, Fortify Strengths Smooth and fast mapping with Cyclone Shockwave adds huge AoE and damage Slayer’s leech makes it tanky even with minimal gear Weaknesses Requires a decent weapon early on Single-target can lag without investment Playstyle Tips Stack attack speed and physical damage Use Rage and Berserk for burst phases Bloodline Grafts can boost leech and AoE scaling Ideal For Players who love fast, aggressive melee builds   DID YOU KNOW?  MmoGah is the most trustworthy digital game goods store. Here you can buy safe PoE currency 3.27 to hold your strong build easily with low prices and fast delivery. poe currency 3.27     3. Rolling Magma Mines Saboteur Overview Rolling Magma Mines Saboteur is a powerful hybrid build that uses mines to trigger chain explosions. Saboteur’s mine bonuses and trap scaling make this build extremely potent for both clear and bossing. Key Mechanics Ascendancy: Saboteur (Shadow) Main Skills: Rolling Magma, Mine Support, Chain Support Defenses: Evasion, Spell Suppression, Mine immunity Strengths Massive AoE clear with chain mechanics High uptime on damage due to mine detonation Saboteur’s trap/mine bonuses make leveling easy Weaknesses Mines require setup and timing Visual clutter can be overwhelming Playstyle Tips Use Rolling Magma for chain clear and boss stacking Prioritize mine throwing speed and detonation speed Bloodline Grafts can enhance mine damage and trap cooldowns Ideal For Players who enjoy strategic, explosive gameplay   4. Kinetic Rain Elementalist (NEW) Overview Kinetic Rain is a new skill introduced in 3.27, firing a barrage of projectiles that rain down in an arc. Elementalist synergizes with elemental damage and ailment proliferation, making this build a top-tier mapper. Key Mechanics Ascendancy: Elementalist (Witch) Main Skills: Kinetic Rain, Greater Multiple Projectiles, Elemental Proliferation Defenses: Elemental ailment immunity, high life, block Strengths Incredible clear speed with projectile spread Elementalist’s golems and ailment immunity boost survivability New skill offers fresh playstyle and visuals Weaknesses Single-target depends on projectile overlap Requires investment in projectile speed and damage Playstyle Tips Scale elemental damage and projectile modifiers Use golems for buffs and tanking Bloodline Grafts can enhance elemental spread and projectile count Ideal For Players who want to try new mechanics with flashy visuals   5. Poisonous Concoction of Bouncing Slayer/Pathfinder Overview: This build uses Poisonous Concoction with the new “Bouncing” mechanic, allowing projectiles to ricochet and apply poison multiple times. Slayer and Pathfinder both offer strong synergy—Slayer for leech and Pathfinder for flask sustain. Key Mechanics Ascendancy: Slayer or Pathfinder (Duelist/Ranger) Main Skills: Poisonous Concoction, Plague Bearer, Wither Defenses: Evasion, Spell Suppression, Flask sustain Strengths Great single-target with poison stacking Bouncing mechanic improves clear and coverage No weapon required—uses flasks for scaling Weaknesses Flask management is crucial Visual clarity can be messy in dense fights Playstyle Tips Use Plague Bearer for clear and Poisonous Concoction for bosses Pathfinder offers smoother sustain; Slayer offers better leech Bloodline Grafts can boost poison duration and flask effects Ideal For Players who enjoy chaos builds and flask mechanics   6. Righteous Fire Chieftain Overview Righteous Fire Chieftain is a tanky, fire-based build that burns enemies with a persistent aura. Chieftain’s fire scaling and regen make it a great starter, especially with Breach-heavy content. Key Mechanics Ascendancy: Chieftain (Marauder) Main Skills: Righteous Fire, Fire Trap, Shield Charge Defenses: High life regen, fire resistance, armor Strengths Extremely tanky and consistent Great for Breach and dense packs Easy to gear and level Weaknesses Requires fire resistance and regen early Slower movement compared to zoomy builds Playstyle Tips Use Fire Trap for single-target and RF for clear Stack life, regen, and fire damage Bloodline Grafts can enhance burning damage and regen Ideal For Players who want a durable, low-maintenance build   Final Thoughts & Tips Bloodline Ascendancy: Mix and match ascendancy traits to create hybrid powerhouses. For example, combining Saboteur’s mine bonuses with Trickster’s recovery can yield unique builds. Breach Rework: Builds with strong AoE and sustain (like RF and Cyclone) excel in Breach-heavy zones. Leveling Strategy: Use alternate skills early (e.g., Fire Trap, Explosive Trap) and transition once gear is available. SSF vs Trade League: All builds here are viable in SSF, but some (like Poisonous Concoction and RF) are especially strong due to low gear dependency. Whether you prefer tactical mines, explosive melee, or elemental barrages, PoE 3.27 offers a rich meta with exciting new tools.
    • Some new features that we added: - 2 new quests - PvP Arena (to get hero status) Olympiad is disabled - Love Event - Dressme for armor/weapons/accessories - HWID Protection - More monsters - New farm zone - New autofarm system (works almost like adrenaline) - Auto enchant - Auto augment - 3 levels of armors - 3 levels of weapons - Anti KS System - Rebirth Manager - 30 days checking rewards - Small event (daily checking with small reward for all online players)
    • Added FloodProtector utility to prevent packet flooding for actions like item use and dice rolling. Integrated flood protection checks in relevant client packet handlers and registered/removal hooks in player lifecycle. Updated movement logic in L2PcInstance for improved position synchronization and geodata handling. Minor fixes and refactoring in attack logic, private store handling, and admin NPC editing. Refactored AI classes to enhance movement, attack, and skill usage logic for characters and mobs. Improved distance checks, attack range calculations, and skill casting conditions. Removed unused intention command logic from L2CharacterAI. Updated configuration to enable CellPathFinding. Minor code cleanups and bug fixes for more reliable AI behavior. Enhanced GeoPathFinding with detailed debug and error messages for region loading, including success/failure counts and file checks. Refactored L2AttackableAI and L2CharacterAI to improve attack range tolerance, immediate attack behavior, and added safety checks for missing targets. Updated configuration to disable CellPathFinding by default and added a new ShowRedName option for aggressive mobs. Minor config and log updates included. Applied TCP socket optimizations (e.g., TCP_NODELAY, buffer sizes, keepalive) in ClientThread, Connection, and SelectorThread to reduce latency and improve throughput. Enhanced L2AttackableAI with better random walk, aggro, and attack logic, including silent move checks, quest monster handling, and improved faction/raid/minion behavior. Added silent move support to L2PlayableInstance and quest monster flag to L2NpcTemplate/L2NpcInstance. These changes aim to improve server responsiveness, AI realism, and overall stability.
    • I’ve been using this Escape from Tarkov Hack for about a week now with no issues at all. ESP works great without any lag, and the aimbot is smooth and doesn't feel obvious. Had a quick setup with the loader, and support answered my questions right away. The HWID spoofer also did its job without messing with my system. So far, the cheat's staying undetected on my side.
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock