Wednesday, 6 February 2019

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.

9 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