146 replies · 4.57k views · thread synced · 4 days ago
· View on torn.com
About this thread
Posts archived:147 / 147 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
147
Discussion span
→
Authority score
46 / 100
Historical score
44 / 100
Story score
72 / 100
Engagement score
87 / 100
People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.
Most-liked replies
Proxima[1879587]Wiki Editor
· 83 likes · Definitely a lesson in actually playing the game instead of becoming overly reliant on supplementary tools.
bogie[148747]Admin
· 72 likes · It's a really unfortunate situation. Restoring chains from an API issues sets a dangerous precedent imo, players should be expected to watch their chains by actually watching their chains - rather than be overly reliant on third party programs to …
the api currently has an issue and i figured people need to know. i mean not all of us check the bugs threads and given the api thinks it is working whilst giving out of date info others might fall foul of it too.
it has cost us a chain so do not trust it till the issue is fixed.
Anyone can be an offline chain watcher if you all have alarms set. When your members put their names down on the list it's because they are active and prepared to commit that time to be a hawk, it can be tough, it does take up your time but if you don't place that level of concentration on your responsibility then those 5 minutes will pass by quickly.
I understand the frustration, I have been in failed chains and understand that it does suck. However, I would consider careful reflection in your preparations for the future.
Yeah always sucks when that happens. But can’t really blame the API. I’ve killed chains due to similar issues, and in the end it’s my own fault for trusting the tools to be 100% reliable as opposed to setting manual timers for the chain.
Restoring chains from an API issues sets a dangerous precedent imo, players should be expected to watch their chains by actually watching their chains - rather than be overly reliant on third party programs to watch it for them. Anyone can be a chain watcher at that point, but if you have people actively watching chains then this is what they should be doing. We cannot reasonably verify a chain broke from someone failing to get a notification and shouldn't restore based on that.
I appreciate there's a fault with the API, and it giving incorrect data is worse than none at all. We've disabled the API for now, the API going down entirely is never something we'd restore chains for - we're currently debating this niche case scenario where it got "stuck" for the 4 factions involved - I certainly am aware they would like that very much, but this decision would is not something we can take lightly in cases of future precedents as well as feeding entitlement.
Chains dropping after 5-6 hours of this issue means every one is watching doing their part and didn't need the timers for 5-6 hours, it was only a fail safe valve and nobody was notified that it broke, and when the one very first time you face the API bug issue, is the time chain is drops without anyone being aware it's possible, thus leaving all your collective efforts of 7 days to waste because of an API bug that wasn't your fault and neither you were told about.
Restore the Chains when API issue from Torn's end is fixed
I just think our biggest issue was that it wasn’t publicized or spread out so that we could be aware of it. Ours dropped a bit after but we never even had a clue that it was an issue until we found the bug report
Not sure if we should be considered lucky or not. The API bug happened about 500 hits away from our 50k target.
It nearly costs us the chain as no notification came in from discord or any of the other scripts. We had to resort to manual-eyes-glued to the chain timer, and not just 1 but 3 chain watchers.
Pity those who still has a long way to achieve their target. Chain watching without redundant backup security is risky business. I would advise factions to have 2 chain watchers 3 chain watchers at all times.
It's just sad to see chains that have been nursed for this long die, because torn wasnt fully functional. Hey, we worked through the horrible lag, the new day crashes, and everything in between.
What a disappointing game. After playing it for more than half my life I cant even laugh at the unprecedented attacks jokes, it's just poorly performing and that was my mistake for expecting a fully functional platform and trying to play within it.
Amazing work to the factions that persevered and kept going this year. It's only going to get worse next year as more people level up their baskets, exchange, and get energy to make more hits.
Hopefully torn PLANS for next years 'surprise' halloween event. I expect it to start sometime around 12:00 on the 25th, but I know what a surprising schedule this is every year that they don't expect attacks.
TL; DR- We work in similar fields. I can't imagine blaming a customer for my data issues and then accusing users of sending others to downvote you. That is generous that you assume anyone needs to be sent to downvote you.Bogie reached out to me and this is valid and I was 100% wrong. People were downvoting him intentionally and that's pretty lame. I intended to downvote him as my faction is affected and I thought his comment was directed at us but I was wrong and am sorry @Bogie. Thanks for the conversation.
Overly-reliant is a responsibility dodging claim. If the API from Torn is f**ked up, how would a customer know what the scope of that issue is and why would any of that be their responsibility?
Did you do anything to notify your customers? Did you stop the transmission of inaccurate information? One chain broke 5 hours after the issue happened but why were you allowing customers to access inaccurate data that entire time? It seems like it is a feat of players that they were able to survive one-quarter of a day with inaccurate information rampant rather than a fault of theirs.
"I appreciate there's a fault with the API and it giving incorrect information is worse than none at all."
Then do something about it. If you cannot prove conclusively how a chain broke, isn't that your own problem? Why is your inability to understand the extent of the issue that was happening for hours the problem of your customer base? How can you appreciate it without addressing it? "Hey, it was our site issue but it is your fault for trusting our data..." Imagine if a company sold products to a customer and when they didn't work, the company blamed its customers for trusting their product to function as designed and advertised. Or what if a company sold subscriptions and when the paid content didn't function as designed, the company blamed the customer for expecting it to? Your lackadaisical response would have merit if the issue was with the services that were using the Torn API data because Torn cannot control that. But Torn absolutely could control this situation.
What is the worst that would happen if you restored users chains? Would Torn taking the blame for a dropped chain cause anarchy?