Update v1.43

2019-02-11: 16:13

Today between 10:30 and 16:00 there was a problem with ddos attack on my server provider.
Status back to normal, added 10h to each valid key. Sorry for problems.

Ascer

Added:
  • Support for Classicus.org new client (10% exp bonus). This client have problems with light so max light size is utevo lux.
  • Client validation checker to avoid crashing game after server update.
Changed:
  • [Medivia] Problem with reading container items due a incorrect $offset
  • [Realesta] Fixed crash reason for attack with new client.
  • [TibiaClient] Fixed reading map registry on Win 10 and added missing water tiles to fishing.
  • [GUI] Pannels: Lua, Advertising, Proxy & Loot will now display as child window without creating additional app on menu bar.
  • [Engine] Speed up engine, bot should works little bit faster now!
  • [Windows] Decreased chance to deleting Rifbot.exe due a pseudo "vir" detection.

26 comments:

  1. Hello i cant start rifbot im getting the a error

    Failed to start riftbot
    ERROR_CODE=2

    ReplyDelete
  2. Hello!

    It's a server provider problem, will be fixed soon.

    ReplyDelete
  3. Replies
    1. Works fine tested a minute ago. Sometimes private message proxy maybe bugged but this will fixed in next update.

      Delete
  4. Replies
    1. ahh this you want to know..
      I can't tell you because I don't have much time to test it all.
      I focus generally on Realesta where botting is ok, you need to test it personally. Timers for actions in bot are x2-3 solower than Realesta.

      Delete
  5. rifbot is not working, error_code=2
    co sie dzieje?

    ReplyDelete
  6. guy's what time i need to wait for key to using legally bot?

    ReplyDelete
  7. Problems with the server again?
    Error_code=2

    ReplyDelete
  8. Rift crashes everytime it advances on fishing skill and ml level and closes the tibia.

    ReplyDelete
  9. My client crashes every single time i open rift, cant figure out why. Any ideas? just started using today

    ReplyDelete
  10. Bot isnt working for me on Retrocores, client crashes once i login. any suggestions?

    ReplyDelete
  11. Failed to start riftbot
    ERROR_CODE=2

    am getting this error message and cannot open the bot. anyone know why?

    ReplyDelete
  12. No existe ninguna opciĆ³n o posibilidad de habilitar cavebot? No puedo botear (lvl), solo runear y es un poco limitado.

    ReplyDelete
  13. SOME LUA TO OPEN THE BACKPACK WHEN THE BLANKS RUNES END?

    ReplyDelete
  14. I would like to know if the cavebot is working in retrocores?

    ReplyDelete
  15. Hi there, when the bot is looting it opens and closes the dead body 5x without taking the loot.

    ReplyDelete
    Replies
    1. Hello,

      It happens due high ping (250ms+) to game server, try fix your internet now. In future update i'll update option walker->settings->Open Bp Delay (default 500) to accept also delay for opening dead bodies and you will able set it higher to don't bug while opening.

      Delete
    2. My ping is 43ms consistantly. it only happens if i have killed two monsters and it is trying to loot the second while the first body is still open

      Delete
    3. Looter is single loop function so it don't start loot next monster if first is not finished. Maybe you have some function/script enabled that make you exhausted example: UH or MF or LG (no items in bp) etc?

      Delete
    4. I don't havy any scripts excecuted and its not trying to uh or mf me. it comes up with this in the message box "Looter: ignore due max Open Tries"

      Delete
    5. Tell me then server name i'll check this.

      Delete
    6. Oh on Retrocores I botting since yesterday and no problem so guess it's your computer maybe. Did you try:
      Windows Defender -> Settings -> Real Time Protection -> disable

      Delete