RYanb0401

Looting seems to be very buggy at the moment. At Dust Devils (smoke dungeon not catacombs) it refuses to use BTP tablets along with the eat for loot option, no matter what I put in my looting list it will not eat to pick them up. This applies to all areas of the game that I have seen so far, but is most noticed here.

Hey folks. Now my understanding is that some time ago my paypal was compromised and all of my outgoing payments for the last few weeks had been charged back. Some were to OSBot, some to other places. Now none of these payments were actually refunded - they've all stayed where they belonged (where I made them) but I've been having issues in some places - one of which is here. I now have a few scripts which are showing as cancelled invoices - almost as if a refund was processed but never actually went through. Is there any way this can be resolved? Either by actually processing the refunds so I can rebuy the scripts or just by reactivating them?

Correction. Ran again for another slayer task and woke up this morning to a ban. RIP 15 year old account I guess. EDIT: Yes, it's my fault. I know that and accept that.

Account is primarily hand done, with some minor botting for convenience and QOL stuff. 3 runs in 2 days and no bans despite it making silly mistakes at times that I don't normally make myself. I guess the failures work in it's favour to a degree as it isn't robotically efficient at it

It kept itself on melee prayer while in range this time, but didn't the first. It ran into melee range with mage prayer on and never switched to melee, dying obviously. This time it stuck with melee prayer through two ranged attacks and luckily only took two small hits (30ish) AFTER healers had spawned and been attacked, so it was no longer trying to do too much at once.

Alright, it succeeded this time. Got to the end and it really scuffed Jad and dodged two VERY lucky hits while on the wrong prayer but it succeeded.

Got to Jad, prayed fine against him but ran straight into melee range and died. Look, dude, no disrespect here but this is getting fairly irritating especially seeing as I'm putting my ass on the line with each of these runs. I understand obviously botting is botting and I do it at my own risk but two runs back to back with different failures doesn't look great. This would have been easily correctable by me if I had any mouse input at all, even with the option enabled. One step back would have solved this. I'm giving it one last try, if it fails again I'm going to be sort of a loss as of what to do outside of a refund request. It isn't a cheap script for it to fail entirely three times in a row after wasting the cash that caves do Adding final try run progress to a spoiler here, will add to it as I progress.

Just got it now, running it now to see how it goes. So far wave 38 with no problems but I've also changed my gear, running a blowpipe setup this time. Let's see how it goes!

Thanks! I did a manual run after just to make sure my time on RS wasn't a total loss tonight. I'll dump some slayer points to get a jad task again tomorrow and run it again to see what I can find too.

PM sent, apologies it's not a complete log but it's what I have at the moment.

Started outside, had my effects volume on and I heard the attack sound but the script didn't react to it.

Worked fantastically right up until Jad where it stood still and died to his first attack without activating any prayers, nothing appeared in the log. I had to force it to run wave 62 as it stopped after killing the first 360. Got to be honest, I was pretty hopeful for this script as the way to push through slayer tasks and my pet hunt without much effort but I had to babysit the entire run to make sure it kept doing what it was supposed to. The run up to this at the end of 62 was....

Just thought I should add given previous posts... Recent updates to both the bot and the client have resolved all issues I've had with Perfect Fighter. Thanks for your hard work Czar! It's much appreciated, glad to see you take feedback on board and work with what we give you.

No console errors at all. I had an emergency teleport in the inventory for the bot to use when it was out of food, and it was set to teleport to the bank. From what I can tell it banked successfully once, but then on the second attempt it failed to bank rather than failed to eat. Since then however it seems to have been fine, no issues at all with another ~10 hours of use. Looting is very aggresive, especially if using both bones to beaches and the eat for loot option, as no matter how you set it it will eat all of your food to make way for bones! Worse things could happen but it dampens a tiny bit of profit from places like dust devils and the likes

Script is back to it's old ways. Randomly stopped eating during a slayer task and died, this time however I'd fallen asleep on the couch and have lost a bandos chest and tassets because of it. There's a solid chunk of cash down the toilet.

It will attack the dark beasts of it's own accord, whether or not they're aggressive or which settings I choose. Fair enough though if catacombs isn't supported. It will stop eating and drinking at any point, either two minutes into the first trip, after three bank runs or anywhere in between. Unfortunately it's very difficult to recreate as it's only a matter of time.

Bot cannot be trusted on it's own at Catacomb fire giants. For whatever reason, at random, it will stop eating and/or drinking prayer potions. Five times within the same slayer task so far. On top of this, it will occasionally get stuck trying to attack a dark beast (that I do not have the slayer level to kill) Between these issues and the camera bug I'm struggling to find reasons to recommend this bot for purchase.

- What is the bug - Camera constantly rotates after releasing keys - How did you make the bug happen - Any time I try to look around with the camera - Tried client restart? - Yes - Normal script or a plugin? - Normal script - Which exact setup options are enabled? - Happens on all settings regardless of what I choose

Just double checking if this is a known issue. Trying to use magic, the client will stop at trying to choose a spell to autocast. It stands still and stops with the mouse hovering over a spell two to the right of the one I choose, or at the edge of the screen if not possible.