[ink my squid]

Hello @Party I have been having some trouble with the bot to get it working, I had it working perfectly when I first started and then it randomly logged me out and whenever I am standing outside NMZ it wont purchase the dream to take me back in or move at all. I've spent about .30 - .40 trying to fix this as I love the previous things I've used from you like the pest control one so I'm a bit biased when I choose bots haha! Just wondering if there was something I'm doing wrong or if the bot was being worked on! Thanks Bro!

 

[i am nico]

Hello @Party I have been having some trouble with the bot to get it working, I had it working perfectly when I first started and then it randomly logged me out and whenever I am standing outside NMZ it wont purchase the dream to take me back in or move at all. I've spent about .30 - .40 trying to fix this as I love the previous things I've used from you like the pest control one so I'm a bit biased when I choose bots haha! Just wondering if there was something I'm doing wrong or if the bot was being worked on! Thanks Bro!

It's currently broken, been trying to reach out to him for a few days now

 

[ink my squid]

It's currently broken, been trying to reach out to him for a few days now

Thanks for reaching out bro! In that case I would like a .20 cent refund if that's possible until it's fixed and I'm able to use that again for a working version of the bot. @Party

 

[blackmamba69]

Hello bot is stuck buying potions, spamming the number in chat.
https://pastebin.com/raw/eaHpFjp6 log for the session.
Been stuck multiple times during the day trying to buy absorbsion potion, but then it writes in chat while the store is open.

I fixed it now by buying max potions of both.
 
Hello again, new problem.

When bot going to repair Dharok's gear it will go to bob and repair the gear. But it wont teleport back to nightmare zone. It just logs out because of idle and logging in with login handler.
https://pastebin.com/raw/JM6ZK4Em

It was stuck for 3 hours. Can i have a refund for those aswell? From 2:43 to 5:45.
Luckily i had autostop enabled.

