7 replies to this topic

[Hailed]

Since the only two options currently in Abrosia are 

 

a) completely disabling the check

b) using the old tiki rs ban check

 

a third option that actually fixes the check should be added.

 

As far as I know, the shops do not clear out at exactly the same time, which means that there should be many shops that still have inventory left.

 

Have Abrosia pick a sample of 5 or 10 shops and cycle through them and check if there are items in stock.

 

If none of the shops have items, then it can be assumed that the user has a rs ban. 

 

If one of the shops has items, then the user is not rs banned.

 

I apologize if this has already been suggested before or if I do not completely understand the restock ban system. 

[KaibaSama]

We initially had the suggested cycling through 5-10 shops to check for RS bans. However, the solution didn't work, because there were still too many false RS bans detected.

I didn't know we got rid of that one. I thought we were still using it. I say there's no longer a way to completely check for an RS ban now, you're going to end up getting false positives no matter what now. 

[Nano]

Someone could host a system with proxies and lots of accounts to determine if a shop has stock. Would just take a few days to code.

[Ka1]

As far as I know, the shops do not clear out at exactly the same time, which means that there should be many shops that still have inventory left.

 

 

They do all clear at the same time. I dont know why so many people are saying it is not.

It is just some shops stock immediately after the clear so it appears not to be cleared.

There is no way to find out unless you try every shop which people do so on RS & chat boards

 

There is another way to decrease the check to once per minute so it might chance the rs and become 'unban'

[Limeh]

Someone could host a system with proxies and lots of accounts to determine if a shop has stock. Would just take a few days to code.

 

I don't think anyone has the resources or would want to waste a bunch of proxies doing this.

Also there are so many users using abrosia that all the proxies would probably get RS banned as well.

 

You guys could probably code something that would scrape the data from the rs chat neoboard and find the key word "swi". 

Then go to the link associated with that post and then check for rs bans.

 

It's probably to big of a pain to do though.

Edited by Limeh, 02 June 2015 - 05:46 AM.

[Nano]

I don't think anyone has the resources or would want to waste a bunch of proxies doing this.

Also there are so many users using abrosia that all the proxies would probably get RS banned as well.

 

You guys could probably code something that would scrape the data from the rs chat neoboard and find the key word "swi". 

Then go to the link associated with that post and then check for rs bans.

 

It's probably to big of a pain to do though.

 

To be honest, it would be that big of job. And in a month there will be a surplus of shells on the market. All Abrosia would need to do is check it against a webpage, and have something like a Raspberry Pi constantly updating the webpage.

 

To be honest, I dont know who Abrosia can't collective work out what store is cleared and what isnt.

Edited by Freestyle, 02 June 2015 - 02:38 PM.

[Jibrille]

When I'm RSing for like... 10min and get ban, usually I manual check a few shops. It would be great to have this feature, but I seriously doubt someone will code this. Too much work like Limeh said

[mvux]

I don't know how to explain this in a short way and I don't know much about computer lingo so bear with me. Here's what I'm thinking:

 

USER A, B, C, etc are all using Abrosia...

 

1. Have Abrosia send a true or false variable(?) to a centralized database for the shop each of its users visit every X minutes.

 

Now let's say USER A is abing a shop and notices 0 stocks...

 

2. After Y number of refreshes returning 0 stock, User A's Abrosia retrieves true/false variable for said shop from the centralized database.

3. If variable returned is 'true', Abrosia determines RS Ban.

4. If variable returned is 'false' Abrosia resets the refresh count back to 0 and waits for Y number of refreshes again and steps 2-4 repeats.

 

Obviously this might be to simple and I've probably overlooked a lot of things. There are some problems I see with this is, one of which is that this wouldn't work for less frequented shops, but it would be ideal for the popular ones like Stamps, Books, etc. as you essentially have someone counterchecking for you without Neocodex needing to waste proxies for shell accounts. It's a start though, maybe this idea can be built upon... maybe?

Edited by mvux, 13 June 2015 - 03:30 AM.