SRL Archive - SRL Stats

Someone added 156M alchs to MSI, :p.

Would there be some way to block excessive editing of the script xp per item, number added to items made, etc. Like cap some values able to be submitted to a little above possible limits to prevent abuse?

From: smurg
Someone added 156M alchs to MSI, :p.

Would there be some way to block excessive editing of the script xp per item, number added to items made, etc. Like cap some values able to be submitted to a little above possible limits to prevent abuse?

Maybe the authors of certain scripts should set max levels of variable amounts eligible for their script per commit.

Scripts can be edited.

From: i luffs yeww
Scripts can be edited.

This. The stats backend is what should be edited.

Could be something like that programmed inside the stats system… though vars are global, so it'd be hard to do. I use a constant stats_IncVariable in PSWC for example, so anyone who commits a number of logs that isn't divisible by 28 is fake. Never had any issue yet… might it be a bug with however MSI increases the stats var? Don't know why someone would waste their time making fakes.

But what if you don't quite finish an invo/ have an axe in your invo?

surely that means you could have any number of logs in your invo at one time? or at east a mixture of multiples of 27 or 28 (for axe wielded or not)

I think it would have to be on a time run basis. Perhaps you could divide the number of the var you are adding by the time the scrip has run in that commit to work out the vars/hour. and if that crosses a certain boundary/ average you can not include the variable increase.

for example:

Running a lobby fisher. after 100 commits the average fished/hour is maybe like 200 (jsut random) but then someone edits the script to increase exp/ lobbies fished to make their SRL stats look better. It works out that it has only run for 1 hour and you've seemingly made over 100k of exp and lobbies. it realises that value cant be correct and debugs that and doesn't imput the value into the stats database.

It should be server-sided because anyone can easily take out the functions to prevent high commits in the script and replace/remove them. There should be an option in stats.villavu.com script management where you should be able to set the max amount to be committed of a variable per commit. Like if I set my script to commit every 10 mins and im doing 3000 lobs an hour then ever 10 mins I should get around 500 lobs (unrealistic) so set the commit cap in script management at 700-1000 lobs. Somewhere in between there. Oh and wizzup should get IP records on stats.villavu

From: Harry
Could be something like that programmed inside the stats system… though vars are global, so it'd be hard to do. I use a constant stats_IncVariable in PSWC for example, so anyone who commits a number of logs that isn't divisible by 28 is fake. Never had any issue yet… might it be a bug with however MSI increases the stats var? Don't know why someone would waste their time making fakes.

What if they have an axe in the inventory?

From: HarryJames
What if they have an axe in the inventory?

Deal with it. It static increases by 28 every time the bank is used. Stats aren't serious business, but at least by doing that I can be sure there is no mistakes.

I think 'deal with it' is a poor attitude to come at this with when there are viable solutions available.

For example i cant imagine it would be to tough for the script to send a variable which dictates if the runner has an axe in his invo or not.

So the server reads that 'AxeInInvo := 1' so there can only be 27 per bank then it divides the loads by 27 to work out if its a real commit.

However, this could be manipulated extremely easily. they would simply change the amount added per bank to a multiple of 28/27 depending.

I don't want to be a douche about it but the idea of a limited ' x amount per commit' or 'x amount per hour per commit' is a much more reliable as values like 'GetTimeRunning'(directly, not x := GetTimeRunning) cannot be manipulated (as far as i know).

It's not hard, just impractical. 28 works fine.

When I made a script, I made stats only for myself just for this reason.

Check IP of phony submissions and ban them.

From: mormonman
Check IP of phony submissions and ban them.

Isn't that a bit harsh?

From: Harry
Deal with it. It static increases by 28 every time the bank is used. Stats aren't serious business, but at least by doing that I can be sure there is no mistakes.

I was just wondering how it worked with an axe in the inventory, that's all. I do agree though, it's only 1 log per inventory. I was just wondering if it accounted for it.

I noticed the MSI Alchs thing the other day. I thought maybe I had made a mistake when I fixed the progress report counting, but I tested it a few times and the proper amount was being added. It's really hard to believe that MSI has made 156 million alchs. :p I actually don't even know if it's possible in the amount of time the stats have been up.

You may be able to check the people who have High Level Alchs in their stats and see who's is abnormally high. I'm sure the alchs isn't the only "phony" stat either. Chances are someone made a mistake somewhere and just hasn't noticed it yet. :p

From: Smarter Child
Isn't that a bit harsh?

No. Why cant people just be responsible and not mess with the things people give them? Im sure many people are tired of shit like this. Its not fun when people do this sort of thing.

http://stats.villavu.com/user/235

High Level Alchs : 156134206

From: Zyt3x
http://stats.villavu.com/user/235

High Level Alchs : 156134206

that's all bullshit. 600k air runes? yeah no. 142k gold bars? no. 156m alchs from 1 user? HA. ha. ha. Total EXP gained? 3062580801. I don't think anyone has 3 bil exp on rs yet. BAN.

From: Smarter Child
Isn't that a bit harsh?

Yeah, I don't like being harsh either but this isn't… it's not like we're banning him for Villavu or from using Simba. Stats is really just for fun and he's abusing it… oh well no stats for him, but he can still auto (if he even autoes LMAO)

or we can find out who this guy is and tell him to knock it off ( <- I like this idea best)

From: LolL
that's all bullshit. 600k air runes? yeah no. 142k gold bars? no. 156m alchs from 1 user? HA. ha. ha. Total EXP gained? 3062580801. I don't think anyone has 3 bil exp on rs yet. BAN.

thats a global account

so thats the exp and stuff earned from loads of people not just one

~shut

