Saving/Loading Bots
Hover over the bot loaded section and you can access the save and load buttons.
Pro Tip
You can save any number of bots. Some bots may ask you to resize the client to work properly. This is automatic.
The complete guide to building, testing, and deploying intelligent automation workflows using the Obvra client.
Hover over the bot loaded section and you can access the save and load buttons.
You can save any number of bots. Some bots may ask you to resize the client to work properly. This is automatic.
This is the action history where your bot’s actions live. Actions run from top to bottom, in order. Access it quickly with Ctrl + H
You can right-click any action to duplicate it, disable it, move it, or hover it to access other tools.
Watchers are separate logic loops. Each Watcher runs its own set of actions and checks.
Most bots use multiple Watchers, for example: one for the main task, one for banking, and one for safety.
You can duplicate watchers and it's actions within a watcher or duplicate them into another watcher.
Very beneficial to avoid having to remake the same thing twice or more.
You can create a new watcher from a specific group of actions so they have their own watcher.
Breaking up watchers is important. You can drag and move a sequence into it's own new watcher.
Select specific actions and move them within a watcher, to another, or delete them.
There are times when you only need a few actions or maybe you made a mistake somewhere.
You can rename watchers within the watcher panel.
Keep all of your watchers organized for quicker building.
Mastering when to disable a watcher is important. There are times when you will need to disable watchers and instead rely on them being triggered manually.
Triggering a disabled watcher allows you to build more complex bots that rely on specific encounters.
You can create any number of groups, rename it, and add other watchers into that group.
You can also right click on a group to delete the group or disable all watchers within that group.
You can move watchers into a tiny tab that sits below the others. This is great for organization.
These are typically placed here if you do not want them to take up space. Click them to restore.
Hover over any action in the action history until you see the + sign. Then click to to access the quick menu.
This will be the fastest way to insert new actions and make new selections.
Insert labeled headers between any action to remind yourself what each part does.
As watchers become long, it's easy to forget the job of each sequence within one.
Click and drag any action or watcher header in order to reposition it with another.
You can also drag any action to new tab which is the + sign and it will automatically create a watcher with it.
Logs show what the bot tried to do and what happened next, in real time. It can jump to the exact part in the bot that is causing the issues.
If something fails or the bot stops, logs usually explain exactly why.
Hover over the bot loaded section and you can access the save and load buttons.
The chatbot understands the context the moment you open it. You can ask it for advice or tips.
Enable AI Vision to analyze the screen. Ask questions, get True/False responses, and track elements purely through text to guide your bot's logic
You can also set custom regions on these vision actions to look at only specific spots on the screen.
Create a auto talker that randomly writes out a poem line by line.
It will automatically write out the poem. You can also have it react based on text seen, etc.
Drag a selection on the screen, then drag again to save it. That image becomes the target this action will look for.
After saving, the image appears directly inside the action so the bot knows what to search for.
The album shows every image you’ve saved for your bot.
You can also add new objects from here directly by adding new selections or uploading files.
Search zones tell the bot where it’s allowed to look on the screen.
This keeps the bot focused and prevents it from clicking the wrong thing.
You can resize or move zones without recreating the action.
Useful when the game window moves or the UI shifts slightly.
When enabled, if there are two or more of the same object visible; it will choose the furthest one from the character dot in center of minimap.
Commonly used to track and switch between fishing spots.
Enabling this allows the watcher to check for its target and execute actions even if a global delay is currently active.
You can also trigger to cancel any global on-going delays.
When enabled, this action interrupts any on-going action and instead instantly executes the watcher it's enabled for.
An example could be when making an agility bot. It should immediately grabs Marks of Grace from the ground.
Automatically disables the parent watcher after this action completes.
Bots are passive by default and will trigger when object is detected. You can stop a watcher completely with this.
Choose whether the bot left-clicks, right-clicks, double-clicks, or holds.
The click happens at the center of the found target unless offsets are applied.
Adds small variation to where the bot clicks.
This prevents repeated clicks on the exact same pixel.
Shifts the click position relative to the target before clicking.
Useful when detecting a large object but clicking a specific part of it.
Type keys to build a sequence the bot will press in order.
Delays can be added between keys to slow things down.
Each action can decide what happens next when it works or fails.
This is how bots retry actions, recover from errors, or switch Watchers.
You can retry an action a set number of times before moving on.
Useful when objects appear with delays or load inconsistently.
Actions can jump to another step or start a different Watcher.
This is how complex bots change behavior based on what’s happening.
Create a Find action that looks for the tree on screen.
This tells the bot what object it should interact with.
Add a Click action so the bot interacts with the tree.
Randomization helps prevent repeated identical clicks.
Add a delay between actions so the bot does not attempt to spam click the tree very quickly.
Delays are important to avoid spamming of any detections.
The bot will continue to cut the tree while it is visible on screen. If not, it will wait until the tree respawns and then click the tree again.
Move to next chapter to learn how to only click when the character is not busy.
In some clients, you will see the 'Not Woodcutting' highlight on screen. We can use this to prevent our player from cutting the tree while they are currently chopping.
This ensures the bot doesn’t click again until it finishes the task.
Label your watcher names appropriately and then create a new watcher and name it 'State'. This will be used to trigger our 'Chop' watcher.
The goal for this step is to prepare and stay organized.
We will be triggering our 'Chop' watcher only when we are not currently chopping. Disable the 'Chop' watcher and then set a conditional for 'State' watcher to trigger 'Chop' when true.
The 'Chop' watcher will never start unless it is triggered by the 'State' watcher.
Make sure 'Not Woodcutting' message is visible. That is the trigger to start. To get it to appear, click the tree first normally if the message disappeared. You can now customize your bot to include more features or start it as is.
The bot will loop the same checks and steps endlessly. You can lower the 5s delay so it rechecks faster.
We couldn't find anything matching your search. Try different keywords.