[party]

Is he still regularly present in the community?

He's the lead developer, so yes.

 

[jesse]

He's the lead developer, so yes.

lol just realised it's Cloud.

 

[slashnhax]

Is he still regularly present in the community?

Yeah. Also, with Alpha Fighter, try turning the Reachability checks off in the Npcs and Loot tabs

 

[jesse]

Yeah. Also, with Alpha Fighter, try turning the Reachability checks off in the Npcs and Loot tabs

No worries Slash Ill try that now thanks.


@Vaped if you're active today please look at this issue.
 
@SlashnHax @Party @Vaped

Now paying $50 if you can fix this issue. Beyond a joke now, can't even run nay bots they just stay constantly on "loading" until I time out into lobby where the bot stops itself.

 

[party]

No worries Slash Ill try that now thanks.


@Vaped if you're active today please look at this issue.
 
@SlashnHax @Party @Vaped

Now paying $50 if you can fix this issue. Beyond a joke now, can't even run nay bots they just stay constantly on "loading" until I time out into lobby where the bot stops itself.

It's been a day since you reported the issue, how quickly do you expect these things to be fixed?

Can you please check that the bot logs into your account in a timely manner. Just start a bot whilst logged out and time how long it takes you to log in.

 

[jesse]

It's been a day since you reported the issue, how quickly do you expect these things to be fixed?

Can you please check that the bot logs into your account in a timely manner. Just start a bot whilst logged out and time how long it takes you to log in.

Took about 2 minutes to start up by itself, logged in fine. Overall speed was a bit better, but the first click to complete an object or task is really slow, so from getting to the fishing spot to actually fishing it takes 45+ seconds

Is that normal?

 

[slashnhax]

Took about 2 minutes to start up by itself, logged in fine. Overall speed was a bit better, but the first click to complete an object or task is really slow, so from getting to the fishing spot to actually fishing it takes 45+ seconds

Is that normal?

Assuming you're using Celestial Fisher, no, that's not normal.

 

[jesse]

Assuming you're using Celestial Fisher, no, that's not normal.

Yes I am.
 
@bump @Vaped @Party @SlashnHax problem is still persisting. No change. Still as bad as before.

 

[hegsmate]

seems like an issue on your end maybe, ive hit 86 fishing with celestial fisher and multiple 24 hours.

 

[jesse]

seems like an issue on your end maybe, ive hit 86 fishing with celestial fisher and multiple 24 hours.

I'm happy to except that and work with that just need help. Celestial fisher is the only but that I can run long times, can actually fix itself when it takes too long to move and enters lobby

 

[swiss396]

Got a question too. Tried alot of different bots, but most of them had very slow walking. Sometiemes it even took 1 min for a bot to click where to go. Though with any skilling, combat and item picking had no issues - runs smooth... So, the question is - that slow walking is because of bot or a client?

P.s. Tried on 2 pc's. Same problem...

 

[party]

Got a question too. Tried alot of different bots, but most of them had very slow walking. Sometiemes it even took 1 min for a bot to click where to go. Though with any skilling, combat and item picking had no issues - runs smooth... So, the question is - that slow walking is because of bot or a client?

P.s. Tried on 2 pc's. Same problem...

Could be either the bot not being optimised (though most of the frequently updated ones are okay) or the client due to the way walking is handled.

Walking using the web is pretty resource intensive, so web walk requests are sent directly to the RuneMate servers where we handled the brunt of the processing power and send the generated path back to the client. If you have his ping or a poor connection to the RM servers, this could be a reason.

 

[swiss396]

Could be either the bot not being optimised (though most of the frequently updated ones are okay) or the client due to the way walking is handled.

Walking using the web is pretty resource intensive, so web walk requests are sent directly to the RuneMate servers where we handled the brunt of the processing power and send the generated path back to the client. If you have his ping or a poor connection to the RM servers, this could be a reason.

ping's not that bad... min: 27, max: 255...

 

[party]

ping's not that bad... min: 27, max: 255...

Pretty sure that's CloudFlare IP, not RuneMate's IP. This was discussed on another thread.

 

[jesse]

Pretty sure that's CloudFlare IP, not RuneMate's IP. This was discussed on another thread.

Could you please elaborate, it would be greatly appreciated.

 

[party]

Could you please elaborate, it would be greatly appreciated.

So (AFAIK, I could be wrong) CloudFlare works as an interim between your PC and the RM server. So your traffic is sent to the CloudFlare node before it gets anywhere near RumeMate, which means when you're pinging the RuneMate IP, you're actually pinging your nearest CloudFlare node and not the RM server.

 

[jesse]

So (AFAIK, I could be wrong) CloudFlare works as an interim between your PC and the RM server. So your traffic is sent to the CloudFlare node before it gets anywhere near RumeMate, which means when you're pinging the RuneMate IP, you're actually pinging your nearest CloudFlare node and not the RM server.

so you reckon it's going to be slow forever?

 

[party]

so you reckon it's going to be slow forever?

No, I reckon we need to tag in @Arbiter to see if he thinks that's a plausible explanation and if so, how to proceed.

 

[alexh666]

No, I reckon we need to tag in @Arbiter to see if he thinks that's a plausible explanation and if so, how to proceed.

If that is the case, cloudflare has options to setup a bypass cname, like direct.runemate.com
Even though I feel like spectre communication with your servers should not pass by CLOUDFLARE [EDIT] in the first place.

 

[arbiter]

If that is the case, cloudflare has options to setup a bypass cname, like direct.runemate.com
Even though I feel like spectre communication with your servers should not pass by runemate in the first place.

Server-side networking has nothing to do with this. It's a moot point. Anyone having this issue should attempt to isolate it through proper debugging. From a cursory look at this thread no such attempt has been made. Which bots are affected? If the answer is all of them, then which API methods are affected? It may require a small amount of programming experience to figure it out, but this is an edge case affecting very few of our users. We cannot recreate it and as such you (the collective you) must.
 
Try using a second computer in the same network. Try using a different network. There are a lot of variables that need to be isolated, and none of it has been done. So I kindly request that you stop tagging me in this thread until there is more relevant info we can work with. "Slow" is grossly insufficient.