RBAssist - Bot Scheduling and Crash Recovery

Get your trial key

Live community: https://discord.gg/s39XdMV

New user ? Check guides​ or ask the discord bot

Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Wed, 11/07/2018 - 10:22 #1

Latest Version: RBAssist v 1.4.5

Updated 2019-09-19


 
 

Download URL
https://www.dropbox.com/sh/dhegbivnmy7qnli/AAAcB3W9LPZ9ZcQB8pI25HDOa?dl=0

Both binary file (.exe) and source file (.au3) are available.
If you don't know which one to use, download the exe file.

RBAssist is a tool created to help RoS-Bot recover from crashes, automatically take screenshots of your game client, and schedule start/stop times for botting.
It was written in AutoIt3 and does not interact with Diablo 3 game memory in any way.

Features

  • Automatically recover from error messages such as "Object not set to an instance of an object"
  • Force a bot restart if no log activity has been detected for a period of time
  • Take screenshots periodically or based on bot events like deaths, fails, or errors
  • Start and stop bot on a customizable schedule
  • New features are being developed all the time - if you have suggestions please feel free to DM me on these forums or on Discord

Instructions

  1. Download the RBAssist exe file and place it in a folder of your choice
  2. Run RBAssist as Administrator
  3. Press the [...] Browse button next to RoS-BoT.exe on the right and select the location of your RoS-BoT.exe
  4. Enable the options you want using the checkboxes.
  5. Click "Start" to begin monitoring. If you've enabled the "Start bot when monitoring starts" option, RBAssist will launch RoS-BoT.exe and begin botting!

Application Requirements

RBAssist must be run with Administrator privileges. For best results, run Diablo 3 in Windowed mode at 800x600 resolution.

RBAssist needs to know the location of your RoS-BoT.exe. You can select the file location using the browse button on the right, or you will be prompted to select the file the first time you start the Monitoring process.

All functions are optional and can be enabled/disabled using the checkboxes.

RBAssist creates some additional files: RBAssistSettings.iniRBAssist.log, and tuhzorRBA.exe. All these files must stay in the same folder as the application. If they are moved/deleted/renamed, RBAssist will just create new ones (and you may lose your custom settings.)

Changelog

1.4.0 - Revamped Trigger creation UI
         - Included updated Rift TP script (credit to Tuhwin)
         - Changed D3 window matching to CLASS method
         - Added Edit Trigger context menu
         - Added 'Enabled' option for triggers
         - Added 'Logged' option for triggers
         - Added additional connectivity checks for autoupdate
         - Fixed 'Stop Bot (F7/F9)' formatting error
         - Fixed a bug where 'Start Botting !' wasn't pressed correctly
1.4.1 - Added additional monitoring on/off checks after trigger execution
         - Updated window search method to be more reliable
         - Fixed restart process
         - Added 'Check for updates' checkbox
1.4.2 - Added rclick->New menu for triggers
         - Changed Death log lines for RB 3.301 (requires Full logs)
         - (Fail screenshots are not currently working)
         - Added failsafe to Start Bot function
         - Changed default Inactivity Timeout to 20 minutes
1.4.3 - Changed Fail log lines for RB 3.301 (requires Full logs)
         - Fixed issue where rosbot exe was not detected after restart
1.4.4 - Fixed RBA closing itself during restart when running from the same folder as Rosbot (again)
         - Fixed new trigger dropdown default selection
         - Force-disabled Rift TP due to incompatibility with new versions
         - Added legacy Death/Fail log strings just in case
         - Compatibility with Diablo patch 2.6.6
1.4.5 - Added check for 'Session timeout' Teamviewer popup
         - Added minimize to tray option

Donate

If you would like to show your appreciation please visit http://paypal.me/sunblood
RBAssist will always be free and donations will never be required to access new versions or features. I appreciate your support!

RBAssist is in active development. Please report any bugs, strange behaviors, or feature requests you might have. Visit us in Discord for more!

Cyp
MODERATOR
Joined: 12/26/2015 - 19:41
Wed, 11/07/2018 - 12:02

