Internal times update schedule
Moderator: Moporators
- Kopaka
- 39mins club
- Posts: 6611
- Joined: 23 May 2002, 13:59
- Team: LAME
- Location: In a northern danish city beating YOUR record.
- Contact:
Internal times update schedule
With various talks going on about how to store and present internal times, one point I'd like to discuss is the update schedule. Currently internal times are updated weekly on EOL, WRs are updated whenever wr table is updated manually (once a month-ish), pawq's tt list is updated monthly-ish, eolstats whenever people bother to upload their stats.
So, if we ignore all practical and technical aspects, what would be your preferred update schedule for internal times?
PRs: weekly, instant, on demand, something else?
WRs: when wr table is updated, weekly, instant, something else?
So, if we ignore all practical and technical aspects, what would be your preferred update schedule for internal times?
PRs: weekly, instant, on demand, something else?
WRs: when wr table is updated, weekly, instant, something else?
Re: Internal times update schedule
PRs: i prefer instantly, but any of the options are fine tbh
WRs: ABSOLUTELY NOT instantly, unless 100% efficient antixiit implemented (its super easy atm to get a time before getting kicked/banned, speaking from my filthy cheater experience).
if it's cool with both EOLmans and px to split from legacy and go our own way, weekly would be great. otherwise right after px table.
WRs: ABSOLUTELY NOT instantly, unless 100% efficient antixiit implemented (its super easy atm to get a time before getting kicked/banned, speaking from my filthy cheater experience).
if it's cool with both EOLmans and px to split from legacy and go our own way, weekly would be great. otherwise right after px table.
Re: Internal times update schedule
PRs: instant
WRs: when wr table is updated while we are still in px system
WRs: when wr table is updated while we are still in px system
Re: Internal times update schedule
Dunno why Elma still lives in year 2000, make instant and put public WR recs. What does some xiited time matter, it's removed and it is no problem anymore because you don't use old retarded table system anyway so it is not going to be visible anywhere
Prestigious member of 14.6x Tutor14 club
Re: Internal times update schedule
my 2020 vote goes for: everything instant for internals. Moposite crew can keep on updating tables every now and then if want.
I just find it annoying nowadays, and I bet it would be a huge relief to developers involved to get rid of those old systems.
I just find it annoying nowadays, and I bet it would be a huge relief to developers involved to get rid of those old systems.
Re: Internal times update schedule
I vote instant
Re: Internal times update schedule
my 2010 vote goes for instant updates
my 2020 vote goes to who cares, 3 wrs a year anyway
my 2020 vote goes to who cares, 3 wrs a year anyway
[carebox]
Re: Internal times update schedule
One problem with instant WRs is that old WR statistics wouldn't be comparable anymore. One solution would be making new statistics based on days not tables and leave old stats as they are. Many stats would be quite different, some in good way, some in bad way. Let's take a quick look at the current ones (https://moposite.com/records_wr_statistics.php):
* WR Development: based on days would be more interesting than now based on tables (+)
* WR Total Time development: maybe make the snapshots in monthly basis? (+/-)
* WR Ages: based on days - this wouldn't work anymore because the last WR owners would eventually win this after enough time passes (-)
* WR Owners: same problem here if we use monthly snapshots (-)
* Most WRs: I guess this stats wouldn't change much which is great because I think this is one the most interesting one! (+/-)
* Most Tables With WRs: most months with WRs? Again the last WR holders would eventually win (-)
* Most Different WRs: same as with Most WRs so would probably work quite same which is nice (+/-)
* Improvements (4x different): no effect (+/-)
So from the statistics point of view: 3x minus, 1x plus and many neutral so eventhough it would be a bit worse (?) it's not that bad?
Maybe this conversion table = month would add also some new fun because the last/first day of the month is when a "statistics snapshot" is done so after that they could be post-analysed when now it's quite random and matter of px and other mans if no one makes new WRs. I mean someone (if wanted) could update somewhere "ok after January 2041 Zweq finally passes Abula in the number of WRs" even when no one is playing anymore. But I want to underline again that some stats would get quite boring after no one is playing anymore unless we add some extra rules.
Maybe it's possible to add a small correction to the pattern that the monthyl snapshot is taken only if there is at least 1 new WR? Maybe that would add some fairness between old veterans and last warriors and still keep the logic simple enough?
So if this idea is good then we have another question: should the new rules start from 2020 beginning (or whenever possible) or from year 2000 so the stats are re-generated? I think (but not suggest it) that we could even continue with the table numbers from where we are now, accept WRs instantaly but increment the table number only in the first second of the month (if there are new WRs). This decission could be done after we see how the statistics would look in the monthly based "tables".
Let's take a quick look also what are the pros and cons to not regenerate old stats:
Pros:
- fair to old veterans
Cons:
- not so simple (there would be an arbitrary date when the logic changes)
- the new system needs more logic to program
But I think the fairness to old veterans could be analysis if it's too bad or/and we could always have both because probably Moposite will have those old stats anyway and the new system could have the new stats. And from the historical point of view I don't need to fix my article (the most important aspect! ) but just add new stats when it's good time for that and add some extra analysis like "zyntifox lost his new WR in 6 tables in a row but now we know that ..."
So maybe it's a good idea to have the new stats based on active months and leave old stats as they are if the new stats are somewhat fair to old veterans. I understand this would probably mean Moposite is not hosting the official WR table then anymore but maybe it's time to handle the torch to next? (or how to say it in English) I'm sure Moposite can still contribute Elma in some other ways
* WR Development: based on days would be more interesting than now based on tables (+)
* WR Total Time development: maybe make the snapshots in monthly basis? (+/-)
* WR Ages: based on days - this wouldn't work anymore because the last WR owners would eventually win this after enough time passes (-)
* WR Owners: same problem here if we use monthly snapshots (-)
* Most WRs: I guess this stats wouldn't change much which is great because I think this is one the most interesting one! (+/-)
* Most Tables With WRs: most months with WRs? Again the last WR holders would eventually win (-)
* Most Different WRs: same as with Most WRs so would probably work quite same which is nice (+/-)
* Improvements (4x different): no effect (+/-)
So from the statistics point of view: 3x minus, 1x plus and many neutral so eventhough it would be a bit worse (?) it's not that bad?
Maybe this conversion table = month would add also some new fun because the last/first day of the month is when a "statistics snapshot" is done so after that they could be post-analysed when now it's quite random and matter of px and other mans if no one makes new WRs. I mean someone (if wanted) could update somewhere "ok after January 2041 Zweq finally passes Abula in the number of WRs" even when no one is playing anymore. But I want to underline again that some stats would get quite boring after no one is playing anymore unless we add some extra rules.
Maybe it's possible to add a small correction to the pattern that the monthyl snapshot is taken only if there is at least 1 new WR? Maybe that would add some fairness between old veterans and last warriors and still keep the logic simple enough?
So if this idea is good then we have another question: should the new rules start from 2020 beginning (or whenever possible) or from year 2000 so the stats are re-generated? I think (but not suggest it) that we could even continue with the table numbers from where we are now, accept WRs instantaly but increment the table number only in the first second of the month (if there are new WRs). This decission could be done after we see how the statistics would look in the monthly based "tables".
Let's take a quick look also what are the pros and cons to not regenerate old stats:
Pros:
- fair to old veterans
Cons:
- not so simple (there would be an arbitrary date when the logic changes)
- the new system needs more logic to program
But I think the fairness to old veterans could be analysis if it's too bad or/and we could always have both because probably Moposite will have those old stats anyway and the new system could have the new stats. And from the historical point of view I don't need to fix my article (the most important aspect! ) but just add new stats when it's good time for that and add some extra analysis like "zyntifox lost his new WR in 6 tables in a row but now we know that ..."
So maybe it's a good idea to have the new stats based on active months and leave old stats as they are if the new stats are somewhat fair to old veterans. I understand this would probably mean Moposite is not hosting the official WR table then anymore but maybe it's time to handle the torch to next? (or how to say it in English) I'm sure Moposite can still contribute Elma in some other ways
40:02,71 (151.) | WCup4: 8. | 3x WR | 3x GAA | 11x FEM | KOM | The History of Elasto Mania (1995-2018)
Re: Internal times update schedule
And maybe to decrease confustion we could use the term "snapshot" (or some better?) instead of tables so we would always know which ones we are talking about. I wouldn't want to forget the statistics made in old logic like zynti's 6 WRs in a row etc and this would get confusing and eventually forgotten if we are going to have"old table statistics" and "table statistics"
40:02,71 (151.) | WCup4: 8. | 3x WR | 3x GAA | 11x FEM | KOM | The History of Elasto Mania (1995-2018)
- Kopaka
- 39mins club
- Posts: 6611
- Joined: 23 May 2002, 13:59
- Team: LAME
- Location: In a northern danish city beating YOUR record.
- Contact:
Re: Internal times update schedule
It's happened like a couple of times in eol history that best time in an int was cheated/bugged, and it was very obvious most of them, so I don't think it's a big issue.
Exactly.
I was thinking, even if we update instantly, there would still be some "WR update" happening once a month, for a couple reasons. Someone should still check the recs for verification, they could still make a news post so people who don't watch the stats every day will know new WRs are made, and then you have the option to still have table numbers for the sake of stats. This update could still happen on old wr tables on moposite and the news there if wanted.
Re: Internal times update schedule
ez weekly ) more tension
<Pawq> at a gym you have only 3 options: 1. have your eyes closed, 2. stare at yourself, 3. stare at others, all of which are either super boring or disgusting
- Grace
- 38mins club
- Posts: 4849
- Joined: 19 Nov 2005, 10:45
- Location: Deep in your Imagination, Twirling your Dreams and Weaving your thoughts.
Re: Internal times update schedule
I don't mind it being weekly wrs rather than instant, gives some chance to investigate any big new times for verify.
Otherwise I think delay unnecessary.
Otherwise I think delay unnecessary.
Cyberscore!
___________________________________________________
Targets: 6 Legendary, 23 WC, 20 Pro, 5 Good | AvgTT: 39:59:96
___________________________________________________
Targets: 6 Legendary, 23 WC, 20 Pro, 5 Good | AvgTT: 39:59:96
Re: Internal times update schedule
The wr table is sacred. I do not like instant, i think WRs need verification, and i think table# is important for statistics too. I think "weekly" is good, but no need to make new wr table if there are no new wrs. So within one week of a wr submission would work imo.
whatever makes sense to those that do the work is probably the more important input though.
whatever makes sense to those that do the work is probably the more important input though.
God Bless America
Re: Internal times update schedule
Yea, imagine having instant updates with no verification and getting super excited about some crazy record only to see it disappear the next day because it turned out buggy.
Re: Internal times update schedule
imagine times being instant only in eol and on elma online site and moposite mans continue to update wr table normally
- Kopaka
- 39mins club
- Posts: 6611
- Joined: 23 May 2002, 13:59
- Team: LAME
- Location: In a northern danish city beating YOUR record.
- Contact:
Re: Internal times update schedule
EOL has been updated now to show times instantly. I felt there was enough support for this. I realise some people still preferred delayed updates, especially for WR's, and I'm not just ignoring those, but there's some technical challenges around this, such as non WR's would never be completely instant if we have to delay WR's, and even with the system we had there were some issues. All in all pros are bigger than cons. I fast tracked it a bit since the current update script broke (9 year old php code) so times have not been updated for a few weeks, and I didn't want to rewrite it if it wasn't needed.
How it works exactly is like this: All times in EOL in-game and on elma.online is updated instantly the moment you drive the time. WR's are still verified and updated to moposite wr table ~monthly. This also applies to other levelpacks with weekly updates such as EOL pack and Twenty.
elma.online has been updated to show things like total times, personal times and highligt of new times on levelpacks. Note that elmaonline.net is not updated to reflect this change, in fact you should now use elma.online for all things statistics and times.
The number of times a cheated/bugged time has appeared in eol in an int that was WR and not very obviously a bug/cheat is almost non existant, so I don't see this as an issue.
How it works exactly is like this: All times in EOL in-game and on elma.online is updated instantly the moment you drive the time. WR's are still verified and updated to moposite wr table ~monthly. This also applies to other levelpacks with weekly updates such as EOL pack and Twenty.
elma.online has been updated to show things like total times, personal times and highligt of new times on levelpacks. Note that elmaonline.net is not updated to reflect this change, in fact you should now use elma.online for all things statistics and times.
Re: Internal times update schedule
only on christmas eve, things are more exciting when you have to wait for them