OutdatedBerserk - Bot
Berserk - Bot
Hello.
Today, me and @Arsenius are releasing the, seemingly, first public bot/trainer for AQ3D. There is work left to do, such as changing the user interface, but because of the release of Beta Berserker we decided to release the bot earlier than planned.
Do not hesitate to suggest new features!
How to use this bot:
1. Find your AQ3D installation folder (usually in C:\Program Files (x86)\Steam\steamapps\common\AdventureQuest3D).
2. In the installation folder you should have another folder called AQ3D_Data. Open that. Once opened, you should find there is a folder called Managed. Open it.
3. Move the "System.Threading.dll" file included in the Berserk zip file to the Managed folder.
^ These steps will only have to be repeated when the game is updated.
4. Start AQ3D
5. Start Berserk.exe
Bot features explained:
DLL ERRORS?
If you encounter any missing DLL errors, you need to install "Visual C++ Redistributable for Visual Studio 2015". Google it.
https://virusscan.jotti.org/en-US/fi...job/kw21izr5pm
https://www.virustotal.com/en/file/d...is/1498770976/
Today, me and @Arsenius are releasing the, seemingly, first public bot/trainer for AQ3D. There is work left to do, such as changing the user interface, but because of the release of Beta Berserker we decided to release the bot earlier than planned.
Do not hesitate to suggest new features!
How to use this bot:
1. Find your AQ3D installation folder (usually in C:\Program Files (x86)\Steam\steamapps\common\AdventureQuest3D).
2. In the installation folder you should have another folder called AQ3D_Data. Open that. Once opened, you should find there is a folder called Managed. Open it.
3. Move the "System.Threading.dll" file included in the Berserk zip file to the Managed folder.
^ These steps will only have to be repeated when the game is updated.
4. Start AQ3D
5. Start Berserk.exe
Bot features explained:
Features
Kill for:
This function will walk to and kill the specified monster until you have the specified quantity of the specified item. You can use it to get both inventory items and temp items (also known as quest items or quest objectives). If you kill for items, DO NOT FORGET to also add the specified item to the whitelist, so that it is automatically picked up.
Kill:
Walks to and kills the specified monster.
Add skill:
Adds the skills/spells you want the bot to use while fighting.
Join area:
Joins the specified area/map. Note that the option to join a private room does not always work for some reason.
Set waypoint:
This will retrieve your current position, and add it to the command list. When the command is executed, the bot will either teleport to that position if specified, otherwise walk to it. The purpose of this is to avoid the bot from getting stuck when walking to a monster/npc.
Teleport to:
Teleports to the specified monster or NPC.
Walk to:
Walks to the specified monster or NPC.
Auto relogin:
If this option is enabled, the bot will automatically log back into the game while running if you disconnect. Do not forget to specify which server you want it to login to.
Bot delay:
The delay in milliseconds between each command. This delay can be disabled by setting it to zero, because all commands are waited for to complete before going to the next command. However, it is always a good idea to have at least a slight delay.
Delay:
Adds a command that upon execution waits for the specified delay in milliseconds.
Skip cutscenes:
When enabled, the bot will automatically skip cutscenes.
Restart bot:
Adds a command that upon execution restarts the bot. Note that this feature is currently useless, but will probably have a good use in future releases.
Stop bot:
Adds a command that upon execution stops the bot. Note that this feature is currently useless, but will probably have a good use in future releases.
Save bot:
Saves the current bot to a file.
Load bot:
Loads the specified bot file.
Add item to auto pickup:
All items (loot) that are added to the whitelist will automatically be picked up while the bot is running.
Add to quest list:
All quests that are added to the quest list will automatically be loaded, accepted and completed.
Always on top and opacity:
Always on top will keep the bot window visible at all times.
Opacity is the visibility of the window. You can make it almost invisible. This is to ensure the window does not interfere too much while you play.
All windows have these two features.
This function will walk to and kill the specified monster until you have the specified quantity of the specified item. You can use it to get both inventory items and temp items (also known as quest items or quest objectives). If you kill for items, DO NOT FORGET to also add the specified item to the whitelist, so that it is automatically picked up.
Kill:
Walks to and kills the specified monster.
Add skill:
Adds the skills/spells you want the bot to use while fighting.
Join area:
Joins the specified area/map. Note that the option to join a private room does not always work for some reason.
Set waypoint:
This will retrieve your current position, and add it to the command list. When the command is executed, the bot will either teleport to that position if specified, otherwise walk to it. The purpose of this is to avoid the bot from getting stuck when walking to a monster/npc.
Teleport to:
Teleports to the specified monster or NPC.
Walk to:
Walks to the specified monster or NPC.
Auto relogin:
If this option is enabled, the bot will automatically log back into the game while running if you disconnect. Do not forget to specify which server you want it to login to.
Bot delay:
The delay in milliseconds between each command. This delay can be disabled by setting it to zero, because all commands are waited for to complete before going to the next command. However, it is always a good idea to have at least a slight delay.
Delay:
Adds a command that upon execution waits for the specified delay in milliseconds.
Skip cutscenes:
When enabled, the bot will automatically skip cutscenes.
Restart bot:
Adds a command that upon execution restarts the bot. Note that this feature is currently useless, but will probably have a good use in future releases.
Stop bot:
Adds a command that upon execution stops the bot. Note that this feature is currently useless, but will probably have a good use in future releases.
Save bot:
Saves the current bot to a file.
Load bot:
Loads the specified bot file.
Add item to auto pickup:
All items (loot) that are added to the whitelist will automatically be picked up while the bot is running.
Add to quest list:
All quests that are added to the quest list will automatically be loaded, accepted and completed.
Always on top and opacity:
Always on top will keep the bot window visible at all times.
Opacity is the visibility of the window. You can make it almost invisible. This is to ensure the window does not interfere too much while you play.
All windows have these two features.
DLL ERRORS?
If you encounter any missing DLL errors, you need to install "Visual C++ Redistributable for Visual Studio 2015". Google it.
https://virusscan.jotti.org/en-US/fi...job/kw21izr5pm
https://www.virustotal.com/en/file/d...is/1498770976/
Is this the secret project? Wow, it was so easy to deduce... Hahaha
That's awesome, I'm gonna create an AQ3D account just to use this bot!
That's awesome, I'm gonna create an AQ3D account just to use this bot!
Originally Posted by JKizt
Is this the secret project? Wow, it was so easy to deduce... Hahaha
That's awesome, I'm gonna create an AQ3D account just to use this bot!
That's awesome, I'm gonna create an AQ3D account just to use this bot!
Sounds good! Be sure to report any bugs.
Invalid link
Originally Posted by M.Stranger
Invalid link
Really sorry for the delay, been feeling ill.
/Approved.
/Approved.
Hey, I just get an error saying beserk.exe has stopped working?
How do you make so much awesome stuff in so little time :O
Originally Posted by Metax15
Hey, I just get an error saying beserk.exe has stopped working?
Originally Posted by Great Barrier
How do you make so much awesome stuff in so little time :O
I didn't create this bot on my own though of course, and that sped it up.
great application.
The only problem i'm having is the limited use of this due to the design of the maps. Most maps are wide and have large gaps between groups of enemies. This means that often the bot will run into walls or ledges that a jump can get the player over, but obviously the bot will not recognise this.
A possible solution is to add a radius slider for the bot so only '*' are attacked within '*' range. The only map i've found this to work well on is the doomskull bridge or whatever it's called.
Again, great application, with one small flaw.
The only problem i'm having is the limited use of this due to the design of the maps. Most maps are wide and have large gaps between groups of enemies. This means that often the bot will run into walls or ledges that a jump can get the player over, but obviously the bot will not recognise this.
A possible solution is to add a radius slider for the bot so only '*' are attacked within '*' range. The only map i've found this to work well on is the doomskull bridge or whatever it's called.
Again, great application, with one small flaw.
Originally Posted by 8554b614e3c97beb
great application.
The only problem i'm having is the limited use of this due to the design of the maps. Most maps are wide and have large gaps between groups of enemies. This means that often the bot will run into walls or ledges that a jump can get the player over, but obviously the bot will not recognise this.
A possible solution is to add a radius slider for the bot so only '*' are attacked within '*' range. The only map i've found this to work well on is the doomskull bridge or whatever it's called.
Again, great application, with one small flaw.
The only problem i'm having is the limited use of this due to the design of the maps. Most maps are wide and have large gaps between groups of enemies. This means that often the bot will run into walls or ledges that a jump can get the player over, but obviously the bot will not recognise this.
A possible solution is to add a radius slider for the bot so only '*' are attacked within '*' range. The only map i've found this to work well on is the doomskull bridge or whatever it's called.
Again, great application, with one small flaw.
We have already added the attack radius if enemy is within the attack radius coming in the next version,
But the jump we will also add that as a command or something if you want the player to jump after reaching a lets say waypoint?
Originally Posted by 8554b614e3c97beb
great application.
The only problem i'm having is the limited use of this due to the design of the maps. Most maps are wide and have large gaps between groups of enemies. This means that often the bot will run into walls or ledges that a jump can get the player over, but obviously the bot will not recognise this.
A possible solution is to add a radius slider for the bot so only '*' are attacked within '*' range. The only map i've found this to work well on is the doomskull bridge or whatever it's called.
Again, great application, with one small flaw.
The only problem i'm having is the limited use of this due to the design of the maps. Most maps are wide and have large gaps between groups of enemies. This means that often the bot will run into walls or ledges that a jump can get the player over, but obviously the bot will not recognise this.
A possible solution is to add a radius slider for the bot so only '*' are attacked within '*' range. The only map i've found this to work well on is the doomskull bridge or whatever it's called.
Again, great application, with one small flaw.
hey bro! it keeps crashing
Originally Posted by soyesh
hey bro! it keeps crashing
Ez solution just set location to the mob :P ez
On a serious note Devs are taking action against bots and shit https://www.aq3d.com/news/botters-get-banned/ if you haven't seen. I'd suggest searching in the login code for hwid/steamid based checks and spoof it in next update.
On a serious note Devs are taking action against bots and shit https://www.aq3d.com/news/botters-get-banned/ if you haven't seen. I'd suggest searching in the login code for hwid/steamid based checks and spoof it in next update.
This thread is closed for replies.