It is also important to note that...FIRST!

I fully support this project. The stucks and odd errors here and there have taken away too much of my bots progress!


Need fast help? Join Discord. Guides: http://tiny.cc/s7poaz Common troubleshooting guide:http://tiny.cc/b8poaz

bumcello
Joined: 02/19/2018 - 07:48
Wed, 11/07/2018 - 12:06

Really nice project! And thx for your works.
I will use this, and report here any bug.
 


SlurpDurp
Joined: 01/30/2017 - 18:25
Wed, 11/07/2018 - 17:25

Very nice project!

GH Meph
Joined: 11/02/2016 - 07:55
Wed, 11/07/2018 - 18:53

Add option turn on PC when its down for 10min ^^ btw this one would make mine life much easier. BIG THANKS u just solved problems of guys without stable net.


diablofan40
DONATOR
Joined: 09/04/2015 - 19:38
Fri, 11/09/2018 - 16:04

Wow this is awesome.  My D3 keeps crashing and it’s pissing me off.  I’m still going through crash dumps and logs to figure it out but this may help higher bot uptime.  

Thanks!


notheoneyouthink
DONATOR
Joined: 01/14/2015 - 18:16
Sat, 11/10/2018 - 00:10

Ummm, AWESOME!


dweeb
DONATOR
Joined: 07/09/2015 - 18:42
Sat, 11/10/2018 - 15:26

Works like a charm. Thank you.


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Sat, 11/10/2018 - 16:49

Updated to v1.1.1
Reworked UI, put settings on various tabs to allow for more expansion and organization
Added Failed Run screenshot option
Changed screenshot path to a single directory (less flexibility but easier to work with internally, especially when adding screenshot options)


notheoneyouthink
DONATOR
Joined: 01/14/2015 - 18:16
Sat, 11/10/2018 - 20:10

This thing is a godsend.  Thank you.


coolingtea
Joined: 03/18/2018 - 23:50
Sun, 11/11/2018 - 05:29

It looks not suitable for the Chinese game edition.

 


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Sun, 11/11/2018 - 10:47 (Reply to #11)

App was built for and tested with English localization of D3. If you let me know what is different or not working with Chinese version I can look into adding compatibility.


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Sun, 11/11/2018 - 17:00

1.1.2 - Re-added individual screenshot paths
         - Fixed some settings not saving
         - String fix to make Fail detection more reliable
         - Added 'Delete Selected' button for Schedule
         - Modified log display so it can be scrolled and selected
         - Added option to set Diablo 3 game window title
         - Added hover tooltips for all settings and buttons


limevan
Joined: 10/19/2017 - 20:15
Mon, 11/12/2018 - 00:52

Awesome stuff, thank you very much!


RomainL
Joined: 11/21/2017 - 08:17
Mon, 11/12/2018 - 04:20

Hello,

the backdraw of this great project is to provide a new mean to catch botters.

This project should be embedded in RB itself.


Cyp
MODERATOR
Joined: 12/26/2015 - 19:41
Mon, 11/12/2018 - 04:56

How exactly do you think it helps to catch botters? Tinfoil hat getting heavy?


Need fast help? Join Discord. Guides: http://tiny.cc/s7poaz Common troubleshooting guide:http://tiny.cc/b8poaz

Lp515
Joined: 04/15/2018 - 08:02
Mon, 11/12/2018 - 06:20

Hi there and thank you for your work.
I would like to suggest/report a few things.
1: when i am setting screenshots number, i can only use the up/down arrow. Can we please type the number it self?
2: I have died twice in some run and it took the screenshot. Another run i died 8th times and there was no screenshot at all.
3: If i have f9/f7 the bot, the assistant does not stop its monitor work . I have ticked the options start monitoring when assistant start and start bot when monitoring starts. The problem is when i click start from the assistant it states some erroe and closes it self. There are 2 ways to make it work. If i close all and start the assistant to start them all or if i click on the bot to start botting. Can there be an option if all opened to just send the start option it self? Thanks again for your hard work and future :).


