[Request Script]

Turn to target:

local monstersToTurn = 1
if #g_game.getMonstersAround(1) >= monstersToTurn then
  g_game.turn(g_game.getBestTurnDirection())
end
auto(250)

 

[Request Script]

Cast wave if all monsters within given range are in front of the character and different spell otherwise:

local player = g_game.getLocalPlayer()
local checkRange = 4
local spellWave = "ten times kamehameha"
local spellArea = "genki dama"

if g_game.isAttacking() then
    if #g_game.getMonstersInFront() == #g_game.getMonstersAround(1) and #g_game.getMonstersAround(1) > 0 and #g_game.getMonstersAround(checkRange) == #g_game.getMonstersAround(1) then
        g_game.talk(spellWave)
        sleep(900, 1100)
    elseif #g_game.getMonstersAround(checkRange) >= 1 then
        g_game.talk(spellArea)
        sleep(900, 1100)
    end
end

auto(100)

 

[Request Script]

Fishing:

local player = g_game.getLocalPlayer()
local pos = player:getPosition()
local offsetX = -3 -- how many sqms to the west/east
local offsetY = 0 -- how many sqms to the north/south
local fishingRodID = 3483
pos.x = pos.x + offsetX
pos.y = pos.y + offsetY
g_game.useItemOnPosition(fishingRodID, pos)
auto(2000)

 

[Extra Instance Of client]

Just to make it clear, when the bot crashes it also closes your client? Or what exactly is happening

 

Edit: I've recognized the issue, it will be fixed in the next beta release.

[suggestion]

13 hours ago, aline said:

with all due respect to his work, but the other version was much simpler to use.
I'm trying to open the client is crashing.
5 min passes and the client closes.
the cure does not return from sayaians is not working because the cure within the game and as other spells are by commands f1 to f12, we cannot perform spells by their names

I'll add an option to send keystrokes as in the previous version.

Also you are encouraged to send crash logs to this topic: 

 

10 hours ago, Markesant said:

At first look the new version looks impressive, can see that a lot of work has gone through. But in the current state is absolutely unusable, the amount of crashes make you waste more time troubleshooting the bot than using it.

First of all, this is a beta version and every bit of feedback is appreciated and crashes are more than expected from my end.

 

10 hours ago, Markesant said:

-I really like the implementation of the alert window with the toggles on the different alerts, but some of them are not working properly (or couldn't make them work) like the messages, or player attacking. one improvement could be adding some color depending on the status of the toggle, centering the words in the state box and uppercasing the yes/no status.

Some of the functions of the bot may not work on specific clients because of the protocol and/or other differences between the servers. In that case I'll be adding few more functions to replace already implemented alerts with scripts that could be customized to fit the server.

 

10 hours ago, Markesant said:

-the split on the targeting window seems a little over the top, the previous versions was so much cleaner and easier to use than this one, this seems more like a war bot than just a cavebot targeting system, imo this much detail on targeting preferences is overkill and shows the importance of an easy to use UI.

I highly disagree on this one, I've added a lot of features to the targeting and it was needed to create a separate panel for it.

For example you can now set the bot to follow or run away from the creature, as well as set different options based on specific creature count and more.
Just mess around with it and you will see how much advanced it is to the prior system.

 

10 hours ago, Markesant said:

-I would add an additional Cavebot enable toggle on the waypoints screen, add a toggle directly to each of the healing rules in order to not have to edit said rule every time you'd like to get something running(something like the scripts toggle on the previous version).

I like the suggestion of moving the checkbox into the grid view. You can add a hotkey script to quickly activate/deactive the cavebot and adding more controls to the UI doesn't feel like necessary for me right now.

 

10 hours ago, Markesant said:

-The script section is fine, but it would be nice to have already saved scripts show in the right column (maybe is already a feature, haven't use this window too much)

It does it already if saved in the default locations.

 

10 hours ago, Markesant said:

-Finally the cavebot in it self feels a lot chunkier than the previous version, I've been using the STAND action to move from one point to the next, and it gets stuck (stays standing for a bit, know that's the purpose of that action) making it look way more suspicious, don't know if I'm supposed to use another action in this case. Also seem that the cabebot could not pick up from mid cave, meaning it always looks for the first waypoint when it starts. On this same topic maybe add  a different window only containing the actions and cardinal direction when adding waypoints, the always on top covers a big portion of the screen, and it may look useless if you don't count with dual monitor setup.

You should be using stands pretty much only when changing floors or if you really need to ensure your character stands on a specific location.

Use nodes otherwise. Also double clicking on the ID column of waypoints sets the current waypoint to the clicked one so you can start wherever you want.

 

Also the bot has never crashed for me while I've tested it at DBL, can you provide more details about that?

[scripts]

Please create a new post with your request here using english: 

 

[DBLOTS]

 

[Help..]

send me your discord in private message @Viperek18

 

Edit: Solved, generally everything worked. Author was just confused.

[Help..]

@Viperek18restart the client and bot and don’t run any of them as administator

[boot don't recognize my client]

The autor of the post already figured it out.

Probably didn't change the executable name to "otclient".

[Request Script]

1 hour ago, legend said:

if possible reattack script and the script that keep my furie on 100 (rage on dbl)

 

You can load the “Keep Target” script that is already included in the bot.

 

Keep soul at 100:

local player = g_game.getLocalPlayer()
if player:getSoul() ~= 100 then
  g_game.talk("furie")
  sleep(900, 1100)
end
auto(100)

 

[Help..]

Did you enable each method individually as well as global spell/item checkbox?

[Changes]

You can read the overview here: https://otclientbot.com/features

 

The bot was designed to work on all otclients, but those heavily modified may not work for now.

[Your subscription has ended]

Yeah for some reason the 14 days didn't apply. Will fix it in a moment.

 

Edit: Should be fixed now.

[Request Script]

Write a brief explanation of what you would like the script to do.

Please make sure that the script you requested isn't already available at the forum, otherwise your post will be removed.

 

List of scripts:

1. Use spell based on player's soul
2. Auto fishing
3. Wave/area spell
4. Turn to target
5. Eat food
6. Drop specified items on the ground
7. Use item on the map based on character's position
8. Cast targeted spell with health check

[Crash Report Thread]

If you have encountered a client crash please attach the crashreport.log in the attachement to your new post.

This file should be located in the client's directory if a crash occured.

 

All posts without an attached crashreport.log will be deleted and user will be warned.

[Getting started]

Make sure to follow these steps to correctly launch the bot and minimize the issues that could occur:

1. It's possible that your antivirus software could detect the bot as a virus. It's a false positive and bot should be added as an exception.
2. Rename the client's name you would like to use to "otclient". (for example: dracona.exe -> otclient.exe)
3. Run the desired client and wait until it fully loads.
4. Launch bot and wait for a few seconds as it tends to crash the client on a startup occasionally.
5. If in the title of the bot's window you can't see your character's name or "Logged off" then the DLL injection failed. Try for a few more times and if it continues to not inject try reinstalling the bot to another location (for example desktop).
6. If there is an error window with "Initialization failed" message, please try again for a few times and if it doesn't work report to the forum in the Bug Report section specifying the client you tried.
7. Any crash should be reported to this thread created for the crash reports exclusively.
8. The bot should work with both openGL and DirectX clients, but it's better to use DirectX client if possible.

[OTClientBot v2.0.0 - beta 1]

You can download it here: OTClientBot-v2.0.0-beta1

Also please remember to install Visual C++ Redistributable for Visual Studio 2015 x86 if you haven't already.