Few suggestions

[Roberto]

Heey, here a few suggestions ;)

-auto eat food
-auto fishing
-rune maker



Also i'd like to see a HUD that displays how many monsters you need to kill for next level.

for example when you need 400 xp till next lvl, and you hunt rots which give you 40exp each, the bot displays: You need to kill 10 rotworms till next level

You need to kill X (monster) till next level

The monster name will change after killing the last monster, if you only hunt rots this will ofc not change, but when your last killed monster was a carrion, it will say: You need to kill 6 Carrion rotworms till next level

[Messed Around]

Auto Eat/Fishing will cave most likely with or after the Cavebot is implemented.

[Roberto]

Auto Eat/Fishing will cave most likely with or after the Cavebot is implemented.

Already thought that, because they are basic features a bot has, what do you think about the HUD feature?

[Messed Around]

The HUD feature would be nice but it would take a butt load of coding, though DarkstaR is easily capable of doing so, might be easier to just have exp to next level and give how many creatures of the creatures you are killing until next level.

E.g

You kill a frost dragon, obtain full exp.
You have 3.75 Frost Dragons until you level up.

etc.

[Roberto]

The HUD feature would be nice but it would take a butt load of coding, though DarkstaR is easily capable of doing so, might be easier to just have exp to next level and give how many creatures of the creatures you are killing until next level.

E.g

You kill a frost dragon, obtain full exp.
You have 3.75 Frost Dragons until you level up.

etc.

Yeah, thats what i mean :P

[DarkstaR]

That HUD feature is a nice suggestion and should be easily possible!
The hardest part of doing so will be determining how much EXP a monster gives. I can statically code it into a file, but that leaves no room for use on OT's. It will also have to adapt to bonus EXP hours.
Secondly, I could see what the last "EXP" packet gave, but what if multiple monsters were killed at once?
Lastly, I could store current EXP after each kill, then subtract it on the next kill (giving me delta(EXP)), but that has the same problem as the second proposal.

Soon enough I will put all of these methods to the test to figure out which one will be the most reliable, and I'll try to get this implemented. Thanks for the suggestion!