Cyp
MODERATOR
Joined: 12/26/2015 - 19:41
Mon, 11/12/2018 - 07:00

1 and 2 I agree. Had same behaviour.

Number 3: If you f7/f9 bot after doing initial launch through RBA you can simply use Bot Gui and press Start botting from there. Like you would do normally. That does not interfere with RBA.
If you press Start from RBA while Rosbot+D3 are running it does get confused and blows up everything, so to speak.


Need fast help? Join Discord. Guides: http://tiny.cc/s7poaz Common troubleshooting guide:http://tiny.cc/b8poaz

Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Mon, 11/12/2018 - 09:22 (Reply to #18)

Thanks for the feedback.
1. UI controls are locked to up/down arrows so we don't end up with negative numbers (or letters) which would cause strange behavior or crashes. For the same reasons I force you to use the Browse buttons to select paths, rosbot.exe, etc. If you want a specific value and don't want to push the buttons, open RBAssistSettings.ini and change the values manually.
2. I'm looking into this issue now. Can you look in your Rosbot logs (Documents\RoS-Bot\logs\logs.txt) and let me know if you see "INFO - Death" at the correct times, or if there is another Death indicator in the logs?
3. If D3 and Rosbot are open (but not botting) RBA will press the "Start botting" button for you with that setting. If the bot is actively running, v1.1.2 RBA will initiate a restart - this should be fixed in next version.


Lp515
Joined: 04/15/2018 - 08:02
Mon, 11/12/2018 - 09:54 (Reply to #19)

About the 3rd. I am still with 1.1.1 , will update any second and if already resolved at 1.1.2 then ignore.
To repeat the problem , simply open the RBA , ( if start monitor auto and start RB when monitoring are on ) , let it run and then stop the bot with f7\f9. The RBA still says it monitors. Then i click the start from RBA again and come up an error . " Line 17536 ( File "C:\Users\myusername\Desktop\Somefolder I made\RBAssist1.1.1.exe"): Error: Variable used without being declared. 
I just did it another way. I started RBA while the 2 options in general are ON ,as stated above , before it give the start botting command to RB i clicked stop in RBA ( i still needed my mouse to type this comment) and then when i tryed to to make it start\continue , the error came up again. If clean restart all good :)
About 1st, i can go in negative values just by clicking down. Probably i should update to RBA 1.1.2 before i report any issues that might have been fixed already.


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Mon, 11/12/2018 - 10:19

1.1.3 - Fix when starting monitoring while already botting
         - Added additional Death and Fail checks
         - Added a 1 second timeout for death/fail screenshots
         - Trimmed changelog
         - Temporarily unlocked inactivity restart minimum
         - Death/Fail checks now print the matching log line


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Mon, 11/12/2018 - 10:29 (Reply to #21)

I wasn't able to replicate the crash - try 1.1.3 and let me know if that's still happening.
All the up/down controls should be locked and not allow negatives, though I just found the Fail Screenshot Keep number did not have this set. Will be fixed in 1.1.4.


Lp515
Joined: 04/15/2018 - 08:02
Mon, 11/12/2018 - 10:37

Yes , the fail counter goes to negative value.
About the crash , i will make a video and pm the link to you in discord. A youtube video.


RomainL
Joined: 11/21/2017 - 08:17
Tue, 11/13/2018 - 14:08

@cyp. Unlike RB which is now quite well secured, this SW is not. Detecting it provides a good lead if not a clue to the Warden that you are running a bot.

AS-IS, this SW can be found in blink of an eye.


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Tue, 11/13/2018 - 15:31

1.1.4 - Fixed Fail Screenshot Keep input allowing negative numbers

- Added icon

- Changed default to 'No' on exit confirmation

- Fixed crash when stopping and starting monitoring

- Inactivity restart minimum is now 3 minutes

- Log display will now clear itself to prevent reaching max length

- Added restart for arithmetic operation overflow


Cyp
MODERATOR
Joined: 12/26/2015 - 19:41
Tue, 11/13/2018 - 15:35

Well, you do understand that if you are using RosBot - warden is effectively cut off from scanning the account where RBA is located on?

Rosbot creates a *limited* user account. Diablo 3 is ran from that account. Warden has no access to scan what is running and your theory is bust.

Moreso - there is absolutely no issue with RBA as it does not even provide you any sort of unfair advantage like THUD/D3Helper or any .ahk that would...enhance the experience.
RBA does not even scan Diablo 3s memory. Only reads Rosbots log file and looks for active process running: Yes/No

But you do not need to use RBA and if you are afraid of a ban then best not use Rosbot.


Need fast help? Join Discord. Guides: http://tiny.cc/s7poaz Common troubleshooting guide:http://tiny.cc/b8poaz

batzmichtot
Joined: 05/15/2017 - 05:24
Wed, 11/14/2018 - 02:18

Hello Sunblood,
first thanks for your work! :)

i have problems with the Assist, running since 2 Days now and he never managed to get an Recover From Crashing.

2018-11-13 20:51:17 - Fail screenshot - 2018-11-13 20:51:17,515 INFO - Runstep failed, moving to next run
2018-11-13 21:11:10 - Fail screenshot - 2018-11-13 21:11:10,644 INFO - Runstep broken: No checkpoint left
2018-11-13 21:31:52 - Fail screenshot - 2018-11-13 21:31:51,952 INFO - Runstep failed, moving to next run
2018-11-13 22:25:41 - Fail screenshot - 2018-11-13 22:25:41,324 INFO - Runstep broken: No checkpoint left
2018-11-13 22:28:36 - Fail screenshot - 2018-11-13 22:28:36,293 INFO - Runstep failed, moving to next run
2018-11-14 01:32:13 - Fail screenshot - 2018-11-14 01:32:12,975 INFO - Runstep broken: No checkpoint left
2018-11-14 01:48:52 - Fail screenshot - 2018-11-14 01:48:52,436 INFO - Runstep failed, moving to next run
2018-11-14 01:51:37 - Fail screenshot - 2018-11-14 01:51:37,039 INFO - Runstep broken: No checkpoint left
2018-11-14 02:12:49 - Fail screenshot - 2018-11-14 02:12:49,795 INFO - Runstep broken: No checkpoint left
2018-11-14 02:30:52 - Inactivity timeout detected

and after that no restarts, it write one but it says
02:30:52 Inactivity timeout detected
02:30:52 Starting bot: Inactivity timeout
02:30:52 Closing Diablo III.exe
02:30:53 Closing Notepad.exe
02:30:53 Bot process: T61Cpn7OChb.exe
02:30:53 Pressing F7
02:30:53 Waiting 5 seconds
02:30:58 Pressing F7 again for good luck
02:30:58 Waiting 5 seconds
02:31:03 Force closing all possible bot processes
02:31:03 Closing Diablo III.exe
02:31:03 Closing RoS-BoT.exe
02:31:03 Closing T61Cpn7OChb.exe
02:31:03 Waiting 10 seconds
02:31:13 Launching RoS-Bot
thats the last logline nothing happens

Ty for helping.

 


RomainL
Joined: 11/21/2017 - 08:17
Wed, 11/14/2018 - 08:39

Why do you think RB bothers generating a new name & hash (among other things, I think) each time it starts up if D3 is not be able to get hints on the running processes?

Your "moreso" § is out of topic as I was pointing out a way for the Warden to get a lead/clue on a running sw against Blizz' rules. For sure, you won't get banned for using it alone, but you're waving a flag saying to the warden, "Search further, I might have something for you".

That's why I think that it could be part of RB as a new app to auto-start at the same it start its "clone".

Unless RB dev is telling me can that I can use it quite safely, as the core sw is preventing d3 from flagging anything, I won't use it as-is just as a precaution.

Anyway, I might be wrong, but I'll need a statement from RB dev for that (Si tu nous lis ;) ).


Rudaan
MODERATOR
Joined: 02/03/2016 - 11:40
Wed, 11/14/2018 - 14:06

RomainL....
Sunblood is a valued & very technical member of the Helpers Team on Discord, and regularly talks with ComMan. Cyp has also endorsed this app as well, and is one of the most technical folks I know of around here. That, in itself, should be sufficient.
If you are expecting an actual endorsement from CM or Tyrael, it is unlikely to come if only for liability reasons. They focus only on RosBot itself and have nothing to do with the extra apps like this, Cube Converter, Mystic Manager, etc.

Use the app and benefit from it, or don't. That is certainly your choice. :)


Need help? Join us in ros-bot discord channel 
Please goto the #support channel and type ?helpme

Cyp
MODERATOR
Joined: 12/26/2015 - 19:41
Wed, 11/14/2018 - 15:20

Look. You might not understand what is or how Warden works, but it's really simple.

Limited account privileges - Warden can't scan your running apps.
Warden can't look further because it simply has no elevated access due to the limited user.
RBs random file name generation predates the limited user access fix and is an added security feature.

Moreso - again - Warden checks for programs/apps that interact with Diablo 3s memory.
If you are able to grasp a simple concept - RBA is like a shortcut on your Desktop with attached scheduler. Does not even read Diablo3 memory and is not able to in any way.
Warden avoided. Again. Not that Warden would have even cared for a scheduler, but I digress.

See, I do not personally care if you use or do not use it, but ignorance bleeds misinformation and spreads like wildfire so that needs to be corrected :)

