Signup Now
Page 1 of 2 12 LastLast
Results 1 to 10 of 17
  1. #1
    Free User Cisco's Avatar
    Join Date
    Aug 2014
    Location
    Brazil
    Posts
    1,424
    Reputation
    119
    Rep Power
    23

    Use waypoint proceeds too quickly to the next

    1. What OS you are at?
    Windows 10 Home

    2. Real PC or VPS?
    Real PC

    3. Using WindAddons? Which version?
    Yes windaddon, yes fast hotkeys

    4. Which version of WindBot?
    beta 33

    5. Which version of Game Client?
    11.03.4221

    6. Do you have a Dedicated Graphics Card?
    Yes, Radeon R9 200 series

    7. Detailed description of the problem.
    Gif

    8. If applicable, a GIF of the action hosted on imgur.com.


    9. Debug Log.
    http://pastebin.com/hfMpfRzA (Log events, Log cavebot, Details and Scripts)

    10. Comments.
    Unable to use script unless you change the "use"

    Test 1:
    Keyboard:
    Type wait: 40 to 90 ms
    Press wait: 40 to 90 ms
    Mouse:
    Click wait: 30 to 70 ms
    ------------------------------
    Test 2:
    Keyboard:
    Type wait: 90 to 90 ms
    Press wait: 90 to 90 ms
    Mouse:
    Click wait: 90 to 90 ms
    ===========

    Action 34: return sqm 32 use

    wait(600,700)
    if not islocation(1) then
    gotolabel($wptid-2) end


    Stand 33 and action 34, near npc

    @RoxZin xD Did you have that same problem too? /// Você também teve esse mesmo problema?

  2. #2
    Free User Akiller's Avatar
    Join Date
    Aug 2015
    Posts
    240
    Reputation
    33
    Rep Power
    18
    @Cisco
    turn use to action and paste it
    usedoor($wptx,$wpty,$wptz, 'open')

    and change ur control action to this
    wait(600,700)
    if not islocation(1) then
    if tilereachable(33010,31535,10) then
    reachlocation(33010,31535,10)
    else
    gotolabel($wptid-2)
    end
    end

    it may fix ur issue
    Last edited by Akiller; 12-16-2016 at 12:26 PM.

  3. #3
    Free User Cisco's Avatar
    Join Date
    Aug 2014
    Location
    Brazil
    Posts
    1,424
    Reputation
    119
    Rep Power
    23
    Quote Originally Posted by Akiller View Post
    @Cisco
    turn use to action and paste it
    usedoor($wptx,$wpty,$wptz, 'open')

    and change ur control action to this
    wait(600,700)
    if not islocation(1) then
    if tilereachable(33010,31535,10) then
    reachlocation(33010,31535,10)
    else
    gotolabel($wptid-2)
    end
    end

    it may fix ur issue
    The problem is not fixing the problem. Fix the problem I know, the point is that it works normal on wind 10 and on wind 11 not.

  4. #4
    Free User downloadkct's Avatar
    Join Date
    Dec 2013
    Location
    Rio de Janeiro
    Posts
    1,167
    Reputation
    25
    Rep Power
    23
    edited, not interested on sharing or helping anymore
    Last edited by downloadkct; 02-17-2017 at 02:15 PM.
    Old 'n Proud Neobot-Elfbot and blackd user

  5. #5
    Moderator RoxZin xD's Avatar
    Join Date
    Dec 2013
    Location
    Rio de Janeiro
    Posts
    4,914
    Reputation
    109
    Rep Power
    31
    I didn't actually try any of the Farmine scripts w/ Tibia 11. That looks really weird though, it should work normally.



    Troubled Animals Quest [100+]
    ALL
    Feyrist Animals Surface [160+]
    RP
    Feyrist Silencers Underground X1 [180+]
    RP | EK
    Feyrist Silencers Underground X2 [200+]
    RP | EK
    Feyrist Silencers Surface [210+]
    RP | EK
    Rathleton Sewers [240+]
    RP
    Glooth Fairy [350+]
    ED/MS
    Hardcore Draken Walls [400+]
    EK

  6. #6
    Free User Cisco's Avatar
    Join Date
    Aug 2014
    Location
    Brazil
    Posts
    1,424
    Reputation
    119
    Rep Power
    23
    Quote Originally Posted by downloadkct View Post
    Did you try to add a wait after the use waypoint ?
    I always add a wait(500,1000) after a door or machine waypoint, if i dont i sometimes get stuck just like you did, using windbot10
    Action 34: return sqm 32 use

    wait(600,700)
    if not islocation(1) then
    gotolabel($wptid-2) end


    Stand 33 and action 34, near npc

    32 (Use) > 33 (Stand) near npc > 34 (Action) near 33 and near npc

  7. #7
    Free User downloadkct's Avatar
    Join Date
    Dec 2013
    Location
    Rio de Janeiro
    Posts
    1,167
    Reputation
    25
    Rep Power
    23
    No, not that, i mean wait time right after the door use waypoint
    wp1- Use (the door waypoint)
    wp2- Wait(500,1000)
    wp3- Stand (near npc)
    wp4- islocation Action
    Old 'n Proud Neobot-Elfbot and blackd user

  8. #8
    Wind Tester
    Join Date
    Dec 2013
    Location
    Warsaw, Poland
    Posts
    2,579
    Reputation
    149
    Rep Power
    27
    This is weird indeed, but i would recommend to use usedoors() and waypoints like:
    1. stand before doors
    2. action with usedoor()
    3. stand after doors
    4. islocation

  9. #9
    Moderator Raphael's Avatar
    Join Date
    Dec 2013
    Location
    raphseller.com
    Posts
    2,441
    Reputation
    309
    Rep Power
    28
    @Cisco

    I'm pretty sure this was a problem when we made the transition Elf -> Neo or Neo -> Wind. I remember at the time, since backwards compatibility wasn't a major concern, we decided to keep it this way.

    Are you absolutely sure this worked with WindBot 10? On this same world? On this same character? On this same place? With the same ping? Using this same script?

  10. #10
    Free User Cisco's Avatar
    Join Date
    Aug 2014
    Location
    Brazil
    Posts
    1,424
    Reputation
    119
    Rep Power
    23
    Quote Originally Posted by Raphael View Post
    @Cisco

    I'm pretty sure this was a problem when we made the transition Elf -> Neo or Neo -> Wind. I remember at the time, since backwards compatibility wasn't a major concern, we decided to keep it this way.

    Are you absolutely sure this worked with WindBot 10? On this same world? On this same character? On this same place? With the same ping? Using this same script?
    Yes. I've been using this script for 3 or 4 months and it's always worked that way. I own 3 roxzin scripts from farmine and they work that way, and they always worked. This error is only happening on these normal ports, those requiring a quest or level are normal.
    If you want I can download client 10 and wind 10 and play as it would in wind 10, but I guarantee it always worked. Because if I stayed like this in the picture I would not have put a character from level 130 up to 217 as in the picture.

    But if need be I can play and record with wind 10

    /////

    Sim. Eu uso esse roteiro já faz 3 ou 4 meses e sempre funcionou dessa forma. Eu possuo 3 roteiros do Roxzin de farmine e funcionam dessa maneira, e sempre funcionaram. Esse erro está acontecendo somente nessas portas normais, as que necessitam de quest ou nível estão normais.
    Se quiser posso baixar o client 10 e o wind 10 e reproduzir como seria no wind 10, mas garanto que sempre funcionou. Porque se ficasse desse modo como na imagem eu não teria colocado um personagem do nível 130 até 217 como na imagem.

    Mas se houver necessidade posso reproduzir e gravar com o wind 10

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •