Jump to content
Sign in to follow this  
helloworldlol1

Pathing for barrows

Recommended Posts

You can write custom paths for it.


Alternatively you might be able override the DPathNavigator's door cache in the tunnels with all the doors that have an 'Open' action. I think the override only works for findPath though, so you'll need to handle the walking yourself. I haven't tested this but in theory it might work.

Share this post


Link to post
Share on other sites
26 minutes ago, laniax said:

You can write custom paths for it.


Alternatively you might be able override the DPathNavigator's door cache in the tunnels with all the doors that have an 'Open' action. I think the override only works for findPath though, so you'll need to handle the walking yourself. I haven't tested this but in theory it might work.

 

I don't think DPathNavigator detects any of the doors, which is the problem. I think it may have something to do with the minimap being blacked out and it thinks it's not in a loaded region, or something.

I definitely do not look forward to writing the custom paths myself haha.

 

@Assume @wussupwussup any ideas?

Edited by helloworldlol1

Share this post


Link to post
Share on other sites

Also what does the areas parameter mean in this PathFinding method? Like certain areas of the screen or...? So far this has been the only method that produced a path when called in the barrows tunnels, but it stays in the region where it's enclosed by doors (AKA it doesn't open them). But at least it produced something.

 

Quote
public static boolean aStarWalk(Positionable position,
                                boolean minimap,
                                java.awt.Polygon[] areas)
Using A* path finding to walk to the specified tile. Stays within the specified areas.
Parameters:
position - The tile to walk to.
areas - The areas the path finding algorithm must stay in.
minimap - True for minimap walking. False for on-screen walking.
Returns:
True if the 'end' tile was reached; false otherwise.

 

Share this post


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

Also what does the areas parameter mean in this PathFinding method? Like certain areas of the screen or...? So far this has been the only method that produced a path when called in the barrows tunnels, but it stays in the region where it's enclosed by doors (AKA it doesn't open them). But at least it produced something.

It's not that hard to write a function which walks an RS path, and opens doors if need be...

Every tile see if next tile is reachable. 

If it's not, then check for a door and open it, otherwise continue.

Share this post


Link to post
Share on other sites
1 hour ago, Worthy said:

It's not that hard to write a function which walks an RS path, and opens doors if need be...

Every tile see if next tile is reachable. 

If it's not, then check for a door and open it, otherwise continue.

 

Yes you're right it's not hard to walk a path and open a door. I think the main challenge was just generating the path when half of the pathing classes don't work in barrows. I only wanted to see if someone had already wrote it before I did.

Share this post


Link to post
Share on other sites
1 minute ago, helloworldlol1 said:

 

Yes you're right it's not hard to walk a path and open a door. I think the main challenge was just generating the path when half of the pathing classes don't work in barrows. I only wanted to see if someone had already wrote it before I did.

Only web walking should fail at barrows, the rest of the pathing/walking methods should work fine if you use them correctly

Share this post


Link to post
Share on other sites
1 minute ago, Flamo353 said:

Only web walking should fail at barrows, the rest of the pathing/walking methods should work fine if you use them correctly

 

It's not that they're broken or I'm using them incorrectly, it's just I guess I kinda expected the classes would be able to generate the a path from me to the chest, and it would traverse it no problem as the only thing in the way are doors, which the classes claim to be able to navigate. While it still wasn't really that complicated, there's definitely something weird with DPathNavigator in barrows.

 

Share this post


Link to post
Share on other sites
7 hours ago, helloworldlol1 said:

 

I don't think DPathNavigator detects any of the doors, which is the problem. I think it may have something to do with the minimap being blacked out and it thinks it's not in a loaded region, or something.

I definitely do not look forward to writing the custom paths myself haha.

 

@Assume @wussupwussup any ideas?

that's why you override the door cache, so it will use the doors u specify.

  • Like 1

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  

  • Our picks

    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 28 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Thanks
        • Like
      • 38 replies
    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 33 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
        • Thanks
        • Like
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×