my suggestion is to increase the rate limit of the api system from 100 requests per minute to 200 as if you use multiple tools for torn the limit can make you hit the limit quite easily
Increase API rate limit
Started by Ayos [2257656] on in API Development.
About this thread
Posts archived: 14 / 14 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
- Archived posts
- 14
- Discussion span
- →
- People posting
- 7
- Likes on archived posts
- 10
- Posts by staff, officers and moderators
- 4
- Authority score
- 72 / 100
- Historical score
- 22 / 100
- Story score
- 34 / 100
- Engagement score
- 58 / 100
Most-liked replies
- DeKleineKobini [2114440] Committee
· 6 likes ·
If you use more than even 50 calls a minute consistently, you are probably doing it wrong.
If you use more than even 50 calls a minute consistently, you are probably doing it wrong.
I only do 50 calls when updating members Personal Stats for spreadsheets, this takes 2 minutes
I have deliberately fixed 50 calls for this process to stop the overuse of the APIs, other people should be taking these steps too
I only do this every few weeks, at the start and end of training periods or chains start and end
I have deliberately fixed 50 calls for this process to stop the overuse of the APIs, other people should be taking these steps too
I only do this every few weeks, at the start and end of training periods or chains start and end
Iterating through every players profile takes a long time on low rates.
Like I said, 'consistently'. If you keep looping though all players all the time, you are doing it wrong too.
How else should you keep an up to date record of player stats and activity then?
I'm not saying this is a reason to raise the limit as 100 is just fine for this, but how would you tackle this? I have my own method. Tracking players like this provides key information such as "who of the inactives might still have a dog tag?" since you can track number of times players have been in the hospital.
I'm not saying this is a reason to raise the limit as 100 is just fine for this, but how would you tackle this? I have my own method. Tracking players like this provides key information such as "who of the inactives might still have a dog tag?" since you can track number of times players have been in the hospital.
There is no reason to have an updates record of all players at all times.
I literally just gave a reason.
You gave a 1 month event as reason to strain the api all year long? And even dog tags, why scan 2.6m people for a few hundred tags?
There are less than half that number of players. Last count I did was 1,174,145 non-deleted accounts.
You don't need to strain for the whole year for that, just the months leading up to it and during it. It's an example regardless.
Other examples include:
An accurate player count. Hey look that comes in handy right now for correcting misinformation about there being 2.6m players.
Tracking player activity to see when people are most active. This can be done and smaller scopes such as a faction, but it's useful for tracking folks not in factions either.
Monitoring changes in statistics to see what a user is up to crime wise, money wise, travel wise, drug wise, mission wise.
Monitoring activity provides loads of useful data to leverage.
You don't need to strain for the whole year for that, just the months leading up to it and during it. It's an example regardless.
Other examples include:
An accurate player count. Hey look that comes in handy right now for correcting misinformation about there being 2.6m players.
Tracking player activity to see when people are most active. This can be done and smaller scopes such as a faction, but it's useful for tracking folks not in factions either.
Monitoring changes in statistics to see what a user is up to crime wise, money wise, travel wise, drug wise, mission wise.
Monitoring activity provides loads of useful data to leverage.
Being able to hit the entire player base like that would be a massively unfair advantage to people using it, nevermind the technical limitations.
Factions being even a little responsible with 50 a minute per user (still high if anyone is using anything else heavily) could pull 5,000 a min which is still ridiculous, and if that's not enough for you IDK what to say.
Factions being even a little responsible with 50 a minute per user (still high if anyone is using anything else heavily) could pull 5,000 a min which is still ridiculous, and if that's not enough for you IDK what to say.
Wow...
And then people complain that Torn is laggy.
My suggestion is Torn bans this guys key.
And then people complain that Torn is laggy.
My suggestion is Torn bans this guys key.
Anyone is allowed to pull all the players personal stats so long as you're within the rate limits and such. There's a popular TornStats site that does this in order to provide graphs for stuff that isn't in the in-game hall of fame.
There's also CRLF who writes reports on various player stats, activity, and feddings.
There's also CRLF who writes reports on various player stats, activity, and feddings.
They added the api because scrapping the site was "unfair" and put strain on the site what we have now is considerable more unfair lol the same as most things they add or change they don't seem to think about what will happen at all.