Tbh, since it's on the global account, does it really matter? Just take off ~156m alchs and get on with it. If someone does it again I'd say a ban is fine, but that account will always be #1, so it really isn't super important, imo.

Yeah something's up for sure. I'm sure Wizzup? could check the commits and get the IP from whoever is committing an excessive amount. Or the Anonymous user could just be deleted since it's just a collaboration of users that are too lazy to register a stats account.

The stats stores individual commits. Sure it's not too hard to remove one of them.

Don't delete Anonymous :( How about something like it logs and displays obfuscated IPs of who did commits if they don't have a real stats account? Or just ban the guy who did the alches on that account, and I don't think anyone else would be dumb like that.

From: Coh3n
Yeah something's up for sure. I'm sure Wizzup? could check the commits and get the IP from whoever is committing an excessive amount. Or the Anonymous user could just be deleted since it's just a collaboration of users that are too lazy to register a stats account.

Actually Wizzup? and DGby714 noticed this a while ago. Unfortunately he sad there isn't IP tracking on the site yet, but that would be the logical answer.

From: Harry
How about something like it logs and displays obfuscated IPs of who did commits if they don't have a real stats account?

Yeah, like for every individual IP assign a codename not related to the IP at all. So every 30.30.30… would be TheBoss5000 and every 50.50.50… would be IOwnAllDay and every 95.93.91… would be TheCakeMaster.

Then we could see: TheBoss5000 commits 50k alchs a day? NO STFU. B&&&

http://stats.villavu.com/commit/829540
http://stats.villavu.com/commit/829256
http://stats.villavu.com/commit/829232

Delete those three commits

From: Harry
Don't delete Anonymous :( How about something like it logs and displays obfuscated IPs of who did commits if they don't have a real stats account? Or just ban the guy who did the alches on that account, and I don't think anyone else would be dumb like that.

I know it sucks not being able to see exactly how much the scripts have been used, but it would solve problems like this. There's nothing else that wouldn't be a pain unless we were to make every script closed source, and that's not even possible with Simba.

From: Zyt3x
http://stats.villavu.com/commit/829540
http://stats.villavu.com/commit/829256
http://stats.villavu.com/commit/829232

Delete those three commits

Nice finds! :) IIRC, someone said there were other variables other than alchs.

From: Coh3n
Nice finds! :) IIRC, someone said there were other variables other than alchs.

Really?
Which ones? :)

From: Zyt3x
Really?
Which ones? :)

From: LolL
that's all bullshit. 600k air runes? yeah no. 142k gold bars? no. 156m alchs from 1 user? HA. ha. ha. Total EXP gained? 3062580801. I don't think anyone has 3 bil exp on rs yet. BAN.

:).

From: Coh3n
:).

That's because he is silly and doesn't realize it's a shared account. I think most of those are legit. Could just nuke whatever IP sent those fake alches and problem solved.

From: Harry
That's because he is silly and doesn't realize it's a shared account. I think most of those are legit. Could just nuke whatever IP sent those fake alches and problem solved.

Yeah the Airs and bars are actually possible. And someone said there was no IPs on the site yet, but the commits can be deleted.

Hm… It's actually temping to not allow anonymous commits as I'm getting quite fed up deleting commits because kids like to send in fake commits. I don't have time to implement a IP banning system right now, though. It'd be easier to ban/block users. I'll see what I can do in the next couple of days.

Maybe you could give some people mod powers?

From: Zyt3x
Maybe you could give some people mod powers?

Sure, but there is no mod panel. ;) I delete the queries in the python interactive interpreter.

Kinda douchey, this is why we cant have nice things…

Yeah, I didn't realize Anonymous was a shared account. sowwy :(

From: Wizzup?
Sure, but there is no mod panel. ;) I delete the queries in the python interactive interpreter.

Add it to you to-do list :)

From: Wizzup?
Hm… It's actually temping to not allow anonymous commits as I'm getting quite fed up deleting commits because kids like to send in fake commits. I don't have time to implement a IP banning system right now, though. It'd be easier to ban/block users. I'll see what I can do in the next couple of days.

I honestly think this is the best solution, at least until the time comes where other people can remove commits. Chances are though, someone will make a new account, call it something else, but have it serve the same purpose as Anonymous.

From: Coh3n
I honestly think this is the best solution, at least until the time comes where other people can remove commits. Chances are though, someone will make a new account, call it something else, but have it serve the same purpose as Anonymous.

IP banning with mini-statsmods would solve something then

From: Yago
IP banning with mini-statsmods would solve something then

Yes in the long run, but until Wizzup? actually has the time to implement such a system, disabling Anonymous is the easiest way to temporarily resolve this issue.

From: Coh3n
Yes in the long run, but until Wizzup? actually has the time to implement such a system, disabling Anonymous is the easiest way to temporarily resolve this issue.

Yes I saw that. I was trying to point out that it would really only be temporary though.

Lol, Alchs are up to 221 million.

I added a max variable amount for now. (10k)

I'll clean the dirty commits later.

E: I cleaned a few commits. I also noticed that there are 28k commits with XP gained > 10k…

From: Wizzup?
I added a max variable amount for now. (10k)

I'll clean the dirty commits later.

E: I cleaned a few commits. I also noticed that there are 28k commits with XP gained > 10k…

Could probably remove Total EXP Gained anyway now that there's separate skill ones. Does it say which scripts are committing that XP?

From: Wizzup?
I added a max variable amount for now. (10k)

I'll clean the dirty commits later.

E: I cleaned a few commits. I also noticed that there are 28k commits with XP gained > 10k…

Well, if you're cooking sharks at rogue den, that is very possible.