Jump to content
  • 0

After Kill Reward Players Which Did Damage


Question

Posted

Hello, i want to make custom reward for players after killing another player not only when he killed him, but also if he made some damage, for e.g. if he made damage 50% of targets hp+cp, in which method I should add checks for how much damage did player to his target?

6 answers to this question

Recommended Posts

  • 0
Posted (edited)

You have to maintain a Map<objectId, Integer> for each player, and whenever an hitter hits the victim then the map is edited. Be aware than a hitter shouldn't be only a L2PcInstance, but a L2Playable (pets count, otherwise summoners are fucked up in the story).

 

The ratio per hitter is simply the value of the hitter / sum of all values.

 

Once the victim dies, the Map is .clear(). The Map should probably be .clear() after a given timer aswell (1min), but the timer refreshed if the victim is hitten.

Edited by Tryskell
  • 0
Posted

You have to maintain a Map<objectId, Integer> for each player, and whenever an hitter hits the victim then the map is edited. Be aware than a hitter shouldn't be only a L2PcInstance, but a L2Playable (pets count, otherwise summoners are fucked up in the story).

 

The ratio per hitter is simply the value of the hitter / sum of all values.

 

Once the victim dies, the Map is .clear(). The Map should probably be .clear() after a given timer aswell (1min), but the timer refreshed if the victim is hitten.

 

In this case I would go straight to ConcurrentHashMap or HashMap<L2PcInstance, Integer> so I have a direct reference to the players who dealt most of the damage, you don't care if someone's client looses L2PcInstance reference after DC / Restart since theres will be no difference.

  • 0
Posted

You have to maintain a Map<objectId, Integer> for each player, and whenever an hitter hits the victim then the map is edited. Be aware than a hitter shouldn't be only a L2PcInstance, but a L2Playable (pets count, otherwise summoners are fucked up in the story).

 

The ratio per hitter is simply the value of the hitter / sum of all values.

 

Once the victim dies, the Map is .clear(). The Map should probably be .clear() after a given timer aswell (1min), but the timer refreshed if the victim is hitten.

 

 

In this case I would go straight to ConcurrentHashMap or HashMap<L2PcInstance, Integer> so I have a direct reference to the players who dealt most of the damage, you don't care if someone's client looses L2PcInstance reference after DC / Restart since theres will be no difference.

 

Thanks for answers, i like idea with HashMap<L2PcInstance, Integer>

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

    • ## [1.5.1] - 2026-01-30   ### 🐛 Bug Fixes - **Top Voters**: Top voters list now loads correctly for inactive servers (previously showed "Server not found"). - **View Counter**: Server info page view count now records correctly for inactive servers.   ### 🔄 Improvements - **My Servers – Hide/Active**: The hide/active toggle now works correctly and is only shown when the server is approved (active) by an admin. Owner hide/show is separate from admin status. Toggling no longer causes a full page refresh. - **Accessibility**: Form fields on the server info edit form, add server form, and related pages now have proper labels and IDs for screen readers and autofill.
    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
  • 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..