Otherwise - what Rudaan said.
Best of luck in your other adventures.


Need fast help? Join Discord. Guides: http://tiny.cc/s7poaz Common troubleshooting guide:http://tiny.cc/b8poaz

RomainL
Joined: 11/21/2017 - 08:17
Thu, 11/15/2018 - 04:19

Thank you for your explanations.


Comcast2140
DONATOR
Joined: 03/04/2015 - 13:59
Mon, 11/19/2018 - 19:54

This program is awesome, thanks so much for creating it. 

It restarted everything after the matience period today and got me botting again without having to touch anything. 


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Tue, 11/20/2018 - 18:53

1.1.5 - Improved CPU usage
         - Removed 'no checkpoint' fail string due to false positives
         - Window now saves position on exit
         - Changed Admin elevation method to fix 'Start with Windows'
         - Added timeouts for death/fail screenshots
         - Reduced frequency of scheduler checks


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Sun, 11/25/2018 - 20:05

1.1.6 - Log now includes full error.txt info
         - RB logfile reading speed increased
         - Additional check to prevent double death screenshot
         - Additional fail strings added


SlurpDurp
Joined: 01/30/2017 - 18:25
Sun, 11/25/2018 - 20:55

Awesome updates!

ek250013
Joined: 11/21/2015 - 14:39
Sun, 11/25/2018 - 23:58

