Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
RoboSalmon

DynamicClicking.click stuck?

Recommended Posts

I've tried to set up a thieving script using

println("about to click");

DynamicClicking.clickRSObject(fruitStall, 1);

println("clicked");

It will click correctly nearly every time but after a few minutes, it will always enter this function and never leave it.

I've used different clicking methods to try and get around it and i've set up checks for everything. Has anyone experienced anything similar or have anything i can read to learn more about why its occurring. Any general coding tips for if i run into similar problems in the future would also be appreciated as i'm pretty new to this, big fan of the site, thanks.

Share this post


Link to post
Share on other sites

How do i do that? I've put it in this try-catch to see if i can see it but same problem, it just enters the click method and never leaves. Thanks a bunch for the help so far!

try{
                        DynamicClicking.clickRSObject(fruitStallFound, 1);
                    }
                    catch(Exception e) {
                        e.printStackTrace();
                        println("some lmao");
                    }
                    println("trycatch complete");

 

Share this post


Link to post
Share on other sites

if it helps this is the last thing to occur in the bot debug 

  • [15:34:17] java.lang.NumberFormatException: For input string: "Fruit Stall"
  • [15:34:17] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
  • [15:34:17] at java.lang.Integer.parseInt(Integer.java:580)
  • [15:34:17] at java.lang.Integer.parseInt(Integer.java:615)
  • [15:34:17] at obf.HE.run(of:1159)
  • [15:34:17] at java.lang.Thread.run(Thread.java:748)

 

Share this post


Link to post
Share on other sites

Apologies im new here, got it:

  • [15:46:37] Script Stack Trace:
  • [15:46:37] java.lang.Thread.sleep(Native Method)
  • [15:46:37] obf.Rc.gc(lc:97)
  • [15:46:37] obf.LF.vC(nm:96)
  • [15:46:37] obf.re.NH(sk:994)
  • [15:46:37] obf.re.Xh(sk:411)
  • [15:46:37] org.tribot.api.DynamicClicking.clickRSModel(mg:995)
  • [15:46:37] org.tribot.api.DynamicClicking.clickRSObject(mg:380)
  • [15:46:37] scripts.Thieve1.thieve25(Thieve1.java:263)
  • [15:46:37] scripts.Thieve1.run(Thieve1.java:64)
  • [15:46:37] java.lang.Thread.run(Thread.java:748)

Share this post


Link to post
Share on other sites
15 hours ago, RoboSalmon said:

Apologies im new here, got it:

  • [15:46:37] Script Stack Trace:
  • [15:46:37] java.lang.Thread.sleep(Native Method)
  • [15:46:37] obf.Rc.gc(lc:97)
  • [15:46:37] obf.LF.vC(nm:96)
  • [15:46:37] obf.re.NH(sk:994)
  • [15:46:37] obf.re.Xh(sk:411)
  • [15:46:37] org.tribot.api.DynamicClicking.clickRSModel(mg:995)
  • [15:46:37] org.tribot.api.DynamicClicking.clickRSObject(mg:380)
  • [15:46:37] scripts.Thieve1.thieve25(Thieve1.java:263)
  • [15:46:37] scripts.Thieve1.run(Thieve1.java:64)
  • [15:46:37] java.lang.Thread.run(Thread.java:748)

Get the code block that includes line 263 from thieve1 class and print the whole method here. 

Share this post


Link to post
Share on other sites

263 is DynamicClicking.clickRSObject(fruitStallFound, 1);

its part of

            case 2: // walked to stall, located stall
                
                General.sleep(abc_util.generateReactionTime());

                if(Inventory.isFull() == true) {
                    STATUS = 3;
                    break;
                } 
                RSObject[] fruitStall = Objects.find(4, fruitStallNo);
                if(fruitStall.length > 0) {
                    RSObject fruitStallFound = fruitStall[0];
                    println("about to click");
263 ->         DynamicClicking.clickRSObject(fruitStallFound, 1);
                    println("clicked");
                }
                break;

Do you want the whole thing? the rest is just two more cases of a switch statement and a DaxWalker initialization. Thanks for the response

Share this post


Link to post
Share on other sites
On 2/12/2019 at 3:56 AM, RoboSalmon said:

263 is DynamicClicking.clickRSObject(fruitStallFound, 1);

its part of

            case 2: // walked to stall, located stall
                
                General.sleep(abc_util.generateReactionTime());

                if(Inventory.isFull() == true) {
                    STATUS = 3;
                    break;
                } 
                RSObject[] fruitStall = Objects.find(4, fruitStallNo);
                if(fruitStall.length > 0) {
                    RSObject fruitStallFound = fruitStall[0];
                    println("about to click");
263 ->         DynamicClicking.clickRSObject(fruitStallFound, 1);
                    println("clicked");
                }
                break;

Do you want the whole thing? the rest is just two more cases of a switch statement and a DaxWalker initialization. Thanks for the response

There is no need for you to use dynamicClicking. You can use:

 if(fruitstall[0].interact("Take")) {
	Wait condition here
	} 

Nvm. Forgot the interact method was from my own API. 

Edited by XmQ

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Our picks

    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 59 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



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

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



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

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 34 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...