Czar Pest Control

July 29Jul 29

Author

I will release new update for this so the bot can detects gates better, I used to do this in java aswell so I'll convert over the gate pathfinding code, ty sir

1

July 30Jul 30

I used the script for 4 hours with pauses on an old main account and got banned; the script still has a lot of room for improvement, but thanks for the test.

1

July 30Jul 30

Author

4 hours ago, wecalu said:
I used the script for 4 hours with pauses on an old main account and got banned; the script still has a lot of room for improvement, but thanks for the test.

This is very unfortunate but I will help potentially reverse the ban + avoid bans in the future, especially if its a legacy account. Aside from the gates/pathfinding shortening what else do you think this bot could improve on? Did you notice the clicks being accurate? Did you use any M.I.N.D behaviour antiban? Please confirm.

Friday at 12:21 PM5 days

Just bought this to use in repair mode but it is un-usable currently as others have stated. It just stand around by the void knight and does nothing for awhile. It will then try to go repair, but zeal is already gone. I'm also 10hp and die a lot and as soon as I die, process of standing by knight starts over again.

[07/31 07:20:03 AM] (2) API Not found!

[07/31 07:20:03 AM] Opening nearest obstacle toward path

[07/31 07:20:03 AM] Total obstacles size: [16]

[07/31 07:20:03 AM] Checking for reach: false

[07/31 07:20:03 AM] Grabbing next obstacle...

[07/31 07:20:03 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }

[07/31 07:20:03 AM] Total obstacles size: [16]

[07/31 07:20:03 AM] Searching for next obstacle...2

[07/31 07:20:03 AM] Searching for next obstacle...3

[07/31 07:20:03 AM] Total obstacles size: [16]

[07/31 07:20:03 AM] Trying regular API ... (4)

[07/31 07:20:03 AM] No obstacle

[07/31 07:20:04 AM] We don't need to walk to the central Void Knight

[07/31 07:20:04 AM] Submitting command: current_node with value:

[07/31 07:20:04 AM] We don't need to walk to the central Void Knight

[07/31 07:20:04 AM] Submitting command: current_node with value: Repair Mode

[07/31 07:20:04 AM] walk_best_path_doors Position { x: 13617, y: 2782, plane: 0 } and me: Position { x: 13601, y: 2789, plane: 0 }

[07/31 07:20:04 AM] API Findpath not found!

[07/31 07:20:04 AM] Trying custom...

[07/31 07:20:04 AM] Total obstacles size: [16]

[07/31 07:20:04 AM] (2) API Not found!

[07/31 07:20:04 AM] Opening nearest obstacle toward path

[07/31 07:20:04 AM] Total obstacles size: [16]

[07/31 07:20:04 AM] Checking for reach: false

[07/31 07:20:04 AM] Grabbing next obstacle...

[07/31 07:20:04 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }

[07/31 07:20:04 AM] Total obstacles size: [16]

[07/31 07:20:04 AM] Searching for next obstacle...2

[07/31 07:20:04 AM] Searching for next obstacle...3

[07/31 07:20:04 AM] Total obstacles size: [16]

[07/31 07:20:04 AM] Trying regular API ... (4)

[07/31 07:20:04 AM] No obstacle

[07/31 07:20:05 AM] We don't need to walk to the central Void Knight

[07/31 07:20:05 AM] Submitting command: current_node with value:

[07/31 07:20:05 AM] We don't need to walk to the central Void Knight

[07/31 07:20:05 AM] Submitting command: current_node with value: Repair Mode

[07/31 07:20:05 AM] walk_best_path_doors Position { x: 13617, y: 2782, plane: 0 } and me: Position { x: 13601, y: 2789, plane: 0 }

[07/31 07:20:05 AM] API Findpath not found!

[07/31 07:20:05 AM] Trying custom...

[07/31 07:20:05 AM] Total obstacles size: [16]

[07/31 07:20:05 AM] (2) API Not found!

[07/31 07:20:05 AM] Opening nearest obstacle toward path

[07/31 07:20:05 AM] Total obstacles size: [16]

[07/31 07:20:05 AM] Checking for reach: false

[07/31 07:20:05 AM] Grabbing next obstacle...

