Jump to content
Encoded

Task Framework Tutorial

Recommended Posts

Posted (edited)

Task Framework

A set is a collection that contains no duplicate elements.
The task framework is a sorted set of tasks where each task performs a specific action.
Tasks are sorted in descending order by priority.

Each task has a validate and execute method. The validate method returns a boolean that decides whether or not the task should execute. The execute method should be called when the validate method returns true.

Priority determines which task will be returned by the getValidTask method if two or more tasks' validate methods are to return true.
If you find yourself having two tasks' validate methods returning true with the same priority level, add additional priority levels or modify the tasks' validate methods.

TaskSet is the aggregate of all the tasks. Tasks are sorted upon being added to the set. The getValidTask method returns the highest priority task with a validate method that returns true or null if no task is valid.

Don't forgot to change the packaging if you are copy/pasting the following code.

Task.java
package scripts.api.script.frameworks.task;

public interface Task {

    Priority priority();

    boolean validate();

    void execute();

}
Priority.java
package scripts.api.script.frameworks.task;

public enum Priority {

    HIGH,
    MEDIUM,
    LOW,
    NONE

}
TaskSet.java
package scripts.api.script.frameworks.task;

import java.util.Arrays;
import java.util.Collection;
import java.util.Comparator;
import java.util.List;
import java.util.TreeSet;

public class TaskSet extends TreeSet<Task> {

    public TaskSet() {
        super(Comparator.comparing(Task::priority).thenComparing(Comparator.comparing(task -> task.getClass().getName())));
    }

    public TaskSet(Task... tasks) {
        super(Comparator.comparing(Task::priority).thenComparing(Comparator.comparing(task -> task.getClass().getName())));
        addAll(tasks);
    }

    public TaskSet(Comparator<? super Task> comparator) {
        this();
    }

    public TaskSet(Collection<? extends Task> c) {
        this(c.toArray(new Task[c.size()]));
    }

    public TaskSet(SortedSet<Task> s) {
        this(s.toArray(new Task[s.size()]));
    }

    public boolean addAll(Task... tasks) {
        return super.addAll(Arrays.asList(tasks));
    }

    public Task getValidTask() {
        for (Task task : this) {
            if (task.validate()) {
                return task;
            }
        }
        return null;
    }

}
Example Task
public class ExampleTask implements Task {

    @Override
    public String toString() {
        return "Example Task";
    }

    @Override
    public Priority priority() {
        return Priority.LOW;
    }

    @Override
    public boolean validate() {
        return false;
    }

    @Override
    public void execute() {

    }
    
}
Example Script run Method
@Override
public void run() {
    TaskSet tasks = new TaskSet(new ExampleTask());
    while (isRunning) {
        Task task = tasks.getValidTask();
        if (task != null) {
            status = task.toString();
            task.execute();
        }
    }
}
Edited by Encoded
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

@Encoded So can you tell me how much stuff you should include in each task? Because it seems counter-intuitive to do a new task for every small action if your script is big.

So for example if I want my script to wc and bank before doing another task that could be a quest or other skill. 

I can include my whole wcing/banking code in a single task?

Or should I spread my wcing into various tasks. (one for walking, one for cutting, one for banking)

 

Share this post


Link to post
Share on other sites
5 hours ago, Enano25 said:

@Encoded So can you tell me how much stuff you should include in each task? Because it seems counter-intuitive to do a new task for every small action if your script is big.

So for example if I want my script to wc and bank before doing another task that could be a quest or other skill. 

I can include my whole wcing/banking code in a single task?

Or should I spread my wcing into various tasks. (one for walking, one for cutting, one for banking)

 

I would separate walking, banking, and wcing into 3 tasks. They each need to be done when different conditions are met, and should be assigned different priorities based on the conditions met.

 

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, Azuz53487 said:

Wasn't this posted somewhere? Can't remember where I saw it.

I had it in the snippets section, but I rewrote it and moved it to tutorials since that's where the other frameworks are posted.

 

7 hours ago, Enano25 said:

@Encoded So can you tell me how much stuff you should include in each task? Because it seems counter-intuitive to do a new task for every small action if your script is big.

So for example if I want my script to wc and bank before doing another task that could be a quest or other skill. 

I can include my whole wcing/banking code in a single task?

Or should I spread my wcing into various tasks. (one for walking, one for cutting, one for banking)

You can break it down as much as you want. I've even made scripts where a Task will have its own TaskSet within it.
If you want to chain TaskSets together, I suggest adding a stopping condition and then creating a linked list of TaskSets so that you can get the next TaskSet once the current's stopping condition is met. That's what I currently do, but this post is about the basics so I didn't include that.

Edited by Encoded
  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, Encoded said:

I had it in the snippets section, but I rewrote it and moved it to tutorials since that's where the other frameworks are posted.

 

You can break it down as much as you want. I've even made scripts where a Task will have its own TaskSet within it.
If you want to chain TaskSets together, I suggest adding a stopping condition and then creating a linked list of TaskSets so that you can get the next TaskSet once the current's stopping condition is met. That's what I currently do, but this post is about the basics so I didn't include that.

Aha, I see! Great! :)

Share this post


Link to post
Share on other sites

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

  • Our picks

    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 21 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×