02:43:44 INFO    [Repair with Bob] Removing Barrows items
02:43:49 INFO    [Repair with Bob] Talking to Bob
02:43:49 DEBUG    [Refresh] Refreshed with Bob(level: 0, position: 3230, 3202, 0)
02:43:50 DEBUG    [TargetWatcher] No Target -> Bob(level: 0, position: 3230, 3202, 0)
02:43:52 DEBUG    [TargetWatcher] Bob(level: 0, position: 3230, 3202, 0) -> No target
02:43:52 DEBUG    [ChatDialog] Found ChatDialog.Option(InterfaceComponent=InterfaceComponent [219, 1, 2], index=2, text=Repair all items: 259,710 coins.)
02:43:52 DEBUG    [ChatDialog] Found ChatDialog.Option(InterfaceComponent=InterfaceComponent [219, 1, 2], index=2, text=Repair all items: 259,710 coins.)
02:43:52 DEBUG    [ChatDialog] Found ChatDialog.Option(InterfaceComponent=InterfaceComponent [219, 1, 2], index=2, text=Repair all items: 259,710 coins.)
02:43:52 DEBUG    [TargetWatcher] No Target -> Bob(level: 0, position: 3230, 3202, 0)
02:43:53 DEBUG    [TargetWatcher] Bob(level: 0, position: 3230, 3202, 0) -> No target
02:43:54 DEBUG    [ChatDialog] Found ChatDialog.Option(InterfaceComponent=InterfaceComponent [219, 1, 2], index=2, text=Repair all items: 259,710 coins.)
02:44:00 INFO    [WebServices] Update successful for nmz
02:45:00 INFO    [WebServices] Update successful for nmz
02:46:00 INFO    [WebServices] Update successful for nmz
02:47:00 INFO    [WebServices] Update successful for nmz
02:48:00 INFO    [WebServices] Update successful for nmz
02:48:54 WARN    [LootTracker] Disabling for 5000ms
02:48:55 DEBUG    Login Handler has been activated!
02:49:00 INFO    [WebServices] Update successful for nmz
02:49:02 DEBUG    Interface Closer - Play Button has been activated!
02:50:00 INFO    [WebServices] Update successful for nmz
02:51:00 INFO    [WebServices] Update successful for nmz
02:52:00 INFO    [WebServices] Update successful for nmz
02:53:00 INFO    [WebServices] Update successful for nmz
02:54:00 INFO    [WebServices] Update successful for nmz
02:54:02 DEBUG    Login Handler has been activated!
02:54:03 WARN    [LootTracker] Disabling for 5000ms
02:54:09 DEBUG    Interface Closer - Play Button has been activated!
02:55:00 INFO    [WebServices] Update successful for nmz
02:56:00 INFO    [WebServices] Update successful for nmz
02:57:00 INFO    [WebServices] Update successful for nmz
02:58:00 INFO    [WebServices] Update successful for nmz
02:59:00 INFO    [WebServices] Update successful for nmz
02:59:10 WARN    [LootTracker] Disabling for 5000ms
02:59:10 DEBUG    Login Handler has been activated!
02:59:17 DEBUG    Interface Closer - Play Button has been activated!
03:00:00 INFO    [WebServices] Update successful for nmz
03:01:00 INFO    [WebServices] Update successful for nmz
03:02:00 INFO    [WebServices] Update successful for nmz
03:03:00 INFO    [WebServices] Update successful for nmz
03:04:00 INFO    [WebServices] Update successful for nmz
03:04:18 DEBUG    Login Handler has been activated!
03:04:18 WARN    [LootTracker] Disabling for 5000ms
03:04:25 DEBUG    Interface Closer - Play Button has been activated!
03:05:00 INFO    [WebServices] Update successful for nmz
03:06:00 INFO    [WebServices] Update successful for nmz
03:07:00 INFO    [WebServices] Update successful for nmz
03:08:00 INFO    [WebServices] Update successful for nmz
03:09:00 INFO    [WebServices] Update successful for nmz
03:09:26 WARN    [LootTracker] Disabling for 5000ms
03:09:27 DEBUG    Login Handler has been activated!
03:09:33 DEBUG    Interface Closer - Play Button has been activated!
03:10:00 INFO    [WebServices] Update successful for nmz
03:11:00 INFO    [WebServices] Update successful for nmz
03:12:00 INFO    [WebServices] Update successful for nmz
03:13:00 INFO    [WebServices] Update successful for nmz
03:14:00 INFO    [WebServices] Update successful for nmz
03:14:34 WARN    [LootTracker] Disabling for 5000ms
03:14:34 DEBUG    Login Handler has been activated!
03:14:41 DEBUG    Interface Closer - Play Button has been activated!
03:15:00 INFO    [WebServices] Update successful for nmz
03:16:00 INFO    [WebServices] Update successful for nmz
03:17:00 INFO    [WebServices] Update successful for nmz
03:18:00 INFO    [WebServices] Update successful for nmz
03:19:00 INFO    [WebServices] Update successful for nmz
03:19:42 WARN    [LootTracker] Disabling for 5000ms
03:19:42 DEBUG    Login Handler has been activated!
03:19:50 DEBUG    Interface Closer - Play Button has been activated!
03:20:00 INFO    [WebServices] Update successful for nmz
03:21:00 INFO    [WebServices] Update successful for nmz
03:22:00 INFO    [WebServices] Update successful for nmz
03:23:00 INFO    [WebServices] Update successful for nmz
03:24:00 INFO    [WebServices] Update successful for nmz
03:24:51 WARN    [LootTracker] Disabling for 5000ms
03:24:51 DEBUG    Login Handler has been activated!
03:24:58 DEBUG    Interface Closer - Play Button has been activated!
03:25:00 INFO    [WebServices] Update successful for nmz
03:26:00 INFO    [WebServices] Update successful for nmz
03:27:00 INFO    [WebServices] Update successful for nmz
03:28:00 INFO    [WebServices] Update successful for nmz
03:29:00 INFO    [WebServices] Update successful for nmz
03:29:59 DEBUG    Login Handler has been activated!
03:29:59 WARN    [LootTracker] Disabling for 5000ms
03:30:00 INFO    [WebServices] Update successful for nmz
03:30:06 DEBUG    Interface Closer - Play Button has been activated!
03:31:00 INFO    [WebServices] Update successful for nmz
03:32:00 INFO    [WebServices] Update successful for nmz
03:33:00 INFO    [WebServices] Update successful for nmz
03:34:00 INFO    [WebServices] Update successful for nmz
03:35:00 INFO    [WebServices] Update successful for nmz
03:35:07 DEBUG    Login Handler has been activated!
03:35:07 WARN    [LootTracker] Disabling for 5000ms
03:35:14 DEBUG    Interface Closer - Play Button has been activated!
03:36:00 INFO    [WebServices] Update successful for nmz
03:37:00 INFO    [WebServices] Update successful for nmz
03:38:00 INFO    [WebServices] Update successful for nmz
03:39:00 INFO    [WebServices] Update successful for nmz
03:40:00 INFO    [WebServices] Update successful for nmz
03:40:15 DEBUG    Login Handler has been activated!
03:40:15 WARN    [LootTracker] Disabling for 5000ms
03:40:22 DEBUG    Interface Closer - Play Button has been activated!
03:41:01 INFO    [WebServices] Update successful for nmz
03:43:00 INFO    [WebServices] Update successful for nmz
03:44:00 INFO    [WebServices] Update successful for nmz
03:45:00 INFO    [WebServices] Update successful for nmz
03:45:23 WARN    [LootTracker] Disabling for 5000ms
03:45:23 DEBUG    Login Handler has been activated!
03:45:31 DEBUG    Interface Closer - Play Button has been activated!
03:46:01 INFO    [WebServices] Update successful for nmz
03:47:00 INFO    [WebServices] Update successful for nmz
03:48:00 INFO    [WebServices] Update successful for nmz
03:49:00 INFO    [WebServices] Update successful for nmz
03:50:00 INFO    [WebServices] Update successful for nmz
03:50:32 DEBUG    Login Handler has been activated!
03:50:32 WARN    [LootTracker] Disabling for 5000ms
03:50:38 DEBUG    Interface Closer - Play Button has been activated!
03:51:00 INFO    [WebServices] Update successful for nmz
03:52:00 INFO    [WebServices] Update successful for nmz
03:53:00 INFO    [WebServices] Update successful for nmz
03:54:00 INFO    [WebServices] Update successful for nmz
03:55:00 INFO    [WebServices] Update successful for nmz
03:55:40 WARN    [LootTracker] Disabling for 5000ms
03:55:40 DEBUG    Login Handler has been activated!
03:55:47 DEBUG    Interface Closer - Play Button has been activated!
03:56:00 INFO    [WebServices] Update successful for nmz
03:57:00 INFO    [WebServices] Update successful for nmz
03:58:00 INFO    [WebServices] Update successful for nmz
03:59:00 INFO    [WebServices] Update successful for nmz
04:00:00 INFO    [WebServices] Update successful for nmz
04:00:48 WARN    [LootTracker] Disabling for 5000ms
04:00:48 DEBUG    Login Handler has been activated!
04:00:55 DEBUG    Interface Closer - Play Button has been activated!
04:01:00 INFO    [WebServices] Update successful for nmz
04:02:00 INFO    [WebServices] Update successful for nmz
04:03:00 INFO    [WebServices] Update successful for nmz
04:04:00 INFO    [WebServices] Update successful for nmz
04:05:00 INFO    [WebServices] Update successful for nmz
04:05:56 WARN    [LootTracker] Disabling for 5000ms
04:05:57 DEBUG    Login Handler has been activated!
04:06:00 INFO    [WebServices] Update successful for nmz
04:06:03 DEBUG    Interface Closer - Play Button has been activated!
04:07:00 INFO    [WebServices] Update successful for nmz
04:08:00 INFO    [WebServices] Update successful for nmz
04:09:00 INFO    [WebServices] Update successful for nmz
04:10:00 INFO    [WebServices] Update successful for nmz
04:11:00 INFO    [WebServices] Update successful for nmz
04:11:05 WARN    [LootTracker] Disabling for 5000ms
04:11:05 DEBUG    Login Handler has been activated!
04:11:12 DEBUG    Interface Closer - Play Button has been activated!
04:12:00 INFO    [WebServices] Update successful for nmz
04:13:00 INFO    [WebServices] Update successful for nmz
04:14:00 INFO    [WebServices] Update successful for nmz
04:15:00 INFO    [WebServices] Update successful for nmz
04:16:00 INFO    [WebServices] Update successful for nmz
04:16:14 DEBUG    Login Handler has been activated!
04:16:14 WARN    [LootTracker] Disabling for 5000ms
04:16:20 DEBUG    Interface Closer - Play Button has been activated!
04:17:00 INFO    [WebServices] Update successful for nmz
04:18:00 INFO    [WebServices] Update successful for nmz
04:19:00 INFO    [WebServices] Update successful for nmz
04:20:00 INFO    [WebServices] Update successful for nmz
04:21:00 INFO    [WebServices] Update successful for nmz
04:21:21 WARN    [LootTracker] Disabling for 5000ms
04:21:21 DEBUG    Login Handler has been activated!
04:21:29 DEBUG    Interface Closer - Play Button has been activated!
04:22:00 INFO    [WebServices] Update successful for nmz
04:23:00 INFO    [WebServices] Update successful for nmz
04:24:00 INFO    [WebServices] Update successful for nmz
04:25:00 INFO    [WebServices] Update successful for nmz
04:26:00 INFO    [WebServices] Update successful for nmz
04:26:29 DEBUG    Login Handler has been activated!
04:26:30 WARN    [LootTracker] Disabling for 5000ms
04:26:36 DEBUG    Interface Closer - Play Button has been activated!
04:27:00 INFO    [WebServices] Update successful for nmz
04:28:00 INFO    [WebServices] Update successful for nmz
04:29:00 INFO    [WebServices] Update successful for nmz
04:30:00 INFO    [WebServices] Update successful for nmz
04:31:01 INFO    [WebServices] Update successful for nmz
04:31:37 WARN    [LootTracker] Disabling for 5000ms
04:31:38 DEBUG    Login Handler has been activated!
04:31:45 DEBUG    Interface Closer - Play Button has been activated!
04:32:00 INFO    [WebServices] Update successful for nmz
04:33:00 INFO    [WebServices] Update successful for nmz
04:34:00 INFO    [WebServices] Update successful for nmz
04:35:00 INFO    [WebServices] Update successful for nmz
04:36:00 INFO    [WebServices] Update successful for nmz
04:36:46 DEBUG    Login Handler has been activated!
04:36:46 WARN    [LootTracker] Disabling for 5000ms
04:36:53 DEBUG    Interface Closer - Play Button has been activated!
04:37:00 INFO    [WebServices] Update successful for nmz
04:38:00 INFO    [WebServices] Update successful for nmz
04:39:00 INFO    [WebServices] Update successful for nmz
04:40:00 INFO    [WebServices] Update successful for nmz
04:41:00 INFO    [WebServices] Update successful for nmz
04:41:54 DEBUG    Login Handler has been activated!
04:41:55 WARN    [LootTracker] Disabling for 5000ms
04:42:00 INFO    [WebServices] Update successful for nmz
04:42:01 DEBUG    Interface Closer - Play Button has been activated!
04:43:00 INFO    [WebServices] Update successful for nmz
04:44:00 INFO    [WebServices] Update successful for nmz
04:45:00 INFO    [WebServices] Update successful for nmz
04:46:00 INFO    [WebServices] Update successful for nmz
04:47:00 INFO    [WebServices] Update successful for nmz
04:47:02 WARN    [LootTracker] Disabling for 5000ms
04:47:03 DEBUG    Login Handler has been activated!
04:47:09 DEBUG    Interface Closer - Play Button has been activated!
04:48:00 INFO    [WebServices] Update successful for nmz
04:49:00 INFO    [WebServices] Update successful for nmz
04:50:00 INFO    [WebServices] Update successful for nmz
04:51:00 INFO    [WebServices] Update successful for nmz
04:52:00 INFO    [WebServices] Update successful for nmz
04:52:11 WARN    [LootTracker] Disabling for 5000ms
04:52:11 DEBUG    Login Handler has been activated!
04:52:18 DEBUG    Interface Closer - Play Button has been activated!
04:53:00 INFO    [WebServices] Update successful for nmz
04:54:00 INFO    [WebServices] Update successful for nmz
04:55:00 INFO    [WebServices] Update successful for nmz
04:56:00 INFO    [WebServices] Update successful for nmz
04:57:00 INFO    [WebServices] Update successful for nmz
04:57:19 WARN    [LootTracker] Disabling for 5000ms
04:57:19 DEBUG    Login Handler has been activated!
04:57:26 DEBUG    Interface Closer - Play Button has been activated!
04:58:00 INFO    [WebServices] Update successful for nmz
04:59:00 INFO    [WebServices] Update successful for nmz
05:00:00 INFO    [WebServices] Update successful for nmz
05:01:00 INFO    [WebServices] Update successful for nmz
05:02:00 INFO    [WebServices] Update successful for nmz
05:02:27 WARN    [LootTracker] Disabling for 5000ms
05:02:27 DEBUG    Login Handler has been activated!
05:02:35 DEBUG    Interface Closer - Play Button has been activated!
05:03:00 INFO    [WebServices] Update successful for nmz
05:04:00 INFO    [WebServices] Update successful for nmz
05:05:00 INFO    [WebServices] Update successful for nmz
05:06:00 INFO    [WebServices] Update successful for nmz
05:07:00 INFO    [WebServices] Update successful for nmz
05:07:35 DEBUG    Login Handler has been activated!
05:07:36 WARN    [LootTracker] Disabling for 5000ms
05:07:42 DEBUG    Interface Closer - Play Button has been activated!
05:08:00 INFO    [WebServices] Update successful for nmz
05:09:00 INFO    [WebServices] Update successful for nmz
05:10:00 INFO    [WebServices] Update successful for nmz
05:11:00 INFO    [WebServices] Update successful for nmz
05:12:00 INFO    [WebServices] Update successful for nmz
05:12:43 WARN    [LootTracker] Disabling for 5000ms
05:12:43 DEBUG    Login Handler has been activated!
05:12:50 DEBUG    Interface Closer - Play Button has been activated!
05:13:00 INFO    [WebServices] Update successful for nmz
05:14:00 INFO    [WebServices] Update successful for nmz
05:15:00 INFO    [WebServices] Update successful for nmz
05:16:00 INFO    [WebServices] Update successful for nmz
05:17:00 INFO    [WebServices] Update successful for nmz
05:17:52 WARN    [LootTracker] Disabling for 5000ms
05:17:52 DEBUG    Login Handler has been activated!
05:17:59 DEBUG    Interface Closer - Play Button has been activated!
05:18:00 INFO    [WebServices] Update successful for nmz
05:19:00 INFO    [WebServices] Update successful for nmz
05:20:00 INFO    [WebServices] Update successful for nmz
05:21:00 INFO    [WebServices] Update successful for nmz
05:22:00 INFO    [WebServices] Update successful for nmz
05:23:00 DEBUG    Login Handler has been activated!
05:23:00 WARN    [LootTracker] Disabling for 5000ms
05:23:00 INFO    [WebServices] Update successful for nmz
05:23:07 DEBUG    Interface Closer - Play Button has been activated!
05:24:00 INFO    [WebServices] Update successful for nmz
05:25:00 INFO    [WebServices] Update successful for nmz
05:26:00 INFO    [WebServices] Update successful for nmz
05:27:00 INFO    [WebServices] Update successful for nmz
05:28:00 INFO    [WebServices] Update successful for nmz
05:28:08 WARN    [LootTracker] Disabling for 5000ms
05:28:08 DEBUG    Login Handler has been activated!
05:28:15 DEBUG    Interface Closer - Play Button has been activated!
05:29:00 INFO    [WebServices] Update successful for nmz
05:30:01 INFO    [WebServices] Update successful for nmz
05:31:00 INFO    [WebServices] Update successful for nmz
05:32:00 INFO    [WebServices] Update successful for nmz
05:33:00 INFO    [WebServices] Update successful for nmz
05:33:15 WARN    [LootTracker] Disabling for 5000ms
05:33:16 DEBUG    Login Handler has been activated!
05:33:23 DEBUG    Interface Closer - Play Button has been activated!
05:34:00 INFO    [WebServices] Update successful for nmz
05:35:00 INFO    [WebServices] Update successful for nmz
05:36:00 INFO    [WebServices] Update successful for nmz
05:37:00 INFO    [WebServices] Update successful for nmz
05:38:00 INFO    [WebServices] Update successful for nmz
05:38:23 DEBUG    Login Handler has been activated!
05:38:24 WARN    [LootTracker] Disabling for 5000ms
05:38:30 DEBUG    Interface Closer - Play Button has been activated!
05:39:00 INFO    [WebServices] Update successful for nmz
05:40:00 INFO    [WebServices] Update successful for nmz
05:41:00 INFO    [WebServices] Update successful for nmz
05:42:00 INFO    [WebServices] Update successful for nmz
05:42:02 INFO    [WebServices] No longer tracking nmz
05:42:02 INFO    [Bot stopped] Thanks for choosing Prime!
05:42:02 INFO    Stopping after the specified amount of time: 05:42:00

 

