Skip to content
TORNLIFE More

Supreme lag

Started by TheOtherMerlin [1925529] on in Bugs & Issues.

11 replies · 82 views · thread synced · 9 days ago · View on torn.com
About this thread

Posts archived: 12 / 12 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
12
Discussion span
→
People posting
3
Likes on archived posts
0
Posts by staff, officers and moderators
3
Authority score
56 / 100
Historical score
29 / 100
Story score
33 / 100
Engagement score
46 / 100
Porny [604593]

Closing, if it happens again try grabbing a screenshot, as it helps diagnose the problem easier and faster, thanks.
TheOtherMerlin [1925529]

Usually, here's what happens. There's on average about four people attacking rowdy at the same time. So when he's just coming out of the hospital:

The attack button is clicked
Then, several attempts are made to initiate the fight
The weapon is pressed multiple times, followed by a prolonged delay (lag) of approximately 5-6 seconds
Finally, the screen is progressed, to the "ajax" error page
25 Energy is still lost, with no compensation
aurel1 [1046304] Admin Staff

I just checked your attack page load times (server only), it's all between 0.2-0.4 seconds, this looks not like a lag issue. Can you please tell, if this happens on a single server every time or on different ones? Perhaps in some specific time?

And what you actually mean on "several attempts are made to initiate the fight" - start fight button is not working when you press it?

Accroding energy spent - if attack is still you active you can just refresh the page, such error will not cause it to end?
TheOtherMerlin [1925529]

"start fight button is not working when you press it?"

That's exactly it

"Can you please tell, if this happens on a single server every time or on different ones? Perhaps in some specific time?"

I'm not sure, sorry :(
aurel1 [1046304] Admin Staff

The fact that load time was fine in all your attacks during last 3 days can tell that this is a client-side problem. Will be good, if you will continue to report, if such things will happen again (you can mail me directly with all required info).