bugs

Time played gets reset when a bot is reset but the per day amount doesn't so people end up with stupid time played amounts.
Is this working as intended(tm)?
I can't google these things so I needed to create a new thread.

just look at my average per day if you need a reference for this has me at 7 minutes a day after reseting 2 days ago

That's how I noticed this ;)

working as intended(tm)?

I think that's called a "feature".

Hmm, I don't think I've considered this.

Played time indeed gets set to 0 when a bot is reset and the played time per day indeed uses the bot creation time instead of the most recent bot reset time. So for consistency, either (a) played time should not get set to 0 upon bot reset or (b) the played time per day should use the most recent bot reset time.

I guess it would be weird to do (a) at this point, plus I imagine folks are used to it by now and like being able to see how much played time it took to accomplish certain things after a reset. So I will do (b) soon^TM unless anyone has anything else to share.

Alright, (b) is done now. The played time per day calculation will now use last reset time (if available) instead of original bot creation time.

Related to whats going on here?

I noticed that awhile back myself. This is the only other bot I've seen with an alleged playtime of over 136 years: http://bots4.net/profile/53943/Mister-Fantastic

Weird.

And another one

The played time on those are all the same, and they never change.

Yea it's the maximum value that can be stored in seconds. I converted it to 4,316,432,707 seconds but I think that's due to improper conversion either on my part or the converter I used with such a large amount of time (leap years etc maybe, not sure). 4294967295 would make a lot more sense and is within what I'd call within margin of error for something like this, so I'm going with that.

It's the same thing with a bug I pointed out before with 114 being the highest level displayed on the beta HoF, experience values being what was topped out for storage. Only this time it's unsigned.

More likely an integer storage limit, rather than a seconds one, but yeah I agree. Likely a data storage limit that is occurring.

Integer is what I meant to imply with it being unsigned this time yea

In response to the posts starting 2017-05-09 (i.e. since my last response), I think this is unrelated to the original bug/fix from this thread. To test, I rolled back the fix for the original bug reported here locally and still saw the problem, so it's not a calculation problem. I also see that some of the affected bots have been reset and others have not, so that makes me think it's not related to the resetting process itself either.

There's a newer bug thread discussing just the "136 year club" problem, so let's continue discussion there:

http://bots4.net/forum/3/7157

*click*