Change 24 hour time checks to "once per day"

Ticket #160
Opened by: Midnight
Status: Closed- Finished
Feature Request
1/27/16 12:21 pm 1/27/16 12:21 pm
1/18/18 9:52 am 1/18/18 9:52 am


Right now servers can be bumped and voted on once every 24 hours. I suggest changing it to a once a day. Basically instead of waiting 24 hours to bump or vote  you can do it at anytime once a day. So for a example, once at 11pm and again the next day at 1am.

Comments (22)

1 - 20 of 22

said 2018-01-18 09:52:44
Cyprezz set status to Closed, set resolution to Finished.
Changed it to vote once per day instead of every 24 hours a while back.
said 2017-04-21 15:40:16
Ralex set status to Accepted.
Paril said 2017-04-21 15:14:18
This ticket will be finished soon. Cyprezz had said he will be tackling it, potentially by next week.
SpaghettiGoat said 2017-04-20 22:35:22
This issue is very important to the server's functionality, but nothing has been done about it, despite it being talked about for years now!

If anyone is confused about the issue, PMC currently measures voting and bumping times as "once every 24 hours", but instead it should be once every calendar day. That way, a user can vote once at any time on the 1st day, once any time on the 2nd day, once any time on the 3rd day, etc. Instead of voting at 6pm on the 1st day and having to wait until after 6pm on the 2nd day to vote again. It would be infinitely more convenient for voters.

To combat abuse, I propose:
  • There additionally be a 4-hour wait period, so someone cannot vote or bump at 11:59pm and again at 12:01am.
  • Calendar days are based on a user's set time zone, and the time zone can only be changed once every, say, two months.

jh34ghu43gu said 2017-04-03 20:48:44
(I finished typing this then realized this ticket also applied to server bumps so just know that vote can be replaced with bump)

I was interested if anyone ever brought this up so I went searching and found this. I am very disappointed there is no conclusion to this ticket after a full year. I was honestly hoping to see a good reason for keeping this system (one vote every 86,400 seconds) because I could not think of one. Almost every vote site I have voted on and had my previous server vote on used this system or at least had a 30 min. grace period (one vote every 23 hours 30 min.)
From what this thicket has shown we have a simple pro/con as follows:
Pros: People don't continually get forced to vote later and later in the day. Still only gets 1 vote per day
Cons: Possible abuse

The only abuse that could occur is if pmc made the "day" defined by the client and not by the server. If you define the day as 00:00:00 EST - 23:59:59 EST there are no cons to switching to this system and it baffles me that perhaps the most popular minecraft voting site still hasn't changed to this system.
All in all, pmc should change to 1 vote per account from 00:00:00 EST - 23:59:59 EST (aka a calendar day) or close this ticket with a valid retort on why the current system is better so everyone like me can have some closure as to why this system is still being used.
notme1 said 2016-09-25 12:59:25
Since I suggested same thing and was noted as duplicate, I'll just drop it here:

This is annoying, that I have remember last time, when I voted previously.
Because of this I vote every 2 days usually - I don't bother coming back to vote later.
MC voting website: allows us to vote every day after midnight.
Pepijn said 2016-02-09 10:18:50
Still wondering what you will use to define the "day".
said 2016-02-08 14:12:14
Midnight modified ticket description.
dr_Cheesecake said 2016-02-08 11:39:36
said 2016-02-08 11:37:08
Paril set title to Change 24 hour time checks to "once per day".
Paril said 2016-02-02 22:35:09
Functionally it's not the same, because the current system requires the user to click on the exact same millisecond otherwise the time shifts every time. I can see why they hate it, lol
Ralex said 2016-02-02 21:15:24
It really depends on the context to me. Functionally, it's the same, it's more who could benefit from it. I feel like a constant reset value is a bit more rigid than a simple 24 hours, which is more "simplier" for me to get.
Paril said 2016-02-02 19:43:45
They want to change it to by day, so basically "if it's the same month/day/year then they can't vote again". It's not a bad idea.
Pepijn said 2016-02-02 05:52:17
It's a very bad idea to start basing votes on the server times them-self as they can be manipulated.
Thereby like Ralex mentioned, it's really more trouble to compute whether a player is allowed to vote with this suggested method.
Ralex said 2016-01-31 16:24:59
The system really is not monitoring at all. It should just be recording when you voted. DB queries for this kind of system and the existing are exactly the same, except for a very minor math difference (if last vote time is < 24 hours or if last vote time is less than midnight).
Jetra said 2016-01-31 10:28:28
You can set "the day" as when the server's clock hits midnight (no pun intended). At 00:00 EST where PMC is located, it's easier to do a full reset other than monitoring about a thousand different timers.
Ralex said 2016-01-28 13:58:56
0 benefit really, and probably harder to track, because what defines "the day"? 24 really is a better system to me.
Pepijn said 2016-01-27 16:33:53
It's way harder to do it this way and it has in my opinion no real benefit.
Jetra said 2016-01-27 14:01:12
Could we also do this for votifier stuff? I tend to forget a lot of times when I vote and I know there's probably people who can't keep up a 24 hour thing as the later you do it, the later you HAVE to do it until you eventually have to lose a day.
Midnight said 2016-01-27 12:47:46
It would be nice for those people who gradually lose time and bump it later and later. And I can see the time going off of PMC time rather than users.

1 - 20 of 22




© 2010 - 2018