Jump to content
Sign in to follow this  
Lambda

GraphScript Framework

Recommended Posts

Looking at the tutorials I didn't notice anyone using a graph-based framework, so I thought that either people hadn't thought of it or at least the newer or less experience programmers weren't aware of using this, so I thought I'd share it. GraphScript is a graph based framework, using a cyclical graph to model the functionality (where each vertex would be the same as a Node or Task from other frameworks) the advantage of this, is that when doing stuff that is rotational such as a skill or simple minigame (I use Wintertodt as an example, something like Hunter would be a fantastic example as well) then it makes sense to use something that more correctly models a human's behavior.

What do I mean by cyclical? Take a look at this flow chart I made for Wintertodt

 

td80EXy.png

 

To breakdown what is happening in the framework, the bottom section is the overlying framework. It decides whether to bank, or go play the minigame. This area also will potentially go into the wait functionality, if the game hasn't started yet but it doesn't need to bank.

 

The top section is a little more interesting, essentially the arrows are ways to traverse between eachother. So for example burn will never traverse back to fletch, fletch will never traverse back to chop. The advantage of this is that everything is self contained, you don't have to write code worrying about messing up the burn in the fletching class, since that'll be in its own section. For these simple cyclical things it makes everything much more self contained and easy to work with.

 

The downside is that you have to be more careful in your coding, if it gets stuck in the chopping class for example, while it's below the door outside of the minigame, the entire script is stuck. Typically it's pretty easy to avoid this happening, it just requires a little extra thought.

 

Here's the source code: https://github.com/Mkerian10/GraphScript

I re-wrote this on my pc so and I haven't ran through it so if anyone sees any issues lmk. Of course you don't (and probably shouldn't) directly copy this framework, but rather use the ideas to implement your own.

Share this post


Link to post
Share on other sites

I've done something similar using Suppliers that lead into other Suppliers to cause a dynamically ordered chain of events. I was gonna release the source on TRiBot but I never got around to it. I'll bookmark this for when I revisit the project.

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
Sign in to follow this  

  • Similar Content

    • By Worthy
      Node Framework Tutorial
      by Worthy
       
      What is Node Framework?
      A node based framework breaks actions into different classes.
      Each class extends a Node and has a validate and execute function.
       
      In this tutorial
      I will be writing a basic powerminer to demonstrate the effectiveness of using Nodes.
       
      ________
      Node class:

       
      Validate: if true, will run the execute method.
      Execute: where the action happens
       
      ________
      Second, we will plan and break down the actions we'll be creating.
      In a powerminer, there are really only a couple classes necessary:
      A GUI class (optional) A MineOre class A DropOre class Since this is a basic tutorial, I'm going to skip the GUI class
      And for simplicity's sake, I won't be externalizing any variables (I usually have separate classes for Constants and Variables).
       
      The MineOre class:

       
      ____
      The DropOre class:

       
      ____
      Lastly, the main class, PowerMiner:

       
       
      Tying everything together:
      When the script is initiated we add all the nodes we want into the ArrayList of nodes.
      The script then loops indefinitely, looping through each node in the ArrayList, validating it, and then executing.
       
      The min and max parameters I have set in the loop method, ensure the bot waits at least 20 to 40 milliseconds in between nodes.
       
      _________
      As you can see you can do much much more with a node-based framework, but this tutorial shows the barebone basics.
      For example: if you have an AIO script, you can have the GUI determine which nodes to add to the ArrayList. You can delete nodes to run if an action is completed, etc.
       
      Full script on GitHub: https://github.com/WorthyTRiBot/PowerMiner
       
       
       
      Regards,
      Worthy
  • Our picks

    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 23 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.

×