1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

  2. RuneMate 2.0 Spectre

    Announcement
    RuneMate 2.0 Spectre Released
    Walkthrough
    How to Use Spectre
    Get Help
    Client & Site Support
Cookies RuneMate Spectre 2.0 Released

Resolved RS3 Webpath broken in Fally

Discussion in 'Client & Site Support' started by Wet Rag V2, May 1, 2018.

  1. Wet Rag V2

    Wet Rag V2

    Joined:
    Nov 18, 2017
    Messages:
    55
    Likes Received:
    8
    00:05:39 DEBUG Timed action (WebPath#getNext()) took 846ms
    00:05:39 DEBUG [WebPath] getNext() returned null.


    Happens in fally area.
    --- Double Post Merged, May 3, 2018, Original Post Date: May 1, 2018 ---
    Anyone?
     
    #1 Wet Rag V2, May 3, 2018
    2. Best Answer:
    Post #2 by Derk, May 4, 2018
  2. Derk

    Derk 12 year old normie

    Joined:
    Jan 8, 2015
    Messages:
    2,766
    Likes Received:
    1,339
    This is a bot related issue. Post on the bot thread corresponding with the bot you've used that outputs this debug line.
     
    #2 Derk, May 4, 2018
  3. EthanOpia

    EthanOpia

    Joined:
    Aug 25, 2017
    Messages:
    272
    Likes Received:
    34
    It isn't a code issue. It worked fine for a month until a Runemate update. It isn't using a stale webpath. Seems to be a broken spot in the web.
     
    #3 EthanOpia, May 4, 2018
(You must log in or sign up to post here.)

Share This Page

Loading...