[bigavi]

As long as you have this bot prepared with max stock in potions it'll work very well.

Gone from 91 str to 99 75 attack to 90 and 90 range to 99, over a few weeks span.

Recommend

 

[jackb123]

hey bud, been using this all week flawlessly, today i cant get it to choose my gear set up and use special attack? tried twice with no luck.
 

hey bud, been using this all week flawlessly, today i cant get it to choose my gear set up and use special attack? tried twice with no luck.

tried again and its taken .30 off my account with no use, any chance i can get it returned?

 

[diice3]

Works flawlessly, please refund the .4$ from this morning! ty

 

[nitz]

Works flawlessly, I did however lose $.20 trying to set the bot up.. Could you please refund that?

Thanks,

 

[boogeysmoogey]

I'm in the same boat as Nitz, tried to setup the bot two times today and it wouldn't setup so i ended up losing $0.20.

Anyone gotten it to work yet? i don't want to try in fear of losing more $$$.

 

[diice3]

thats cool, the guy dont give a shit about serving anyone

 

[jhinn]

Works flawlessly, please refund the .4$ from this morning! ty

Why would he refund you because an OSRS update happened? Next time, assume the client isn't working, and wait for your fellow community members to give the green light. It's not Party's fault the OSRS update broke the client and not this bot.

 

[nitz]

Why would he refund you because an OSRS update happened? Next time, assume the client isn't working, and wait for your fellow community members to give the green light. It's not Party's fault the OSRS update broke the client and not this bot.

I can understand where you're coming from but you need to also look at it from the point of view of the user. There was no indication that the client was broken, the only issue that the users face was that the scripts did not load once they were activated. You'd assume that some one trying it once maybe twice and having the same result would maybe indicate there was an issue and the user should stop attempting to load a script.

Why would he refund you because an OSRS update happened?
In the past 6 months that I've been an active user there has been plenty of updates that hasn't affected the client in any way. Based on that it would be a safe assumption that the update from last week wouldn't break the client. I even tried to load the script twice, the first time it didn't load I assumed there was an issue loading the information so I attempted again before reaching out to the forums.

It's not Party's fault the OSRS update broke the client and not this bot.
I agree that is it not Party's fault the update broke the client, however; with the client working after prior updates and making an assumption that the script would work why should users be penalized? Why should Party receive payment for a transaction that wasn't fulfilled?

 

[boogeysmoogey]

Why would he refund you because an OSRS update happened? Next time, assume the client isn't working, and wait for your fellow community members to give the green light. It's not Party's fault the OSRS update broke the client and not this bot.

I do think it is funny that you have come over to this thread to flame us for asking for a refund when one of your top posts was giving advice to someone to go to the specific Bot Thread and ask for a refund.

 

[diice3]

Why would he refund you because an OSRS update happened? Next time, assume the client isn't working, and wait for your fellow community members to give the green light. It's not Party's fault the OSRS update broke the client and not this bot.

Are you all there mate? Not sure if youve had one too many sir

 

[kingy91]

damn havent used runemate in ages n got some money left on it but since robins a noob ill stay away for a while longer

 

[jhinn]

I can understand where you're coming from but you need to also look at it from the point of view of the user. There was no indication that the client was broken, the only issue that the users face was that the scripts did not load once they were activated. You'd assume that some one trying it once maybe twice and having the same result would maybe indicate there was an issue and the user should stop attempting to load a script.

Why would he refund you because an OSRS update happened?
In the past 6 months that I've been an active user there has been plenty of updates that hasn't affected the client in any way. Based on that it would be a safe assumption that the update from last week wouldn't break the client. I even tried to load the script twice, the first time it didn't load I assumed there was an issue loading the information so I attempted again before reaching out to the forums.

It's not Party's fault the OSRS update broke the client and not this bot.
I agree that is it not Party's fault the update broke the client, however; with the client working after prior updates and making an assumption that the script would work why should users be penalized? Why should Party receive payment for a transaction that wasn't fulfilled?

I agree, there should have been a client notification. Authors cannot do that, so that's up to the people who are in charge. If people cannot assume something is wrong after they've tried to use their favorite bot twice then I don't know what to tell you.

