-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No points docked for incomplete dailies/reverted health loss #417
Comments
Sounds buggy indeed. Although I wonder how this could have happened. I doubt the active/inactive settings should nor can affect already taken damage. Maybe you can post some more details about it while it is still fresh? System, browser? Do I get it right you logged out on Friday and logged back in on Sunday? |
System is Win7, Firefox 18.02. |
It's possible that the damage was never fully synced to the server. After you reloaded the page, were your other changes intact (the removing of the Sat/Sun markers)? |
I had something similar happen in that health got undeservedly refreshed. I took an undeserved reward, for which I took 9.9 dmg. Then I clicked a Habit and it gave me 20 gold and most of that health loss back!!! |
It's possible that the other changes reverted as well, but I did not really memorise that (I was so perplexed by my sudden health). |
@cleave29 did you also reload the page before you got back your healh, or did you get it right when you clicked on the habit? |
@toebu I got my health and 20g right when I clicked on my Habit. |
Yep, I can confirm this. I could reproduce it on my local server. |
i think it's related to #427, i'm going to work on that and follow up here when that's fixed |
yep, definitely #427. let's follow there |
I did not complete some dailies last Friday, and when I logged in on Sunday, it docked health at first - but after changing two other dailies (removing the markers for Sat and Sun) and reloading, I was back to full health again. Plus some of the technically inactive dailies were not grayed out.
The text was updated successfully, but these errors were encountered: