Jump to content
  • 0

check if player.isDead() method


Question

Posted (edited)

Hello again! XD .

 

Well i created a zone with auto-revive  when a player is dead inside zone.

But i want check if players is dead before auto-revive..

Because even he get res before cooldown of auto-revive, after cooldown he teleport to revived-location even he is alive :/.

 

i want check if player isDead before auto-revive to avoid if he is alive to revive .

 

i hope you understand :) 

Code i use: 

Spoiler

        public void onDieInside(final L2Character character)
        { 
            if (character instanceof L2PcInstance)
            {
                final L2PcInstance activeChar = ((L2PcInstance) character);

                if(Config.revive)
                {
                    ThreadPoolManager.getInstance().scheduleGeneral(new Runnable()
                    {
                        @Override
                        public void run()
                        {
                            activeChar.doRevive();
                            heal(activeChar);
                            int[] loc = Config.spawn_loc[Rnd.get(Config.spawn_loc.length)];
                            activeChar.teleToLocation(loc[0]+Rnd.get(-Config.radius,Config.radius), loc[1]+Rnd.get(-Config.radius,Config.radius), loc[2]);
                        }
                    },Config.revive_delay*1000);    
                } 
            }

 

Also i tried something like this but nothing:

Spoiler

        public void onDieInside(final L2Character character)
        { 
            if (character instanceof L2PcInstance)
            {
                final L2PcInstance activeChar = ((L2PcInstance) character);
                try
                {
                    Thread.sleep(600);
                }
                catch (InterruptedException e)
                {
                    // TODO Auto-generated catch block
                    e.printStackTrace();
                }
                if(Config.revive && activeChar.isDead())
                {
                    ThreadPoolManager.getInstance().scheduleGeneral(new Runnable()
                    {
                        @Override
                        public void run()
                        {
                            activeChar.doRevive();
                            heal(activeChar);
                            int[] loc = Config.spawn_loc[Rnd.get(Config.spawn_loc.length)];
                            activeChar.teleToLocation(loc[0]+Rnd.get(-Config.radius,Config.radius), loc[1]+Rnd.get(-Config.radius,Config.radius), loc[2]);
                        }
                    },Config.revive_delay*1000);    
                } 
            }

 

 

Help!! i tried to find similar code to find a solution but couldnt!

Edited by Irrelevant

7 answers to this question

Recommended Posts

  • 0
Posted (edited)

You don't have to code anything inside the zone's method since the feature is about the player instance. You could make a manager to handle all these actions but this is just another case.

 

Lets begin about the basics. The zone, should only call a method in the player instance without any check for dead/alive since this call will be executed inside of Zone#onDieInside.

So,

 	@Override
 	protected void onDieInside(final L2Character character)
 	{
+		final L2PcInstance player = character.getActingPlayer();
+		if (player == null)
+			return;
+		
+		if (!Config.revive)
+			return;
+		
+		player.startAutoReviveTask();
 	}
 	
 	@Override

 

 

The player instance now will handle the next actions by itself.

The concept is:

  • Before start the task scheduler, you should check if the speficic scheudler is already running.
  • When the scheduler fires the runnable, you should just check if the player is dead or not.
  • If the player will be revived without the auto revive task, just cancel the auto revive.

So,

 

Index: head-src/com/l2jfrozen/gameserver/model/actor/instance/L2PcInstance.java
===================================================================
@@ -15415,6 +15469,7 @@
 	public void doRevive()
 	{
 		super.doRevive();
+		resetAutoReviveTask();
 		updateEffectIcons();
 		sendPacket(new EtcStatusUpdate(this));
 		_reviveRequested = 0;

@@ -19644,4 +19705,41 @@
 		_currentPetSkill = new SkillDat(currentSkill, ctrlPressed, shiftPressed);
 	}
 	
+	// The task
+	private ScheduledFuture<?> _autoReviveTask = null;
+	
+	public void startAutoReviveTask()
+	{
+		// Before initiate the auto revive task, check if another scheduler is active
+		resetAutoReviveTask();
+		
+		// Start the task
+		_autoReviveTask = ThreadPoolManager.getInstance().scheduleGeneral(() -> doAutoRevive(), TimeUnit.SECONDS.toMillis(Config.revive_delay));
+	}
+	
+	private void resetAutoReviveTask()
+	{
+		// If is not running, do nothing
+		if (_autoReviveTask == null)
+			return;
+		
+		_autoReviveTask.cancel(true);
+		_autoReviveTask = null;
+	}
+	
+	private void doAutoRevive()
+	{
+		// Check for any possible scenario if the player is alive
+		if (!isDead())
+			return;
+		
+		doRevive();
+		heal();
+		teleToLocation(Rnd.get(Config.spawn_loc), false);
+	}
+	
+	private void heal()
+	{
+		// Heal the instance
+	}

 

 

And the last thing, get the Rnd#get which is generic from aCis sources which is returning a random element of the given list class as parameter.

 

Index: head-src/com/l2jfrozen/util/random/Rnd.java
===================================================================
--- head-src/com/l2jfrozen/util/random/Rnd.java	(revision 1118)
+++ head-src/com/l2jfrozen/util/random/Rnd.java	(working copy)
@@ -23,7 +23,19 @@
  */
 public final class Rnd
 {
+	
+ 	/**
+	 * Returns a randomly selected element taken from the given array.
+	 * @param <T> type of array elements.
+	 * @param array an array.
+	 * @return a randomly selected element.
+	 */
+	public static final <T> T get(T[] array)
+	{
+		return array[get(array.length)];
+	}
+	

 

With this version of Rnd#get, you can do this:

teleToLocation(Rnd.get(Config.spawn_loc), false);

instead of 

int[] loc = Config.spawn_loc[Rnd.get(Config.spawn_loc.length)];
teleToLocation(loc[0]+Rnd.get(-Config.radius,Config.radius), loc[1]+Rnd.get(-Config.radius,Config.radius), loc[2]);

 

Edited by melron
  • 0
Posted

Store this runnable into a ScheduledFuture<?> . Let's say you call this reviveTask. Upon Player#doRevive call you should cancel this task.

 

if (reviveTask != null)
{
reviveTask.cancel(false);
reviveTask = null;
}

  • 0
Posted (edited)
7 hours ago, Zake said:

Store this runnable into a ScheduledFuture<?> . Let's say you call this reviveTask. Upon Player#doRevive call you should cancel this task.

 

if (reviveTask != null)
{
reviveTask.cancel(false);
reviveTask = null;
}

like that?

 

Spoiler

public class L2PartyEventZone extends L2ZoneType
{
    
    public L2PartyEventZone (final int id)
    {
        super (id);
    }
+    protected ScheduledFuture<?> reviveTask;

 


 

 

        @Override
        public void onDieInside(final L2Character character)
        {
            if (character instanceof L2PcInstance)
            {
                final L2PcInstance activeChar = ((L2PcInstance) character);
    if(Config.revive)
                {

-                ThreadPoolManager.getInstance().scheduleGeneral(new Runnable()
+               reviveTask = ThreadPoolManager.getInstance().scheduleGeneral(new Runnable()
                    {
                        @Override
                        public void run()
                        {
                           activeChar.doRevive();
+                           if (reviveTask != null)
+                            {
+                            reviveTask.cancel(false);
+                            reviveTask = null;
+                            }
                            heal(activeChar);

 

Edited by Irrelevant
  • 0
Posted (edited)

No, not really. At first , fields should be private in most cases. Furthermore, upon death (method onDieInside in your file) you should say something like

 

if (reviveTask == null)

reviveTask == ThreadPoolManager.getInstance().scheduleblabla()

 

Also, as i already mentioned above. You should cancel the task inside the method doRevive(L2PcInstance.java)

Edited by Zake
  • 0
Posted (edited)
1 hour ago, Zake said:

No, not really. At first , fields should be private in most cases. Furthermore, upon death (method onDieInside in your file) you should say something like

 

if (reviveTask == null)

reviveTask == ThreadPoolManager.getInstance().scheduleblabla()

 

Also, as i already mentioned above. You should cancel the task inside the method doRevive(L2PcInstance.java)

like that in l2PcInstance?

Spoiler

 

 

    /** The _donator. */
    private boolean _donator = false;
    
+    /**Auto Revive*/
+    public ScheduledFuture<?> reviveTask;

 

 

 

@@@

 

 

 

 

    @Override
    public void doRevive()
    {
        super.doRevive();
        updateEffectIcons();
        sendPacket(new EtcStatusUpdate(this));
        _reviveRequested = 0;
        _revivePower = 0;
        
+        if (isInsideZone(L2Character.ZONE_PARTYEVENT))
+                        
+                        if (reviveTask != null)
+                        {
+                        reviveTask.cancel(false);
+                        reviveTask = null;
+                       }
+                        doRevive();
+        }

 

 

 

and in zone like that? 

Spoiler

public class L2PartyEventZone extends L2ZoneType
{
    
    public L2PartyEventZone (final int id)
    {
        super (id);
    }
+    private ScheduledFuture<?> reviveTask;

 


 

 

        @Override
        public void onDieInside(final L2Character character)
        {
            if (character instanceof L2PcInstance)
            {
                final L2PcInstance activeChar = ((L2PcInstance) character);
    if(Config.revive)
                {

-                ThreadPoolManager.getInstance().scheduleGeneral(new Runnable()

+               if (reviveTask == null)
+               reviveTask = ThreadPoolManager.getInstance().scheduleGeneral(new Runnable()
                    {
                        @Override
                        public void run()
                        {
                           activeChar.doRevive();
                            heal(activeChar);



NOPE, i tried it! :/ 

Edited by Irrelevant
  • 0
Posted

reviveTask should be linked with players so you have to store this in L2PcInstance and not random classes. Also you don't need to check if a player is in a custom zone in doRevive() method, all you need is to cancel revive task.

  • 0
Posted (edited)
2 hours ago, melron said:

You don't have to code anything inside the zone's method since the feature is about the player instance. You could make a manager to handle all these actions but this is just another case.

 

 

 

 

 

 

DUDE <3 . I dont have words to thank you!! Awesome  for 1 more time!!!!!! THANK YOU! :hug
 

Edited by Irrelevant
Guest
This topic is now closed to further replies.


  • Posts

    • Lineage2Dex x25 is opening on October 9! We are excited to announce the launch of our new Interlude x25 server, designed for players who want a balanced, competitive, and long-term Lineage 2 experience. If you are looking for a server with an active community, stable environment, and a serious project behind it, this is the perfect time to join us. Server Information Project: Lineage2Dex Chronicle: Interlude Rates: x25 Opening Date: October 9 Type: Mid Rate Platform: Stable and optimized gameplay Focus: PvP, progression, competitive environment, long-term gameplay Why join Lineage2Dex x25? Well-known and trusted project Smooth and optimized gameplay Balanced progression Competitive PvP environment Active community Serious administration and continuous support Important Dates PTS Available: Until October 5 Beta Starts: October 6 Official Launch: October 9 This is your chance to prepare early, test the server, and be ready for launch day. Join Us Website: https://lineage2dex.com⁠
    • Today I would like to introduce a new set of tools developed entirely from scratch in Java, designed to simplify and modernize one of the most important tasks for any online server: distributing, updating, and maintaining the game client quickly, securely, and efficiently. The system has been designed to work with Lineage II, Aion, World of Warcraft, or any other project that requires a file distribution and update system, providing a simple solution for both players and administrators.   The entire project features a modern dark-mode interface, is completely separated into individual tools, and is distributed as standalone Windows executables (.exe) using Launch4j.   1. GameLauncher: The Player Client     GameLauncher is the launcher used by players on their computers. Its goal is to make keeping the game client up to date a completely automatic and transparent process.   Smart Updates: Automatically compares local files with the remote server using a manifest file (manifest.json) Hash-Based Integrity: Calculates file hashes to download only new or modified files, saving time and bandwidth. Real-Time Downloads: Detailed progress bar with transfer speed and automatic ZIP package extraction. Standalone: Packaged into a single .exe with Java 17 requirement validation and automatic redirection if the required environment is not installed.   Source code: https://gitlab.com/u3games/GameLauncher   2. L2Compiler: The Administrator Tool     L2Compiler is the tool designed for server administrators and developers. It allows updates to be prepared and published quickly, automating much of the process that would otherwise have to be performed manually.   Mass Packaging: Select the root folder of your development client and automatically generate optimized compressed packages ready for distribution. Automatic Manifest Generation: Instantly generates the manifest.json file with all the required metadata, including file sizes, paths, and hashes, using Gson. Preference Management: Automatically saves the last used paths through java.util.prefs to speed up everyday development tasks. Asynchronous Interface: Background processing through SwingWorker to prevent the interface from freezing during heavy operations.   Source code: https://gitlab.com/u3games/GameCompiler   A System Designed for Online Servers   The idea behind this project is simple: the administrator prepares an update using L2Compiler, and the player receives it automatically through GameLauncher. This allows both tools to work together and provide a simple update workflow:   Development Client → L2Compiler → Server → GameLauncher → Updated Client   There is no need for players to manually search for files, download patches one by one, or go through complicated installation processes. Although the system was initially designed with projects such as Lineage II, Aion, and World of Warcraft in mind, it is not tied to any specific game. If your project needs to distribute files and keep its clients up to date, it can be easily adapted to fit your needs.   Open Source for the Community   This project was created by me for the U3Games community, with the goal of providing a modern, simple, and reusable alternative for managing updates across our servers. The source code is publicly available so that other developers can study it, adapt it, improve it, and contribute to the project.     Have a Suggestion, Found a Bug, or Want to Contribute?   Any suggestions, bug reports, improvements, or contributions are more than welcome. The goal is to continue evolving the project together with the community and turn it into an increasingly complete tool for all kinds of online servers and projects.
    • Let's do 1 for share for people? Which one? 
    • A 100-YEAR-OLD ORDERED A FLAGSHIP AND PASSED THE VIDEO CALL 🚓 Spanish police took down a gang that found a hole in a major telecom operator's online store. A script told the warehouse to ship before payment went through. The haul: over 150 smartphones worth more than €50,000. The cover was a farm of borrowed identities: documents of around fifty people, including 100-year-old pensioners. They used them to open bank accounts, register phone numbers and send parcels across the country. The cherry on top: gang members passed video KYC themselves, posing as the elderly document holders. The "customer's" age didn't bother the antifraud. Operation Sakosita: seven arrested in Madrid, the alleged ringleader caught in Italy on a European arrest warrant. Meanwhile, the frozen accounts and someone else's debts land on the people whose names were used. 🔒 Account locked because someone opened something in your name? Message us – we'll gather the evidence and see the unlock through. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #kyc #photoshop #unban #news
    • he did it for me    thanks you 😄  some of that bones is broken is some pets or is not exist so is better to buy some from the clientDev: @NevesOma
  • 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..