[PI] Run Energy Out of Process

**Our Promise** · 08-07-2014, 10:44 PM

I know most of you pi users use this as your run energy alternative [Only registered and activated users can see links. ]

which uses process, so i thought id convert it to a task for ya to help you yet again remove something out of process and hopefully help you understand that there are always alternatives than just throwing things in process

Code:

package com.divine.fate.main.cycle.event;

import com.divine.fate.main.cycle.CycleEvent;
import com.divine.fate.main.cycle.CycleEventContainer;

import game.model.entity.players.Player;

public class RunEnergyTask extends CycleEvent {
	
	private Player player;
	
	public RunEnergyTask(Player player) {
		this.player = player;
	}

	@Override
	public void execute(CycleEventContainer container) {
		if (player.playerEnergy == 100 || player.playerEnergy > 100) {
			container.stop();
		}
		if (player.playerEnergy < 100 && !player.isRunning()) {
			if (System.currentTimeMillis() > player.getPA()
					.getAgilityRunRestore() + player.lastRunRecovery) {
				player.playerEnergy++;
				player.lastRunRecovery = System.currentTimeMillis();
				player.getPA().sendFrame126(player.playerEnergy + "%", 149);
			}
		}
	}

	@Override
	public void stop() {
		player.playerEnergy = 100;
	}
	
}

now just call the task under where you have this declared, runEnergy--;

**Bow** · 08-07-2014, 10:56 PM

Nice release there.

**Karma_K** · 08-08-2014, 01:03 AM

Forgot, you'll also need to call this in initialize() or whenever the player logs in

**Anneliese** · 08-08-2014, 07:04 AM

thanks for the share

**Rhubarb** · 08-08-2014, 11:44 AM

You also need to check whether the player has been disconnected or not, otherwise the event will just run. Like so:

Code:

		if (player.playerEnergy == 100 || player.playerEnergy > 100 || player.disconnected) {
			container.stop();
		}

**~~lare96~~** · 08-09-2014, 09:25 AM

Originally Posted by Rhubarb

You also need to check whether the player has been disconnected or not, otherwise the event will just run. Like so:

Code:

		if (player.playerEnergy == 100 || player.playerEnergy > 100 || player.disconnected) {
			container.stop();
		}

iirc even pi has support for attaching objects to tasks so checking is not needed, all tasks with the attached player will be stopped automatically when the player logs out

he doesn't seem to be attaching the player instance though lol

**Our Promise** · 08-09-2014, 05:55 PM

Originally Posted by lare96

iirc even pi has support for attaching objects to tasks so checking is not needed, all tasks with the attached player will be stopped automatically when the player logs out

he doesn't seem to be attaching the player instance though lol

I'm not sure what you're meaning by me not attaching the player instance. I am currently calling it as

CycleEventContainer.getSingleton().addEvent(this, new RunEnergyTask(this), 1);

The first this is in the field of where you specify the object owner, is it not?

**~~lare96~~** · 08-09-2014, 07:25 PM

Originally Posted by Our Promise

I'm not sure what you're meaning by me not attaching the player instance. I am currently calling it as

CycleEventContainer.getSingleton().addEvent(this, new RunEnergyTask(this), 1);

The first this is in the field of where you specify the object owner, is it not?

well I'm not sure how the Object attachments work in PI, but yeah if it's like that then you are attaching the player instance

Thread: [PI] Run Energy Out of Process

Thread Tools

Thankful user:

Thankful user:

Thankful user:

Thankful user:

Users Browsing this Thread

User Tag List

Similar Threads

[PI] Prayer reducing out of process

[PI] Prayer reducing out of process

Cleaning things out of process[PI]

[PI]Spawn npc out of a chest on click

[PI] People teleporting out of duel arena