lol LMFAO LOLOLOL KEK LMFAO ROFL LUL.
I run bounty now 24/7 thanks to this program thanks again sunblood. 


luzhonghao
Joined: 06/19/2018 - 10:07
Mon, 11/26/2018 - 04:29

I need to open the rosbot first then click the start button of RBA,Otherwise it didn't start botting.Is this the right order?


ek250013
Joined: 11/21/2015 - 14:39
Mon, 11/26/2018 - 09:59

No lmfao


burgerking
DONATOR
Joined: 05/14/2014 - 01:14
Tue, 11/27/2018 - 06:11

1. This works great as intended.
2. Long ago, I also wrote a similar Autoit app, but I used mouse to click on the RB buttons and it was a no go. I realized you used keyboard hooks to press on the start button. Very good technique!



 

Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Wed, 11/28/2018 - 16:26 (Reply to #39)

Depending on the options you have selected there is different behavior.

Under General tab, If you have "Start RoS-Bot when monitoring starts" enabled, RBA will launch Rosbot and click the "Start Botting" button by itself as soon as you start monitoring. (Highly recommend this option.) If you also have "Start monitoring automatically" then Rosbot will be launched and botting started as soon as you launch RBA.

If you do not use this option, RBA will just begin "monitoring" but will not launch Rosbot or D3. You will need to start Rosbot and click "Start Botting" by yourself. If you've also enabled "Restart after X minutes of no log activity", then as soon as you start RBA monitoring this timer starts. If you haven't started Rosbot by the timeout, since no log activity will be detected, RBA will initiate a "restart" and launch Rosbot+D3 and start botting. 


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Wed, 11/28/2018 - 16:36 (Reply to #40)

1. Thanks!
2. I'm using ControlSend to send a {SPACE} keystroke directly to the "Start Botting" button on Rosbot. Much more reliable, doesn't matter where the Rosbot window is located, and works even if Rosbot is not the active window (usually D3 is the active window during the restart process). The only catch is that ControlSend needs to know the window title, and Rosbot changes its own window title every restart. To that end I have some code to find the Rosbot window by iterating through every existing window and looking for that same "Start Botting" button (which is actually precisely labeled "Start Boting !" with that spelling and the space before the ! mark.) If found, that is probably the correct window. So there are some assumptions made, but unless you're somehow running two copies simultaneously (Rosbot itself prevents this) or you somehow have another unrelated window that has a button with the same mispelled text, it's enough precision for the purposes of the script. I've used AutoIt for a looooooong time and MouseClick() is basically a last resort for when ControlSend() or Send() do not work. The latter two are much more reliable and won't break as often.


burgerking
DONATOR
Joined: 05/14/2014 - 01:14
Wed, 11/28/2018 - 18:28

I just recently encountered a non-recovery scenario for RBAssist:
 

My bot machine just got disconnect a few minutes ago and RB was flooding the log file with:

2018-11-29 07:07:35,240 INFO - DisconnectionException thrown
2018-11-29 07:07:35,240 DEBUG - Stopping all tasks
2018-11-29 07:07:35,744 INFO - Disconnection
2018-11-29 07:07:35,744 INFO - Start a loop
2018-11-29 07:07:35,744 DEBUG - Stopping all tasks
2018-11-29 07:07:35,745 INFO - Start a loop
2018-11-29 07:07:35,745 DEBUG - Stopping all tasks
2018-11-29 07:07:35,746 INFO - Start a loop
2018-11-29 07:07:35,746 DEBUG - Stopping all tasks
2018-11-29 07:07:35,746 INFO - Start a loop
2018-11-29 07:07:35,747 DEBUG - Stopping all tasks
2018-11-29 07:07:35,747 INFO - Start a loop
2018-11-29 07:07:35,747 DEBUG - Stopping all tasks
2018-11-29 07:07:35,748 INFO - Start a loop
2018-11-29 07:07:35,748 DEBUG - Stopping all tasks
2018-11-29 07:07:35,749 INFO - Start a loop
2018-11-29 07:07:35,749 DEBUG - Stopping all tasks
2018-11-29 07:07:35,749 INFO - Start a loop
2018-11-29 07:07:35,750 DEBUG - Stopping all tasks
2018-11-29 07:07:35,750 INFO - Start a loop
2018-11-29 07:07:35,750 DEBUG - Stopping all tasks
2018-11-29 07:07:35,751 INFO - Start a loop
2018-11-29 07:07:35,751 DEBUG - Stopping all tasks
2018-11-29 07:07:35,752 INFO - Start a loop
2018-11-29 07:07:35,752 DEBUG - Stopping all tasks
2018-11-29 07:07:35,752 INFO - Start a loop
2018-11-29 07:07:35,753 DEBUG - Stopping all tasks
2018-11-29 07:07:35,753 INFO - Start a loop
2018-11-29 07:07:35,753 DEBUG - Stopping all tasks
2018-11-29 07:07:35,754 INFO - Start a loop
2018-11-29 07:07:35,754 DEBUG - Stopping all tasks
2018-11-29 07:07:35,755 INFO - Start a loop
2018-11-29 07:07:35,755 DEBUG - Stopping all tasks
2018-11-29 07:07:35,756 INFO - Start a loop
2018-11-29 07:07:35,757 DEBUG - Stopping all tasks
2018-11-29 07:07:35,758 INFO - Start a loop
2018-11-29 07:07:35,758 DEBUG - Stopping all tasks
2018-11-29 07:07:35,758 INFO - Start a loop
2018-11-29 07:07:35,759 DEBUG - Stopping all tasks
2018-11-29 07:07:35,759 INFO - Start a loop
2018-11-29 07:07:35,759 DEBUG - Stopping all tasks
2018-11-29 07:07:35,760 INFO - Start a loop
2018-11-29 07:07:35,760 DEBUG - Stopping all tasks

I stopped RB and checked RBAssist:

RBAssist was minutes behind in checking the log file as shown. Clearly it wont be able to catch up reading the log file as RB writes faster than RBA could read.

​I read the codes and found you were using $sLine = FileReadLine($lFile) in a Sleep(1) loop to check for bot's status.

According to Autoit Documentation, Sleep has a minimum duration of 10ms.

Due to internal implementation, the sleep time completion is checked every 10 milisseconds so the precision cannot be less than 10.
Note that other running processes often affect the timing accuracy and so pauses are likely to last for slightly longer than requested.

 


Perhaps, using a method to read from current line to last line in one go for it to catch up regardless how fast RB writes into log file?
 



 

Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Wed, 11/28/2018 - 19:52

This is actually an artifact of how Rosbot writes to log file - it does not write "live" per se but caches a few log lines and writes them in intervals. RBA can read the log plenty fast, it's just that Rosbot itself is not actually writing those log lines until a little while later (especially if it's spamming errors like that.) That's why sometimes you get death/fail screenshots that are delayed from the real event. It's a limitation of Rosbot itself.

With that output in RBA, it actually looks like Rosbot may have been spamming keystrokes on the start/stop buttons in the actual RBA window, which is why you get those stop/start messages. Under normal circumstances those don't ever appear without human interaction (except from the scheduler.) Not sure if there's anything RBA can do to recover from that - let me know if it happens again.

edit: in fact I can remove that Sleep(1) line entirely since GuiGetMsg() idles the CPU appropriately without Sleep(). No change in performance or CPU usage.


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Wed, 11/28/2018 - 19:58

1.2.0 - Added Tuhz0r Teleport! Check the new "Rift TP" tab.
         - Screenshot paths are now required if enabled


natu
DONATOR
Joined: 10/19/2015 - 13:46
Thu, 11/29/2018 - 06:21

awesome guys best tool of the year 


zerger3
Joined: 11/30/2017 - 18:13
Thu, 11/29/2018 - 07:21

would you mind hosting it also on some 1 click upload sites? i have the experience that after a while dropbox  uploads disappear sometimes but 1 click hoster stay (at least some of them) :)


