Jump to content

Molly's Chaos Druids


Molly

Recommended Posts

You might notice when the bot loots during combat that it attempts to attack a target whilst actually still in combat, this will be fixed tonight after work. This problem arises due to how looting is handled in the script.

 

edit: Pushed looting/combat update. Live version is 3.3.

Edited by Molly
Link to comment
Share on other sites

Hello Molly hope all is well.

 

I have purchased your script and it seems to be working pretty well its just i am using it on an account with 1 attack so i am kicking with the rpg and my attack accuracy is low, sometimes i can be on a druid for 15 seconds missing hits. For some reason the script will just give up on killing the target druid after 9-15 seconds and try attacking another, making it very bot like. Is there any chance something could be set to wait for druid death then add a slight random sleep timer straight after.

Hope to hear soon! Cheers

Link to comment
Share on other sites

Hello Molly hope all is well.

 

I have purchased your script and it seems to be working pretty well its just i am using it on an account with 1 attack so i am kicking with the rpg and my attack accuracy is low, sometimes i can be on a druid for 15 seconds missing hits. For some reason the script will just give up on killing the target druid after 9-15 seconds and try attacking another, making it very bot like. Is there any chance something could be set to wait for druid death then add a slight random sleep timer straight after.

Hope to hear soon! Cheers

If this still happens in version 3.3 please let me know, I just checked at it looks like version 3.2 is still live. I pushed 3.3 last night however the the update has not been reflected on the SDN.

Link to comment
Share on other sites

Hello Molly hope all is well.

 

I have purchased your script and it seems to be working pretty well its just i am using it on an account with 1 attack so i am kicking with the rpg and my attack accuracy is low, sometimes i can be on a druid for 15 seconds missing hits. For some reason the script will just give up on killing the target druid after 9-15 seconds and try attacking another, making it very bot like. Is there any chance something could be set to wait for druid death then add a slight random sleep timer straight after.

Hope to hear soon! Cheers

P.S

Also if you could set it to bank as soon as food has run out (or have option to), i had set eat to 19 hp and le script waited for my hp to reach 19 after running out of food to go back to bank, Fortunately it glory tele'd right before i was dbow speced. Close call :P

If this still happens in version 3.3 please let me know, I just checked at it looks like version 3.2 is still live. I pushed 3.3 last night however the the update has not been reflected on the SDN.

Very Nice Thank you!

Oh and quick question, SDN should automatically update?

Link to comment
Share on other sites

P.S

Also if you could set it to bank as soon as food has run out (or have option to), i had set eat to 19 hp and le script waited for my hp to reach 19 after running out of food to go back to bank, Fortunately it glory tele'd right before i was dbow speced. Close call :P

Very Nice Thank you!

Oh and quick question, SDN should automatically update?

 

I can add that this weekend, just added it to my to-do list.

 

As for the SDN, the updates are not automatic. Each update is reviewed by an SDN manager(Alek being the only on at this time I believe) to make sure there is nothing malicious in the code and that the code is up to OSBot's standard.

Link to comment
Share on other sites

Sorry to be a pain in the ass here Molly just one last *suggestion (And this one will be a pain) :P