[07/31 07:20:05 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }

[07/31 07:20:05 AM] Total obstacles size: [16]

[07/31 07:20:05 AM] Searching for next obstacle...2

[07/31 07:20:05 AM] Searching for next obstacle...3

[07/31 07:20:05 AM] Total obstacles size: [16]

[07/31 07:20:05 AM] Trying regular API ... (4)

[07/31 07:20:05 AM] No obstacle

[07/31 07:20:05 AM] We don't need to walk to the central Void Knight

[07/31 07:20:05 AM] Submitting command: current_node with value:

[07/31 07:20:05 AM] We don't need to walk to the central Void Knight

[07/31 07:20:05 AM] Submitting command: current_node with value: Repair Mode

[07/31 07:20:06 AM] walk_best_path_doors Position { x: 13617, y: 2782, plane: 0 } and me: Position { x: 13601, y: 2789, plane: 0 }

[07/31 07:20:06 AM] API Findpath not found!

[07/31 07:20:06 AM] Trying custom...

[07/31 07:20:06 AM] Total obstacles size: [16]

[07/31 07:20:06 AM] (2) API Not found!

[07/31 07:20:06 AM] Opening nearest obstacle toward path

[07/31 07:20:06 AM] Total obstacles size: [16]

[07/31 07:20:06 AM] Checking for reach: false

[07/31 07:20:06 AM] Grabbing next obstacle...

[07/31 07:20:06 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }

1

Friday at 01:02 PM5 days

21 hours ago, Czar said:
Isso é muito lamentável, mas posso ajudar a reverter o banimento e evitar banimentos futuros, principalmente se for uma conta antiga. Além do encurtamento de caminhos/portais, o que mais você acha que este bot poderia melhorar? Você notou se os cliques estavam precisos? Você usou algum sistema anti-banimento baseado em comportamento do MIND? Por favor, confirme.