lexluger34
DONATOR
Joined: 10/31/2015 - 03:30
Thu, 11/29/2018 - 11:04

Thanks again  Sunblood this program really allows me to hit that bounty no more coming home seeing a fucking error  I gained well over 30k mats since I use this program thanks again SIR.

 


BBC
Joined: 05/07/2017 - 15:25
Fri, 11/30/2018 - 12:19

Great program! Allows you to truely run 24/7 no crashes or errors can stop you now! 2018 what a time to be alive :)


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Fri, 11/30/2018 - 16:15 (Reply to #48)

Dropbox will be the primary (and only) source of this app for as long as I'm developing it. If you have issues downloading from Dropbox, please let me know, or hop into Discord to see if someone can send you a copy through other hosting means.


Sunblood
DONATOR
Joined: 09/06/2015 - 16:47
Fri, 11/30/2018 - 16:21

1.2.1 - Added Tuhzor restart during logfile rollover

- Fixed Tuhzor not closing if app exits while still monitoring

- Tuhzor app now gracefully exits (prevents orphan tray icons)

- Added auto-close for Teamviewer popup option

- Removed some log spam


darkacidblue
Joined: 11/27/2017 - 19:55
Sat, 12/01/2018 - 14:04

RBAssist press f7 randomly "for good look"


Advertisements

Advertisements