When my bot came back from a full trip, the first 3 druids dropped lootable herbs, after the first 2 druids i ate 2 tuna, then picked up the 2 herbs and had full inven, i then proceeded to kill the 3rd druid and got another good herb, problem is the 3rd druid cost me no food to kill so i still had a full inven and couldnt loot the herb. The script then proceeded to try and use the two herb in my full inven on the loot bag (Whilst being attacked because of aggro, ;kept closing off the dialog option to deposit 'one' or 'both' roughly 30 times before i lost enough HP from the 4th druid to eat a food and loot the herb. Now this is nothing major to me as im a pure and im using tuna so food goes fast, but this could become a problem for someone with defence and decent food, it could take ages to lose the hp to be able to loot the herb instead of just ;Eating a food to make room. Stuck in an almost infinite loop of trying to use herbs on loot bag untill aggro dies.

Im not sure if this is constructive or straight up annoying lol. 

Anyway, All the best.

Link to comment
Share on other sites

Sorry to be a pain in the ass here Molly just one last *suggestion (And this one will be a pain) :P

When my bot came back from a full trip, the first 3 druids dropped lootable herbs, after the first 2 druids i ate 2 tuna, then picked up the 2 herbs and had full inven, i then proceeded to kill the 3rd druid and got another good herb, problem is the 3rd druid cost me no food to kill so i still had a full inven and couldnt loot the herb. The script then proceeded to try and use the two herb in my full inven on the loot bag (Whilst being attacked because of aggro, ;kept closing off the dialog option to deposit 'one' or 'both' roughly 30 times before i lost enough HP from the 4th druid to eat a food and loot the herb. Now this is nothing major to me as im a pure and im using tuna so food goes fast, but this could become a problem for someone with defence and decent food, it could take ages to lose the hp to be able to loot the herb instead of just ;Eating a food to make room. Stuck in an almost infinite loop of trying to use herbs on loot bag untill aggro dies.

Im not sure if this is constructive or straight up annoying lol. 

Anyway, All the best.

The bot uses a check to determine if the player is in combat prior to using the looting bag, and subsequently runs the check each time it tries to deposit an in item in the bag.  The check also looks to see if the player is below the hp set to eat at as well as if another player is attacking the bot, if the checks returns those things are true at any point the bot will then stop using the bag and do what it needs to do. I just added another combat check in there just to be safe but I haven't been able to replicate that issue yet. That being said I may just rewrite my looting bag method this weekend because its fairly old code and probably not as efficient as I could write it to be now.

Link to comment
Share on other sites

The bot uses a check to determine if the player is in combat prior to using the looting bag, and subsequently runs the check each time it tries to deposit an in item in the bag.  The check also looks to see if the player is below the hp set to eat at as well as if another player is attacking the bot, if the checks returns those things are true at any point the bot will then stop using the bag and do what it needs to do. I just added another combat check in there just to be safe but I haven't been able to replicate that issue yet. That being said I may just rewrite my looting bag method this weekend because its fairly old code and probably not as efficient as I could write it to be now.

Damn your good :) I am from Australia and my connection would have to be the worst of everyone playing osrs, The Sleep timer may be just too fast for my connection to respond fast enough even on a good connection day.  I believe it only occurs during the aggro period and due to ms lag on my behalf it will repeat continually as i think the bot thinks its missclicked and tries again where as its just taking 1.5 seconds for the dialoug to even show up. by the time it does the next druid is well into pwning me with snare :P It might just be a problem for australians/New zealanders with that extra long delay :P 

Thank you for reading. Your awesome. If you would like i will keep an eye out for bugs etc and keep you informed :)

Link to comment
Share on other sites

Not worth buying untill update comes through onto the SDN, Account was just banned 48 hours because of the double clicking problem. I knew that would happen hahaha

What is the "double clicking problem"?

 

Also, about to push an update that should make the bot able to handle combat after looting better. I noticed that occasionally the bot would not correctly interact with the target that it was fighting before looting, this update will force the script to attack the target it had prior to looting assuming the target is not under attack by another player and your player is not already under attack. Live version will be 3.4.

Edited by Molly
Link to comment
Share on other sites

What is the "double clicking problem"?

 

The one where it will start killing a druid, then 2 seconds later try attacking the next one and spam click it continuously whilst still being attacking by the fukkn druid you were attacking previously, with auto retaliate on i counted up to 20 clicks trying to attack the next druid whilst already under attack. I knows its stupid that i even kept using the script and lost my account. But hopefully constructive criticism will make this shit work better so i can start a new account to try again.

 

insanecaptain23, on 13 Aug 2016 - 12:54 AM, said:snapback.png

Hello Molly hope all is well.

 

I have purchased your script and it seems to be working pretty well its just i am using it on an account with 1 attack so i am kicking with the rpg and my attack accuracy is low, sometimes i can be on a druid for 15 seconds missing hits. For some reason the script will just give up on killing the target druid after 9-15 seconds and try attacking another, making it very bot like. Is there any chance something could be set to wait for druid death then add a slight random sleep timer straight after.

Hope to hear soon! Cheers

"If this still happens in version 3.3 please let me know, I just checked at it looks like version 3.2 is still live. I pushed 3.3 last night however the the update has not been reflected on the SDN."

 

 

 

OBVIOUSLY the SDN team aint doing fucken shit and haven't pushed through the update '3.3'

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...