The account already had a past ban on its record (from 2021); it was recovered in 2023, so I think it’s unlikely it can be recovered again... :(

I enabled all of OSBot's anti-ban systems and manually tweaked settings to try to make the behavior seem more "human."

Looking at how the script ran before the ban, I think the bot's behavior could be improved; sometimes the clicks weren't precise, and it would just stand there until it finally clicked and hit the mob. I believe that contributed to the ban, along with issues like failing to open doors and the bot's clicks and movement patterns being very monotonous.

Still, it was performing its core function and making it to the end.

I also think it would be good to add a food option, since there's a risk of losing a lot of HP and dying (especially with low-level accounts), I suggest a complete overhaul of the bot to make it 100% effective.

Edited Friday at 01:03 PM5 days by wecalu

1

Friday at 04:48 PM5 days

Author

4 hours ago, J7wilson7 said:
Just bought this to use in repair mode but it is un-usable currently as others have stated. It just stand around by the void knight and does nothing for awhile. It will then try to go repair, but zeal is already gone. I'm also 10hp and die a lot and as soon as I die, process of standing by knight starts over again.
[07/31 07:20:03 AM] (2) API Not found!
[07/31 07:20:03 AM] Opening nearest obstacle toward path
[07/31 07:20:03 AM] Total obstacles size: [16]
[07/31 07:20:03 AM] Checking for reach: false
[07/31 07:20:03 AM] Grabbing next obstacle...
[07/31 07:20:03 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }
[07/31 07:20:03 AM] Total obstacles size: [16]
[07/31 07:20:03 AM] Searching for next obstacle...2
[07/31 07:20:03 AM] Searching for next obstacle...3
[07/31 07:20:03 AM] Total obstacles size: [16]
[07/31 07:20:03 AM] Trying regular API ... (4)
[07/31 07:20:03 AM] No obstacle
[07/31 07:20:04 AM] We don't need to walk to the central Void Knight
[07/31 07:20:04 AM] Submitting command: current_node with value:
[07/31 07:20:04 AM] We don't need to walk to the central Void Knight
[07/31 07:20:04 AM] We don't need to walk to the central Void Knight
[07/31 07:20:04 AM] We don't need to walk to the central Void Knight
[07/31 07:20:04 AM] We don't need to walk to the central Void Knight
[07/31 07:20:04 AM] Submitting command: current_node with value: Repair Mode
[07/31 07:20:04 AM] walk_best_path_doors Position { x: 13617, y: 2782, plane: 0 } and me: Position { x: 13601, y: 2789, plane: 0 }
[07/31 07:20:04 AM] API Findpath not found!
[07/31 07:20:04 AM] Trying custom...
[07/31 07:20:04 AM] Total obstacles size: [16]
[07/31 07:20:04 AM] (2) API Not found!
[07/31 07:20:04 AM] Opening nearest obstacle toward path
[07/31 07:20:04 AM] Total obstacles size: [16]
[07/31 07:20:04 AM] Checking for reach: false
[07/31 07:20:04 AM] Grabbing next obstacle...
[07/31 07:20:04 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }
[07/31 07:20:04 AM] Total obstacles size: [16]
[07/31 07:20:04 AM] Searching for next obstacle...2
[07/31 07:20:04 AM] Searching for next obstacle...3
[07/31 07:20:04 AM] Total obstacles size: [16]
[07/31 07:20:04 AM] Trying regular API ... (4)
[07/31 07:20:04 AM] No obstacle
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] Submitting command: current_node with value:
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] Submitting command: current_node with value: Repair Mode
[07/31 07:20:05 AM] walk_best_path_doors Position { x: 13617, y: 2782, plane: 0 } and me: Position { x: 13601, y: 2789, plane: 0 }
[07/31 07:20:05 AM] API Findpath not found!
[07/31 07:20:05 AM] Trying custom...
[07/31 07:20:05 AM] Total obstacles size: [16]
[07/31 07:20:05 AM] (2) API Not found!
[07/31 07:20:05 AM] Opening nearest obstacle toward path
[07/31 07:20:05 AM] Total obstacles size: [16]
[07/31 07:20:05 AM] Checking for reach: false
[07/31 07:20:05 AM] Grabbing next obstacle...
[07/31 07:20:05 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }
[07/31 07:20:05 AM] Total obstacles size: [16]
[07/31 07:20:05 AM] Searching for next obstacle...2
[07/31 07:20:05 AM] Searching for next obstacle...3
[07/31 07:20:05 AM] Total obstacles size: [16]
[07/31 07:20:05 AM] Trying regular API ... (4)
[07/31 07:20:05 AM] No obstacle
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] Submitting command: current_node with value:
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] We don't need to walk to the central Void Knight
[07/31 07:20:05 AM] Submitting command: current_node with value: Repair Mode
[07/31 07:20:06 AM] walk_best_path_doors Position { x: 13617, y: 2782, plane: 0 } and me: Position { x: 13601, y: 2789, plane: 0 }
[07/31 07:20:06 AM] API Findpath not found!
[07/31 07:20:06 AM] Trying custom...
[07/31 07:20:06 AM] Total obstacles size: [16]
[07/31 07:20:06 AM] (2) API Not found!
[07/31 07:20:06 AM] Opening nearest obstacle toward path
[07/31 07:20:06 AM] Total obstacles size: [16]
[07/31 07:20:06 AM] Checking for reach: false
[07/31 07:20:06 AM] Grabbing next obstacle...
[07/31 07:20:06 AM] Searching for next obstacle... to Position { x: 13617, y: 2782, plane: 0 } from Position { x: 13601, y: 2789, plane: 0 }

Thank you I can see the problem clearly, it seems to be with pathfinding, will release a patch right now. Amazing feedback thank you, I will make sure repair-mode works for you 100% perfectly

