[takito]

Do you mean it activates and fails to disable or doesn't activate it at all? There is a failsafe right now that will deactivate it if it is activated.

There is still same problem. 43 prayer points drains over 3 ovls pots sometimes 1 sometimes 6.
 

one account 70/70/70 stats+ 43prayer
 
other one working fine

(still runing)

 

[serene]

There is still same problem. 43 prayer points drains over 3 ovls pots sometimes 1 sometimes 6.
 

one account 70/70/70 stats+ 43prayer

It drains overloads when trying to toggle? When you set the bot up what are your settings?
Also either thats very quick 19 strength levels or somethings wrong in the paint..

 

[takito]

It drains overloads when trying to toggle? When you set the bot up what are your settings?
Also either thats very quick 19 strength levels or somethings wrong in the paint..

it's paint glich. Cannot tell because i'm not looking at screen.

 

[serene]

it's paint glich. Cannot tell because i'm not looking at screen.

Will get the paint fixed.

I'm still unsure of where the bot is messing up.
You said it fails to toggle prayer but now it drains overloads?
Also you still haven't mentioned your settings.

 

[takito]

str+ absorbs + rapid heal+ ovls

it doesn't drain ovls.... after prayer drain bot stops~

 

[serene]

str+ absorbs + rapid heal+ ovls

it doesn't drain ovls.... after prayer drain bot stops~

Pushed update. Should be fixed when it is deployed.
 

~2hr proggy using msb at 80 range. Per hour values have been fixed, just not in this picture. Going to redo the UI to fit the UI of my other bots in progress as well.

 

[takito]

you've pushed wrong update. because verion is still the same as it was. i've started this 2hrs and a half ago. rapid heal flicking works (maybe i'm lucky). i'll let you know if it mess up until pots are out.
 
was runing fine for 4 hrs till inventory got emptied both accs. Doing 2nd run now.
 
2nd run 1account bugged on the same thing " rapid heal" flicking and emptied prayer points in 30min . 2nd account still runing.
 
2nd account stoped after 1hour of runing

 

[serene]

Serene updated DivineNMZ with a new update entry:

DivineNMZ v1.0.3 Released!

DivineNMZ updated to v1.0.3.

Read the rest of this update entry...
 

you've pushed wrong update. because verion is still the same as it was. i've started this 2hrs and a half ago. rapid heal flicking works (maybe i'm lucky). i'll let you know if it mess up until pots are out.
 
was runing fine for 4 hrs till inventory got emptied both accs. Doing 2nd run now.
 
2nd run 1account bugged on the same thing " rapid heal" flicking and emptied prayer points in 30min . 2nd account still runing.
 
2nd account stoped after 1hour of runing

I didn't push the wrong update, you used the old version. If the version is still the same as it was previously then the update wasn't deployed. Push means I queued it to be updated in the store, deployed means it was updated in the store to reflect what I pushed - and only executives can deploy updates. As you can see above, the update was deployed 2 minutes ago.

 

[takito]

gonna check this version now

 

[m lad]

I suggest adding a feature where it toggles your quick prayer instead of going through the prayer tab and clicking rapid heal as sometimes it doesn't activate the rapid heal, also at times it fails to work for longer than 5 minutes not sure why.

 

[takito]

there are still issues with rapid heal flicking on latest version. I've notice that bot fails to click on rapid heal prayer and clicks on different one. In this case prayer pons drains... and bot stops. Suggestion with toggling quick prayers should help to fix this.

edit:
testing with 2 accounts.

 

[serene]

there are still issues with rapid heal flicking on latest version. I've notice that bot fails to click on rapid heal prayer and clicks on different one. In this case prayer pons drains... and bot stops. Suggestion with toggling quick prayers should help to fix this.

edit:
testing with 2 accounts.

Working on adding quickprayer button instead of switching tabs.

I've run the bot 3 different times since updating it to v1.0.3, and each time hasn't encountered the problem you have. Am able to run each instance without a problem with rapid heal and they have each run for over 2hours. If the bot missclicks on a different prayer that would be a problem with clouse not bot specific. But even then it shouldn't happen often if at all because of the spacing between the different prayers. Which prayers are being clicked instead of rapid heal?
 
Rapid heal should be fixed. Let me know if it logs you out of dream too early, I switched the status to tell you exactly why it logged you out. Here's a quick proggy with blowpipe + void @ 75 range. Didn't start it with full supplies so it only ran for an hour.

 

[serene]

Serene updated DivineNMZ with a new update entry:

DivineNMZ v1.1.0 Released!

DivineNMZ updated to v1.1.0.

Read the rest of this update entry...

 

[takito]

there is still issue with rapid heal flicking. I noticed that it clicks on mage pray "mystic will" which empties pray. v1.1.0

 

[serene]

there is still issue with rapid heal flicking. I noticed that it clicks on mage pray "mystic will" which empties pray. v1.1.0

I've monitored the bot for the last 4 times I've run it and still haven't run into an issue with prayer flicking. Make sure your mouse multiplier is set to default 1.0. Post a screenshot of your settings as well.

 

[serene]

Serene updated DivineNMZ with a new update entry:

DivineNMZ v1.1.1 Released!

DivineNMZ updated to v1.1.1.

Read the rest of this update entry...

 

[takito]

after latest update script doesn't work.

 

[serene]

after latest update script doesn't work.

Doesn't start at all?

 

[party]

after latest update script doesn't work.

Please make reports clear and concise.

 

[takito]

error log:

java.lang.NullPointerException
at nul.IIiiiIiIiIii.move(lvb:53)
at com.runemate.game.api.hybrid.input.Mouse.move(rvb:127)
at com.deathizpro.bots.divineNMZ.divineNMZ.long(v:112)
at com.deathizpro.bots.divineNMZ.divineNMZ.onLoop(v:223)
at com.runemate.game.api.script.framework.LoopingScript.run(enb:257)
at com.runemate.game.api.script.framework.AbstractScript.start(iub:159)
at nul.iIiIiIiiiiIi.run(ugc:117)