Picture says it all really, I reached 33% destruction on an arson requiring 60% or more, but once the fire was out I had the option to collect the payment.
Successful failed arson
Started by Hamfest_Reyes [2572177] on in Bugs & Issues.
About this thread
Posts archived: 8 / 8 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
- 8
- Discussion span
- →
- People posting
- 3
- Likes on archived posts
- 4
- Posts by staff, officers and moderators
- 5
- Authority score
- 58 / 100
- Historical score
- 44 / 100
- Story score
- 43 / 100
- Engagement score
- 56 / 100
Most-liked replies
![[image: i.imgur.com]](https://i.imgur.com/HLC2k1l.png){kind=link}
According to the log final damage was actually 95
Oh ok nice just a display issue then. Percentages keep going up whenever I switch windows or whatever.
What exactly was the behavior of the damage %? Did it smoothly land on 33% or did it race up and just stay there? We need a live case to check this because per the backend logs the damage looks fine. And if the Collect button was enabled, then the frontend did receive the correct values through the poll (else the Collect button would not have been enabled).
It went up smoothly at the beggining, then I switched tabs and forgot about it, then came back to this.
I will leave this open for now, if you can reproduce the issue reliably and leave the bugged row open for the developers to troubleshoot, I can ask the devs to check.
I have replicated the issue and passed on the necessary details to Wouter. I will mark the report as confirmed.
Thanks!
We have pushed a potential fix for this issue. Please comment here or post a new thread if you see something like this happen again.
Thanks!