Hey everyone, straight: the play time is going to be reset! Why? As some of you might have noticed something was wrong with the data, I did find out why: Spoiler Consider a database with the columns like "session_id, player_id, server_id, play_time, login_time, logout_time" In order to avoid sql injections the data is passed via prepared statements. This means the "command"/statement is being written with question marks instead of the value. Later on you assign the question marks their value. The problem here was that the statement was at the top of a 300 line page and the binding happened somewhere in the middle/end. It was logical - on how the information was passed - to bind it in the order of session_id, play_time -> but the statement was the other way around.. So the session_id was bound to play_time and play_time as the session_id.. Code: logPlayerSessionUpdate.setInt(1, sessionId); logPlayerSessionUpdate.setInt(2, playTime); instead of Code: logPlayerSessionUpdate.setInt(1, playTime); logPlayerSessionUpdate.setInt(2, sessionId); In the end all data is useless, which explains why some players have enormous amounts of playtime, due to other players giving them those
i told you that Doctorfoxwolf shoulda had the top playtime, not those people with OVER 200 DAYS of playtime
I had 176d (I was at like 17d after it reset when 1.7.10 came out) -_- Pretty sure Doctor and Decnav were the top 2 though
Just as a reminder for anyone and all who reads about the playtime reset. We staff will be even more watchful than before, for anyone using any setup to bypass the afk-kick, once the reset is done. Anti-afk machines are against the rules of MyM. Tries to gain playtime with these setups, as well as continuously loading base/map can be punishable.
Remembers me of that one time I made a afk machine .... to let someone write a book. Had to do that to prevent another player getting kicked in the midst of all that writing and having to do it again. XD