Based on that it would be a safe assumption that the update from last week wouldn't break the client.

This is wrong. Never assume OSRS updates do not break the client. They have done plenty of times, especially in 2020. Trying a bot twice is fine, but some people are trying to use a bot 20 times in a row and then complain about the script not working and wanting a refund. This is mostly aimed at those people. You're fine.

I agree that is it not Party's fault the update broke the client, however; with the client working after prior updates and making an assumption that the script would work why should users be penalized? Why should Party receive payment for a transaction that wasn't fulfilled?

Users shouldn't be penalized, I agree. There should have been a warning, there should automatically be a warning every Thursday until the client-dev confirms everything is working. Payments are handled by Arbiter, so take it up with him. You should be looking for a refund from them, not from Party. He has nothing to do with this problem.

I do think it is funny that you have come over to this thread to flame us for asking for a refund when one of your top posts was giving advice to someone to go to the specific Bot Thread and ask for a refund.

I also said that no one is obligated to give someone a refund. Refunds shouldn't be given out by an author if the fault is on the client. Hope that clears it up.

 

[diice3]

This is wrong. Never assume OSRS updates do not break the client. They have done plenty of times, especially in 2020. Trying a bot twice is fine, but some people are trying to use a bot 20 times in a row and then complain about the script not working and wanting a refund. This is mostly aimed at those people. You're fine./QUOTE]