3 hours ago, wecalu said:
The account already had a past ban on its record (from 2021); it was recovered in 2023, so I think it’s unlikely it can be recovered again... :(
I enabled all of OSBot's anti-ban systems and manually tweaked settings to try to make the behavior seem more "human."
Looking at how the script ran before the ban, I think the bot's behavior could be improved; sometimes the clicks weren't precise, and it would just stand there until it finally clicked and hit the mob. I believe that contributed to the ban, along with issues like failing to open doors and the bot's clicks and movement patterns being very monotonous.
Still, it was performing its core function and making it to the end.
I also think it would be good to add a food option, since there's a risk of losing a lot of HP and dying (especially with low-level accounts), I suggest a complete overhaul of the bot to make it 100% effective.

Great feedback thank you, I will improve the clicks as much as possible, I am slightly worried about your resolution/zoom, this can interfere with clicks a lot. Were you on 100% scaling on both osrs in-game and windows? Did you notice any clicks were offset by a few pixels? The new c++ client is different to the java one so we have to be more careful.

Also tysm, I'll add food mode even though it's a safe minigame which means you will respawn nearby all the time, but I am always listening to suggestions. I would otherwise recommend using quickprayer, it's really useful especially with protect from melee enabled

Friday at 04:58 PM5 days

Author

New Update (v1.71)

Added better pathfinding for repair mode, fixed a lot of random walking/idle issues
Added more accurate mouse clicks and conditional delays upon successful mouse clicks

Update will automatically go live within 24 hours, enjoy!

Saturday at 06:48 PM4 days

Tried it out agian today...Still doing the same exact thing, just standing around mostly....

[08/01 01:46:13 PM] Submitting command: current_node with value:

[08/01 01:46:13 PM] We don't need to walk to the central Void Knight

[08/01 01:46:13 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:13 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:13 PM] We don't need to walk to the central Void Knight

[08/01 01:46:13 PM] Submitting command: current_node with value:

[08/01 01:46:13 PM] We don't need to walk to the central Void Knight

[08/01 01:46:13 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:13 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:14 PM] We don't need to walk to the central Void Knight

[08/01 01:46:14 PM] Submitting command: current_node with value:

[08/01 01:46:14 PM] We don't need to walk to the central Void Knight

[08/01 01:46:14 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:14 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:14 PM] We don't need to walk to the central Void Knight

[08/01 01:46:14 PM] Submitting command: current_node with value:

[08/01 01:46:14 PM] We don't need to walk to the central Void Knight

[08/01 01:46:14 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:14 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:15 PM] We don't need to walk to the central Void Knight

[08/01 01:46:15 PM] Submitting command: current_node with value:

[08/01 01:46:15 PM] We don't need to walk to the central Void Knight

[08/01 01:46:15 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:15 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:15 PM] We don't need to walk to the central Void Knight

[08/01 01:46:15 PM] Submitting command: current_node with value:

[08/01 01:46:15 PM] We don't need to walk to the central Void Knight

[08/01 01:46:15 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:15 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:16 PM] We don't need to walk to the central Void Knight

[08/01 01:46:16 PM] Submitting command: current_node with value:

[08/01 01:46:16 PM] We don't need to walk to the central Void Knight

[08/01 01:46:16 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:16 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:16 PM] We don't need to walk to the central Void Knight

[08/01 01:46:16 PM] Submitting command: current_node with value:

[08/01 01:46:16 PM] We don't need to walk to the central Void Knight

[08/01 01:46:16 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:16 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:17 PM] We don't need to walk to the central Void Knight

[08/01 01:46:17 PM] Submitting command: current_node with value:

[08/01 01:46:17 PM] We don't need to walk to the central Void Knight

[08/01 01:46:17 PM] Submitting command: current_node with value: Repair Mode

[08/01 01:46:17 PM] Waiting for activity to drop before repairing anything else!

[08/01 01:46:17 PM] Stopping script

[08/01 01:46:17 PM] Finalized event executor

[08/01 01:46:18 PM] Finalized random executor

[08/01 01:46:18 PM] Script stopped successfully

1

Saturday at 07:37 PM4 days

Author

Hmm looks like my update is still pending approval/safechecking, it should go live any moment soon, the latest version is v1.71, it will show inside the osbot client.

My apologies for the wait, I will edit this message as soon as they approve my update

21 hours ago21 hr

Any update on this? I'm still waiting.

1

19 hours ago19 hr

Author

1 hour ago, J7wilson7 said:
Any update on this? I'm still waiting.

Yessir the update went live 2 days ago, glgl lemme know how it goes for you, you should notice the walking/movement improve by a lot, I am also listening to any other suggestions you like

I forgot to mention in thread apologies, we get automated reminders on the osbot disc when updates go live

Featured Replies

Create an account or sign in to comment

Recently Browsing 0

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)