Jump to content
  • 0

[HELP] Custom killing spree system l2j server [/HELP]


Question

Posted

Hello, i got the source code for the custom killing spree system from Cobra which was for l2j free and i converted it for l2j server. The  only problem is the following: I configured it so that when someone had 30 pvp kills in a row, a "You are on a killing spree" message would show up on his screen and an announcement would be published on the global chat. Here is the thing. I inserted a code so that when you have 30 pvp kills in a row not only would a message appear but you'd also get hero status and on death this hero status would disappear but i failed. I compiled and i went ingame to test it ,everything worked fine except that when i was getting 30 pvp kills i could see the hero glow but others could not, they could only see it after a restart of their client. And also, when i was on death my hero glow would not disappear if i didnt restart my client. Here is the code in the file L2PcInstance:

+private int impro = 0;
    public void increasePvpKills()
    {
    	 + impro++;
    	            
    	           +switch(impro){
               
    	         
    	      +case 30:
    	        + ExShowScreenMessage case30 = new ExShowScreenMessage("You reached 30 killing spree!", 10000);
    	         +sendPacket(case30);
    	         +Announcements.getInstance().announceToAll("Player  " + getName() + " Is On a Killing Spree Someone Stop Him");
    	         +setHero(true);   	        
    	        + break;
    	             + default:
    	              + ;
    	           + }

 

 

// Check if the player is dead
        if (isDead())
        {
        	+impro = 0;
        	+setHero(false);
        	abortCast();

 

Anyone got an idead of how to fix this? Thanks!

4 answers to this question

Recommended Posts

  • 0
Posted

is this the code for sending the users data to the server? or is there anything else like sendPacket(setHero); ? i tried to build a new method that would connect with isHero but didnt work out

  • 0
Posted

broadcastUserInfo() send player informations both for player (CharInfo packet) and for his knownlist (broadcast UserInfo). Both problems you said can be linked to a miss of that method. In the end of setHero() method, just add that line :

broadcastUserInfo();

 

If it works I'm glad, if it doesn't, drop that line and search anywhere else. I got no other idea.

 

Btw the switch for one case isn't easy to read (I know you made it like that because Cobra code was using it), just use following if you got only one case :

if (impro == 30)
{
    	         sendPacket(new ExShowScreenMessage("You reached 30 killing spree!", 10000));
    	         Announcements.getInstance().announceToAll("Player  " + getName() + " Is On a Killing Spree Someone Stop Him");
    	         setHero(true);
}

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

    • 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:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
  • 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..