Not sure why you feel so passionately about this subject but I feel less obliged to use your bots since you feel so intensely about no refunds. This isnt your thread, why are you hijacking it to argue with a whole crowd of people simply asking a creator for their money back. Moments ago, I was likely to try your bot but since youre so outspoken about the fact I asked for .40$ back after spending over 10$ with this user, there is no way in hell... Next time keep your mouth shut.

 

[jhinn]

I feel less obliged to use your bots

I was likely to try your bot but since youre so outspoken about the fact I asked for .40$ back after spending over 10$ with this user, there is no way in hell

Damn... I am devastated to hear this!!

 

[boogeysmoogey]

I also said that no one is obligated to give someone a refund. Refunds shouldn't be given out by an author if the fault is on the client. Hope that clears it up.

100% understand, but how does one go about trying to obtain a refund without posting? Then after one has posted to get flamed for asking for a refund all together. Wonderful circle we have going here. Keep your comment count going!

 

[jhinn]

100% understand, but how does one go about trying to obtain a refund without posting? Then after one has posted to get flamed for asking for a refund all together. Wonderful circle we have going here. Keep your comment count going!

No one is flaming you You're just asking the wrong person for a refund, that's all.
If you would like you request a refund from the owners, you can make a thread here - Client & Site Support
Good luck!