13 replies · 192 views · thread synced · 8 days ago
· View on torn.com
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
4
Likes on archived posts
7
Posts by staff, officers and moderators
7
Authority score
60 / 100
Historical score
37 / 100
Story score
44 / 100
Engagement score
58 / 100
Most-liked replies
bbeebs[2313341]
· 2 likes · No problem. So does that mean our 2.5k chain was actually a 2499 chain?
IHTl[2403739]
· 2 likes · That stealth I even hid from the game.
Chedburn[1]Admin
· 1 likes · Oh I've just realised the date, Valentine's Day, when we were having all the issues. I think that makes perfect sense now. I think we can close this and we can be pretty sure it won't happen again. Thanks.
I wrote a script in a google sheet to generate a chain report. It does that by fetching all of the attacks using the /attacks API endpoint in a loop. I noticed one of my chains was missing an attack. It was a 2.5k chain, but the attack count my script gathered was 2499.
So I did some digging and figured out exactly which attack was missing - who the attacker was and even the attack number in the chain - it's #1112.
I then did some experimenting with different from time when calling the API, but there seems to be no way to get that missing attack. I was able to get that person's previous and next attacks in the same response from the API, but hit #1112 is still missing.
Am I doing something wrong or is there some other possible explanation? I can provide more details upon request.
PS: I also posted this in API Development, so the thread there can be removed.
CloudJumper[1636201]Staff · #2
Just to confirm, you are saying that the API system doesn't show one of the attacks which was counted in the chain and is present in your faction log?
Can you please paste the faction news log here? We need the timestamp and the initiator of the attack for the logs that are missing in the API.
Yes, that is indeed what seems to be the problem. That chain is from February though, so I can no longer see the log entry.
This is the closest I can point you to: - chain ID: 9540799 - chain hit # (the number that is returned as "chain" in /attacks): 1112 - attacker ID: 2403739 - timestamp should be between 1581706638 and 1581706861 (these are timestamps of that attacker's previous and next attack)
I have determined the attacker by comparing my report to torn's war report - and that person showed one attack less in my report. I hope that helps.