Skip to content
TORNLIFE More

Attack timeout issue

Started by Wiber [2065939] on in Bugs & Issues.

3 replies · 27 views · thread synced · 4 days ago · View on torn.com
About this thread

Posts archived: 4 / 4 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
4
Discussion span
→
People posting
3
Likes on archived posts
0
Posts by staff, officers and moderators
2
Authority score
55 / 100
Historical score
28 / 100
Story score
30 / 100
Engagement score
38 / 100
Wiber [2065939] · #1

I'm currently posting this with TornTools enabled.

At the end of an attack after defeating an enemy, a 30 second timer begins while the attacker has the choice of Leaving, Mugging, or hospitalising their opponent. 

This timer does not seem to be taking effect unless the person has that tab active. Here is an example (resulting in a chain timeout), of the fight not registering for 36 seconds after the final hit is made.


While in this case it might be argued that I was on another tab, what happens if I closed the attack tab instead? Did the attack even happen? Given that allowing the post attack period to time out is a well worn chaining strategy, is this a bug? 

aurel1 [1046304] Admin Staff · #2

"This timer does not seem to be taking effect unless the person has that tab active" - not really, in this case it wil be handled by cron that may have some delays, however auto-leave will work anyway, even if there was no direct request from the client.

Wiber [2065939] · #3

"however auto-leave will work anyway, even if there was no direct request from the client." - not at all. In this case the screenshot clearly shows the finishing hit at 4:37:00 and the auto-leave not occurring until 04:37:36 when the tab was made active again. 

CloudJumper [1636201]Staff · #4

The auto-leave works regardless of whether you are viewing the page. If you are actively viewing the page, it will auto-leave around 30-31s mark if there are no issues. If you are not viewing the page, the auto-leave will trigger around 37-38s mark (you making the tab active does not play a role in this). There's a deliberate delay in place when the auto-leave takes place in the background like that to avoid different issues that can be caused by introducing effective locking. We have reduced this background auto-leave delay to 2 seconds for the time being. If things look fine, we can keep these changes, else we will go back to the old system.

 

Thanks!