What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Bot][Alpha] Grind Bot - CTP

Apoc

Well-Known Member
Joined
Jan 16, 2010
Messages
2,790
Reaction score
94
So, a while ago I started working on a rewrite of the level bot within HB. Unfortunately due to time constraints, and other misc issues, I never got around to completely finishing it.

Thusly, what I bring you today, is just that. Originally it was called "GrindBot2" but since I'm going to be working on it this way, we'll just call it "Grind Bot".

What is it?

In short, its a complete rewrite of the grind bot in HB right now. (Actually, its not really a rewrite, as its almost entirely different)

Its very small, which in turn, means less room for bugs to creep in.
Its very fast. It only does what it needs to, and nothing more. However, that doesn't mean it can't be extended (more on that later)

TL;DR; It grinds, vendors, and thats pretty much it.

Why is it better than whats already in HB?

Well, the code in HB is great, don't get me wrong. But the logic trees are... confusing. There are many things that decide for themselves what to be doing. GrindBot however, centralizes the decision process, and only allows 'branches' to execute a task. (Eg; A loot behavior shouldn't decide if it needs to loot... it should just loot the object and nothing more.)

Also... hooks. :)

Yes, I said hooks. GrindBot brings to the table the idea of "Tree Hooks". In other words; you can add, remove, or just change, entire branches of logic. Very easily. I'll explain more about this later.

Above all else, it doesn't try to do more than it needs to. Its objective is to kill mobs, loot them, and visit vendors when it has to. It doesn't try to complete quests, doesn't attempt to do BGs, etc.

What are these awesome hooks you speak of?

GrindBot implements a class called "TreeHooks", which allows you to well... hook into the tree.

Note: If you're NOT a developer, please don't bother reading the following, it'll only just confuse you.

TreeHooks allows developers to add, remove, or replace, entire branches of logic, easily, without having to iterate through the composite children, and hoping you got the right one. It also allows for "custom" hooks within your own composites.

The idea behind this, is that developers can extend, replace, or "fix" logic within the bot, without breaking things. I'll eventually explain more about this, but I don't have the time atm to do so.

What can I do to help?

Well, the bot itself is in alpha stages right now (meaning, its mostly proof-of-concept), so there will be bugs. Please report any bugs you find, any hooks you create, etc. It'll be nice to judge how useful this little semi-framework is for future use. (Eventually I'd like to extend it to questing, etc)

If you don't like alpha/beta testing software, then please, don't use it. I'm not here to give you free stuff bug-free. Its a work in progress, and with that, there WILL be bugs.

Download (Put it in your Bots folder)

Developer XML Docs Download
 
Last edited:
Known Bugs

It has no death logic. At all. (Yes, I know. I haven't gotten to it just yet)
 
Last edited:
Known Bugs

It has no death logic. At all. (Yes, I know. I haven't gotten to it just yet)

So... you can grind with this, but whatever you do, don't die... lol
 
fifth?

Please add fly to vendor :D or something, for example grinding for skinning mobs then when bags are full activating a fly to.

Raphus leave this thread now and go fix arelog :P dosn?t start bots when it starts up.
 
fifth?

Please add fly to vendor :D or something, for example grinding for skinning mobs then when bags are full activating a fly to.

Raphus leave this thread now and go fix arelog :P dosn?t start bots when it starts up.

Thats actually on my list. However, that will be *incredibly* buggy until our nav supports "indoors" area flags. (Basically; it'll work, if the vendors are all outdoors. But if they're in a building, Flightor will have major issues.)
 
I was testing it now 10 minutes (fully watching it) with an Winterspring Skinning profile I've just created (for the original Grind Bot).
In general it really seems to be faster in targeting, walking to the target and killing it after the first one has been killed. So it looks more fluid.

But in 95% of the cases it forgets to loot + skin. It runs to the next mob, realizes it and runs back to the previous map to loot it. Afterwards it tries to skin what also only sometimes works, as it tries to do that while it's moving (just a step towards the killed mob).
Once it got "stuck" as it was standing in the middle of two mobs. It was looking like the bot wasn't sure which one is closer and was running between both a couple of times :)
If this is changed I'm going to use this bot.
 
Last edited:
I was testing it now 10 minutes (fully watching it) with an Winterspring Skinning profile I've just created (for the original Grind Bot).
In general it really seems to be faster in targeting, walking to the target and killing it after the first one has been killed. So it looks more fluid.

But in 95% of the cases it forgets to loot + skin. It runs to the next mob, realizes it and runs back to the previous map to loot it. Afterwards it tries to skin what also only sometimes works, as it tries to do that while it's moving (just a step towards the killed mob).
Once it got "stuck" as it was standing in the middle of two mobs. It was looking like the bot wasn't sure which one is closer and was running between both a couple of times :)

If this is changed I'm going to use this bot.

These problems are the flaws in the bundled grind bot.
 
Back
Top