The premise of the game is that you have 30 "toggles". Some are simply ON/OFF switches and others you set to a single number (in a range). The feedback you get is if your previous day's toggles...
The premise of the game is that you have 30 "toggles". Some are simply ON/OFF switches and others you set to a single number (in a range). The feedback you get is if your previous day's toggles were correct or not. Based on that, your job is to determine the pattern of each toggle. The winner is the one that can have a perfect score for 30 days in a row.
It does require that you log in since this is a game meant to be played over many days.
Please let me know what you think or if you have any feedback.
This is exactly the kind of weird stuff I love about the Internet. I'm signed up and anxiously awaiting the scoring. The only feedback I have so far: Landing on the rules page is a little baffling...
This is exactly the kind of weird stuff I love about the Internet. I'm signed up and anxiously awaiting the scoring. The only feedback I have so far:
Landing on the rules page is a little baffling if you don't already have a bit of an idea what it is. Maybe add an "Overview" page which is exactly what you have in this comment, "The premise of the game..."?
For the number values, maybe add a label or a hover tooltip that gives the available range for that value?
It seems like the (N/A) text will be replaced with the previous day's score, but it seems like it would also be nice to see my full history for a given control. I'm going to want to keep track of it, so let me keep track of it right in the app, you know?
Similarly, a text box where I could keep notes about what I think each toggle does could be handy as well.
I appreciate your feedback and will be incorporating some of this right away. As for the full history, I purposefully left that out. I want to encourage people to develop their own way to track...
I appreciate your feedback and will be incorporating some of this right away. As for the full history, I purposefully left that out. I want to encourage people to develop their own way to track the history and analysis the data. I think part of the game is the meta around how to track things.
BTW, this is one of the key reasons I made this. Just trying to add to some of the old school fun on the internet. The times when not everything was instant gratification and monetization.
This is exactly the kind of weird stuff I love about the Internet.
BTW, this is one of the key reasons I made this. Just trying to add to some of the old school fun on the internet. The times when not everything was instant gratification and monetization.
Looks interesting in theory, though it's a long wait to see any sort of payoff. The first day's values are basically chosen at random, and you need another day to even begin to identify a pattern...
Looks interesting in theory, though it's a long wait to see any sort of payoff. The first day's values are basically chosen at random, and you need another day to even begin to identify a pattern from them. So even though I just started now, it'll be another 48 hours until I actually start working on the puzzle.
I feel like there should be some sort of "initial" score available - maybe just the score for each day if all values are set to default/minimum. On the other hand, I can see why that could leak a lot of information, and someone joining later would be at a much greater disadvantage (or maybe you could publish the historic scores for the "default" set).
Maybe the waiting and no initial dataset is a good feature in the world of instant gratification. I don't know. I guess I'll find out.
One more thing - I (and probably most people) found the website from Tildes, but I tried using the website before reading your comment here. You might want to mention the login requirement in the "rules/how things work" page.
Thanks for the feedback. Yes, I definitely designed this where the payoff is in the longer term. The first rounds are guesses. Then, as you have more data, you make more educated guesses.
Thanks for the feedback. Yes, I definitely designed this where the payoff is in the longer term. The first rounds are guesses. Then, as you have more data, you make more educated guesses.
You could allow people to play the first rounds without registering, and then ask for them to register later on when they are already hooked. It's more difficult to persuade someone to play a new...
It does require that you log in since this is a game meant to be played over many days.
You could allow people to play the first rounds without registering, and then ask for them to register later on when they are already hooked.
It's more difficult to persuade someone to play a new game if they need to register beforehand.
Wordle is different in that you go there, play, and you are done. This is a game that you need persistence over many days. I also wanted to allow people to utilize different devices to access the...
Wordle is different in that you go there, play, and you are done. This is a game that you need persistence over many days. I also wanted to allow people to utilize different devices to access the game and update their toggles.
I, too, am dissuaded due to having to sign up. Got enough internet accounts trying to get info, and I don't need yet another account. That's not to say the concept isn't interesting. I'd just...
I, too, am dissuaded due to having to sign up. Got enough internet accounts trying to get info, and I don't need yet another account.
That's not to say the concept isn't interesting. I'd just rather make the bs account on my trashy laptop when I decide to boot it back up and maybe check it out.
But, also going to add, Universal Paperclips is playable over days without an account and uses cookies (I believe?) to keep score.
I do appreciate the feedback. I just checked Universal Paperclips and it looks like an interesting game (and one I'll waste some time on!). It appears to be only keeping a local score, which...
I do appreciate the feedback. I just checked Universal Paperclips and it looks like an interesting game (and one I'll waste some time on!). It appears to be only keeping a local score, which definitely can work cookie based. Toggles has a scoreboard and the calculations have to happen server side. If the calculations happens client side, then people could just view the JavaScript and win right away.
I just grabbed the app after reading your comment and could not put it down for two hours. I must make more Paperclips. Seriously that game should have a warning it’s so addictive
I just grabbed the app after reading your comment and could not put it down for two hours. I must make more Paperclips.
Seriously that game should have a warning it’s so addictive
Comparing scores against other players requires server based storage. Client based storage can't be trusted. I understand that a login puts some people off. I also understand that the email part...
Comparing scores against other players requires server based storage. Client based storage can't be trusted. I understand that a login puts some people off. I also understand that the email part of it is maybe the most off-putting. If/when I put something else out like this I will definitely remove the email requirement. I'm seriously considering making the necessary modifications to this game to remove email.
Could you not calculate the local player score, send that back to the user (without adding it to the global scoreboard)? The only issue I see would be how to store that info on the client side...
Could you not calculate the local player score, send that back to the user (without adding it to the global scoreboard)? The only issue I see would be how to store that info on the client side without cheating. I think (if you’re willing to possibly reprocess each day) you could just store the user’s daily state info in an array, then send that up to the server whenever the user submits the next day. And that’s only if storing the user’s state information is vital. If you just need the score for each switch, then you could easily just send back that day’s scores and allow the user to keep that info.
If a user doesn’t want to sign in, they can still play, but their stats don’t affect the global stats.
I will be honest, I have 0 idea how you are storing that data server side, how anything is being calculated, what data needs to persist from day to day, and how worried you are that non-verified users will cheat by submitting lots of requests/score checks on a single day.
The score is calculated once a day, on the server side. For that to happen the server must store the user's selections. One of the foundations of the game is that the calculation only happens once...
The score is calculated once a day, on the server side. For that to happen the server must store the user's selections.
One of the foundations of the game is that the calculation only happens once a day. If a calculation was done every time a user submitted (and then handed back for local storage to the client), then someone would just submit 5,000 times in a day and figure out all the correct toggles.
I'm giving this a try! Just put down my first shot. I will note that I feel like the binary 'toggles' currently leave me absolutely shrugging at what they might be, that feels like that will take...
I'm giving this a try! Just put down my first shot.
I will note that I feel like the binary 'toggles' currently leave me absolutely shrugging at what they might be, that feels like that will take quite some time to deduce.
The numeric numbers though give me the feeling like I have to immediately start categorizing what I know about them (being vague on purpose to not ruin anything for others reading this, OP feel free to DM me if you want more details as to what I'm doing to categorize already), and I'm already taking my shot at the correct value for 5 of them. I'm already/immediately enjoying that!
My toggle method is more basic, I will
spoilers
leave them all off for the next week and see what happens each day.
Definitely an interesting concept though, and something maybe that would do very very well as an app with multiple 'levels'; for e.g. 99 cents or something? Just in case you felt like doing something more with it!
Hey mate, I'm interested in playing but find it odd that there's a requirement to provide email address to register. I get the point of tracking scores by requiring participants to log in but why...
Hey mate, I'm interested in playing but find it odd that there's a requirement to provide email address to register. I get the point of tracking scores by requiring participants to log in but why do you also need an email address?
The honest reason is that I just used Laravel's out of the box authentication and it uses email addresses. I would have spent an hour removing the email address functionality. As a bonus, I...
The honest reason is that I just used Laravel's out of the box authentication and it uses email addresses. I would have spent an hour removing the email address functionality. As a bonus, I figured it allowed people to retrieve their passwords, if they forget them.
I just simply promise that I'm a good guy, concerned about people's privacy, and hate spam.
Oh a small thing that might be fun - Maybe list the number of players that started playing on the same day you did? e.g. if I log in tomorrow, I see "you and 6 other players started their toggle...
Oh a small thing that might be fun - Maybe list the number of players that started playing on the same day you did? e.g. if I log in tomorrow, I see "you and 6 other players started their toggle adventure yesterday!"; and, I dunno, something in a week from now to let me know how many of my 'start group' are still going? That could breed a tiny bit of fun competition! Not saying usernames need to come into play here to be clear, but something small like the above might a nice add! You could even add the 'average' score of the start group?
Alternatively, maybe have something like "Welcome to day 7 of your toggle adventure - your score as of yesterday 23.00 UTC is [x]. On average, other players on day 7 have a score of [x]" to give...
Alternatively, maybe have something like "Welcome to day 7 of your toggle adventure - your score as of yesterday 23.00 UTC is [x]. On average, other players on day 7 have a score of [x]" to give you a clue as to how you're doing
Congratulations to Joey and Thorn! Great work to all the others that were close behind. And thank you to everyone for the interest you showed for this game. I made this game not because I thought...
Congratulations to Joey and Thorn! Great work to all the others that were close behind. And thank you to everyone for the interest you showed for this game.
I made this game not because I thought it would be wildly popular, but because I thought there would be some small number of people in the world that would find it interesting. To that end, I am very happy with the results. Again, thank you all!!
I will admit (and I think the calculations below will attest to) that I found it difficult to come up with 30 different toggles that were all consistently repeatable and didn't require info not available to the program itself.
I am considering a V2 that does make use of publicly available information (e.g., Was the DOW up or down at last market close?). Please let me know your interest in such a game.
Finally, the list of calculations. Please don't roast me on these. I know 24 is particular in impossible -- I don't remember why it went with it except to say that I was struggling to come up with more.
Spoilers
Always 1
Day of month is even or odd (0-1)
Month number is even or odd (0-1)
Day of year is even or odd (0-1)
Number of days in current month is even or odd (0-1)
Day of week (1-7)
Week # in month (1-7)
Week of the year (1-53)
Quarter of the year (1-4)
Number of letters in day name (6-9)
Number of days in month (28-31)
Number of letters in month name (3-9)
Number of month (1-12)
Number of days since start of week (0-6)
Number of days until Christmas (0-365)
Letter of the alphabet the month starts with (1-26, but really 1,4,6,10,13,14,15,19)
Day of week mod 4 (0-3)
Number of letters in day of week name is even or odd (0-1)
Number of letters in month name is even or odd (0-1)
0 for weekends and 1 for weekdays (0-1)
1 for the last day of the month, else 0 (0-1)
1 for the first day of the month, else 0 (0-1)
Day of the year mod 10 (0-9)
1 if palindrome date, else 0 (0-1)
1 if day name contains a 's', else 0 (0-1)
1 if day name contains a 's', else 0 (0-1) -- this was supposed to be 'n', but was a bug.
The good news about #24 is that The good news about #24 is... It'll always be 0 until 2030-03-02, so you have another 6 years to change it to something more reasonable before we notice (even if...
The good news about #24 is that
The good news about #24 is...
It'll always be 0 until 2030-03-02, so you have another 6 years to change it to something more reasonable before we notice (even if it's just always 0).
Regarding #7 and #15
Why were the ranges as big as they were? They can never use the highest number in their range. It obviously makes sense for #16 to have the full 26 options (so we can figure it out), but the 7 was a little misleading (there are never 7 Mondays in a single month), and the 366 made me worried about what the value should be on Christmas (0 or 366?).
I think a similar challenge with publicly available information could be interesting, though the difficulty could range from "slightly harder than this one" to "basically impossible" depending on the criteria you choose.
On the publicly available info, the data points would need to be non-obscure. I think that some scoping would be a good thing as well. I was thinking if I could find a list of APIs that had a variety of data and then scope the game to those APIs (and publish the APIs).
Regarding #24 > 4202024 would be a palindrome date per the calculation Oh wow. US-style dates without leading zeros would have thrown me off for a long time, especially for something as infrequent...
Regarding #24
> 4202024 would be a palindrome date per the calculation
Oh wow. US-style dates without leading zeros would have thrown me off for a long time, especially for something as infrequent as a palindromic date. I guess the first two cases (May 20, 2024, and April 20, 2025) might give it away, but I doubt I would have been able to figure that out with only the first data point.
#15
On Christmas (2023-12-25), I entered "0", and it was marked correct. It was both 0 days until Christmas (2023), and 366 days until Christmas (2024). I don't know how your algorithm verified things, so I suppose it's possible that both values were judged to be correct.
Since multiple people's streaks were broken when we switched months, I added a "CURRENT 30 SCORE STREAKS" widget on the dashboard to see only the current streaks of a score of 30.
Since multiple people's streaks were broken when we switched months, I added a "CURRENT 30 SCORE STREAKS" widget on the dashboard to see only the current streaks of a score of 30.
It's been amazing to see how many people have signed up so far. Thanks so much for the interest in this! I can't wait to see the daily scores rising as more and more toggle patterns are identified.
It's been amazing to see how many people have signed up so far. Thanks so much for the interest in this! I can't wait to see the daily scores rising as more and more toggle patterns are identified.
New month, so we've been able to collect a bit of data. Here are my thoughts so far (vague spoilers, but probably nothing useful). Some of these values are based on the month, and I suspect some...
New month, so we've been able to collect a bit of data. Here are my thoughts so far (vague spoilers, but probably nothing useful).
Some of these values are based on the month, and I suspect some are based on the year. I'd want more than 2 datapoints to know determine a pattern, so we're looking at New Year's before figuring out some of these values.
Some of the ranges I still have pretty much no data on. I picked a number, and I guess I just have to wait until it shows up, which could take a year (or more, in theory). If it gets to the point where I've figured out all but one value, it will be super frustrating, and I may not stick around past that point just for a guessing/waiting game.
I'm not sure how "rank" is calculated (on the Dashboard), but I think it's wrong (maybe backwards, where a higher number is better).
@mattw2121: How long do you anticipate it should take someone to (a) get it right 30 days in a row; and (b) actually figure out what all 30 values represent? I'm thinking right now that (a) can be figured out in about 6 months if you get lucky with some of the bigger ranges and might take up to a year if you're unlucky, but (b) would take multiple years.
Adding some of my own data Spoilers regarding how many toggles I have received correct matches on and how many toggles I think I have solved As of today, there is only a single toggle I have not...
Adding some of my own data
Spoilers regarding how many toggles I have received correct matches on and how many toggles I think I have solved
As of today, there is only a single toggle I have not yet received a correct guess on.
For the 13 ranges, I feel confident about having solved 10 of them, and think I know 2 more but need more time to verify.
The 17 Booleans I find are more tricky. I only really feel confident about 3 of them since there may be conditions on them which have not yet changed and thus are not yet detectable. Despite this, I have working theories for most of them and I've had about 75% success rate on them on average over the last week.
Another two weeks down. I messed up one day not hitting submit, because I was way too tired. Doesn't matter much as it didn't really affect any information I got and I'm definitely not on the top...
Another two weeks down. I messed up one day not hitting submit, because I was way too tired. Doesn't matter much as it didn't really affect any information I got and I'm definitely not on the top of the leaderboard.
Spoilers so far in the game
I have reasonable patterns for all but one toggle.
Some of the patterns (I would estimate about 4) I feel less confident about having down 100%, as they are either extrapolations (trying to find patterns in the patterns), or because they have multiple similarly simple interpretations which have been identical so far but would differ on certain dates in the future.
Maybe unsurprisingly, the one I have had no luck with is #15, with a range of 0 - 366. I don't expect anyone to discuss it here (figuring it out is the game, after all), but if I don't figure it out before someone has won, I would like to hear what people did to figure that one out.
30 days into the game for me, so I've put together a score overview of my own. It shows whether I guessed correctly for each toggle each day, but with the toggles unnumbered and sorted based on...
30 days into the game for me, so I've put together a score overview of my own. It shows whether I guessed correctly for each toggle each day, but with the toggles unnumbered and sorted based on the most recent failure so that from the image alone it should not be possible to deduce which toggle is which. It does not contain any of my actual guessed values.
I'm sure it's technically possible to draw some conclusions from looking at it, but I honestly doubt it will be useful to anyone in that sense.
I have a similar spreadsheet. It's interesting to see the progression of red (or in my case white) to green over the days. I also fat-fingered a couple values the other day when I was away and...
I have a similar spreadsheet. It's interesting to see the progression of red (or in my case white) to green over the days. I also fat-fingered a couple values the other day when I was away and tried to do it on mobile, so there's a patch of white in what I had hoped would be a good streak of 30s (until December, when I inevitably find out that I have no idea what some of these values are supposed to represent).
This game is interesting, as it produces a lot of things that I'd like to discuss, but can't for obvious reasons. I'll just say that I now think there's a non-zero chance that someone gets the 30-day streak in December, but if that doesn't happen, I think with the new year and February being a short month, I don't see it being completed until March.
Minor spoilers but nothing revealed I am having trouble with #12 as I've never been correct with it. It has a range of 3-9 and I left it unchanged for a week without luck. Then there are some...
Minor spoilers but nothing revealed
I am having trouble with #12 as I've never been correct with it. It has a range of 3-9 and I left it unchanged for a week without luck.
Then there are some toggles that's always been the same. I´m guessing something will happen there on January 1st.
I have figured out #15. Obviously, the range is to big to guess. Consider what it could be and try out different ideas based on that.
Comment on #12 I feel confident I have figured out #12 and did so fairly early. I would echo your comment on #15, except the range being too big to guess. Comment on #15 (including some of my...
Comment on #12
I feel confident I have figured out #12 and did so fairly early. I would echo your comment on #15, except the range being too big to guess.
Comment on #15 (including some of my thoughts on how I'm approaching it)
Yes, that is what I have been trying to do, but to no avail. Given that people have managed to figure it out I assume it can't be too complex, I just can't see the measure that fits with such a range.
If it is somehow related to the day of year (counting up from something, counting down to something), I would expect it to be either 0-365 or 1-366, to include a total of 366 different values for a leap year, but it is not. It is however the closest I have thought of so far, so I keep trying more and more spurious things with it unless I can think of some completely different approach.
Sorry, I've been on vacation and not able to reply until now.... My thoughts were it would take a month or so for people to mostly lock onto the correct values. Another 2-4 weeks to 100% sort...
Sorry, I've been on vacation and not able to reply until now....
My thoughts were it would take a month or so for people to mostly lock onto the correct values. Another 2-4 weeks to 100% sort things out and then the final 30 days to obtain perfect scores each day. So, really was thinking about 3 months total. We've seen a couple of perfect scores already, so I think some people are getting really close to determining the patterns.
Congratulations to the winner(s)! I was some days behind after having missed updating data for the 7th of December. Life has been hectic. Since I was behind, I took a gamble for the 31st, because...
Congratulations to the winner(s)!
I was some days behind after having missed updating data for the 7th of December. Life has been hectic. Since I was behind, I took a gamble for the 31st, because even if it was risky it was really the only way I could possibly secure a victory. It did not pay off.
Below are spoilers on what I think each toggle is, and then a few questions I have, primarily directed at @mattw2121.
Toggle descriptions
(?) indicates uncertainty, because the values have not changed enough to be certain one way or the other
Parity of year
Parity of day of month
Parity of month of year
Parity of day of year
Parity of days in month
Day of week (starting Monday)
Week of month
Week of year
(?) Quarter of year
Letters in name of day
Days in month
Letters in name of month
Month of year
Day of week, 0-index, starting Sunday (Sunday = 0, Saturday = 6)
Days until Christmas Day
Alphabetical index of first letter of name of month (A = 1, Z = 26)
Day of week, mod 4 (Monday = 1 mod 4, Sunday = 7 mod 4)
Parity of letters in name of day
Parity of letters in name of month
Is weekday
Is last day of month
Is first day of month
Last digit of day of year
(?) Has only ever been 0; I guessed it could be last day of year (it wasn't)
Is not Monday nor Friday
Is not Monday nor Friday
Is Tuesday or Wednesday
Is Tuesday
Is Thursday or Saturday
Parity of month of year
Question regarding all non-Boolean toggles
Was there some intent as to why some toggles had ranges that minimally spanned all possible values, while others did not? In particular, I am curious about why #7 and #15 were not reduced. As a side note, I think the range on #16 assists in figuring out the underlying pattern, so I understand why it would be as it is.
Question regarding toggle #24
This is the only toggle I feel acutely uncertain about in that it had never changed value and if the pattern repeats and is non-zero at any point, the duration of the pattern would need to be on the order of several months or more. Are you willing to share what it was?
Question regarding toggle #3, #18, #25, #26, #27, and #30
In pairs, these have been identical to each other; #3 and #30, #18 and #27, #25 and #26. Was this intentional? Were they different calculations that just happened to give the same output, or were they actually the same calculations?
Question regarding toggle #25 - #29
Was there some further semantic meaning behind this group of toggles, or were they each set to more or less random selections?
#25 and #26 could be first letter of name of day is in second half of alphabet
#27 could be parity of letters in name of day
#29 could be sum of alphabet index (A=1, Z=26) of letters in name of day > 100
It took me until 1 week ago to figure out what #16 was about, lost my first rank in average score I had since almost the beginning. Took a gamble on the 22nd of December on the #9, thinking it was...
It took me until 1 week ago to figure out what #16 was about, lost my first rank in average score I had since almost the beginning.
Took a gamble on the 22nd of December on the #9, thinking it was about seasons.
I think based on the rules of the game (the fact that it doesn't import any special libraries) it makes the calculation for seasons difficult or impossible without significantly more work from OP...
Took a gamble on the 22nd of December on the #9, thinking it was about seasons.
I think based on the rules of the game (the fact that it doesn't import any special libraries) it makes the calculation for seasons difficult or impossible without significantly more work from OP than was put in for any of the other calculations.
Congrats Thorn and Joey! I broke my 27 day streak because I was busy with family stuff at my normal time of filling this in, and then just completely forgot about it. Oops. Toggle Descriptions I...
Congrats Thorn and Joey! I broke my 27 day streak because I was busy with family stuff at my normal time of filling this in, and then just completely forgot about it. Oops.
Toggle Descriptions
I have the same guesses for everything except #1/#24, #3, #5, #19, and #30, where I didn't really put too much effort into guessing what they were - they just don't change on a daily basis. Your explanations make sense, but we'll have to wait another 7.5 hours to find out.
For 18, I actually just had the same guess as 27, rather than using parity, but you pointed that out in a later section. Doesn't really matter either way.
I don't know if the #3/#30 pair will continue. There's a lot of ways to get a single boolean value out of a month, and with only 3 points to form a pattern with, it wouldn't surprise me if these diverged within the next few months.
Regarding values that have never changed
You seem to have singled out #24 as the only one that hasn't changed, but I'm pretty sure #1 has always been 1, and #9 has always been 4.
I think you're correct on the parity for #1, but #24 could be almost anything - it could be the opposite parity, it could be "is a leap year", it could be "year is divisible by 6". Depending on what it is, it could take any number of years to conclusively determine it.
I also agree with #9 being the quarter of the year.
Hardest to figure out
Of the ones I think I've figured out, I struggled a lot with #7, #15, and #16. Once I got a the first correct value for each of them, they were mostly fine to figure out.
With #7, for some reason I started the whole thing by guessing 2 (because I thought the initial guess wouldn't really matter), and when that didn't change for 10 days, I tried 7. I could have just waited 3 more days and the 2 would have been correct. Instead, it took nearly a month for me to figure this one out.
#15 was just a lot of trial and error. It was clearly a span of a year, though I'm still confused as to why it's 0-366 instead of 1-366 or 0-365 (making the guess for Christmas Day a little harrowing), but I didn't know what the target date was or whether it was counting up or down.
Regarding the "singling out" and other toggles having that behavior, you are absolutely right. It's just that for the others I've to some extent based my guesses on context from other toggles....
Regarding the "singling out" and other toggles having that behavior, you are absolutely right. It's just that for the others I've to some extent based my guesses on context from other toggles. It's far from being certain, of course, but I have working hypotheses with some context so I don't feel as confounded by them (even if it may be mistaken and/or misguided). For the one I've singled out, I don't think I have any reasonable basis to make any specific prediction, so I'm curious about it.
Hey, I'm 'Joey' on the Toggles leaderboards. Good Game, everyone! I've never seen a game quite like this one, but I had a lot of fun riddling out everything. I spent my first week or so just...
Hey, I'm 'Joey' on the Toggles leaderboards. Good Game, everyone! I've never seen a game quite like this one, but I had a lot of fun riddling out everything. I spent my first week or so just collecting data and experimenting without worrying about scores, and once I had a good idea of what each control meant I went for it. Every day at midnight I would hand-compute my predictions until I was fairly confident in their meanings, then I wrote a program to compute them for me. I had hoped to automate the process of submitting my predictions, but Toggles lacked a submission API and had security in place to stop me from just CURLing my guesses in. I got off to an early lead like that, but accidentally fat-fingered a few of the inputs one day while traveling over the Thanksgiving holidays. I had always been worried that I would incorrectly enter my predictions (I was double and triple-checking my submissions every day lol), so I wrote a Chrome userscript that would display my computed guesses next to each control and highlight any controls that did not match my generated predictions so that I wouldn't botch my inputs again. Toggles' gameplay was interesting in that you couldn't do anything to get ahead once you fell behind - you just had to keep playing and hope that there'd be an upset that put you ahead. And we saw just that on 1 December when no one got a perfect score (probably because of input #19). I'm really happy this came down to a close race in the end - it wouldn't have been exciting if one person just led the pack the whole time. It was much more fun that the lead changed hands a few times before the field was leveled and Thorn and I could cross the finish line together. As it currently stands, I'm pretty confident I understand how 29 out of the 30 controls work. I can't say I fully understand input #19 - I have a guess but I won't know until tonight whether its correct. Other than that, though, great job @mattw2121 for writing the game and for using the numerical ranges as hints to their meanings. I had so much fun figuring out why input #10 specifically went from 6-9. Here's my understanding of the inputs:
Spoilers
Is the current quarter even
Is the date odd
Is the month odd
Is the day of the year odd
Is the month even
The day of the week
The week of the month
The ISO week number
The quarter
The number of letters in the day of the week's name
The number of days in the month
The number of letters in the month's name
The month number
The number of days since Sunday
The number of days until Christmas
The number of the alphabet corresponding to the month's first letter
The day of the week % 4 (giving the pattern 1230123)
Is today Tuesday or Wednesday
??? (my guess is Is this month the first month of the quarter, but I don't have enough data to say)
Is today a weekday
Is today the last day of the month
Is today the first day of the month
The last digit of the day of the year (or, mathematically, the day of the year % 10)
Hah, that's why I Spoilers set the two toggles that go from 1 to 7 to both 1. I think they might both be weekday counters, both starting on a different day. I set both to 1 because I have the...
Hah, that's why I
Spoilers
set the two toggles that go from 1 to 7 to both 1. I think they might both be weekday counters, both starting on a different day. I set both to 1 because I have the feeling at least one of them counts starting Monday (and I think the other one counts starting Sunday most likely - so if I see one is correct tomorrow then I'll put the other to 3 to test if the Sunday theory is correct too!)
Hey, I like the concept. I started yesterday and got a few hits right away. Some pure luck, and some I think I know what they represent. Allthough, there is one incorrect that seems obvious so...
Hey, I like the concept. I started yesterday and got a few hits right away. Some pure luck, and some I think I know what they represent. Allthough, there is one incorrect that seems obvious so there´s some shenanigans going on there.
I do have one question. Am I correct in assuming that the value ranges are static for each of the values? E.g. nr 10 will always be between 6 and 9?
Thanks for checking the game out. I'm glad you like the concept and are giving it a try! Yes, the value ranges never change. Each toggle value ranges are static. Just the value itself changes...
Thanks for checking the game out. I'm glad you like the concept and are giving it a try!
Yes, the value ranges never change. Each toggle value ranges are static. Just the value itself changes based on some unknown (to you, right now) criteria.
@mattw2121 I would like a better picture of how well people are doing, and how close they are to potentially winning. Could you do one of the following (or something else which fulfills the same...
@mattw2121 I would like a better picture of how well people are doing, and how close they are to potentially winning. Could you do one of the following (or something else which fulfills the same purpose):
Add a leaderboard score streak table, where entries show the latest score for a player and for how many days they have maintained at least that amount of points. Sorting would primarily be on descending score, with days maintained as the tiebreaker. I've uploaded a mockup on imgur.
Subsort the leaderboard top daily score on descending date. If a later score is listed above an earlier equal score, we can manually keep track of the streak of anyone who scores a high score (as long as it's fewer people than can fit in the leaderboard).
Adjust the leaderboard so that it is average score over the last 30 days (if it isn't already)
I agree with you and have been thinking similar things over the past few days. I'll make some adjustments to the leaderboards this evening when I get home from work.
I agree with you and have been thinking similar things over the past few days. I'll make some adjustments to the leaderboards this evening when I get home from work.
Thank you! One more thing to mention is that if I view the toggles on a vertical monitor (1080x1920), the numerical entries only have space enough to show a single digit. I added some custom CSS...
Thank you!
One more thing to mention is that if I view the toggles on a vertical monitor (1080x1920), the numerical entries only have space enough to show a single digit. I added some custom CSS using an extension to fix it for me, but if you could handle it that would be nice.
This is my simple injection to have enough space for three digits:
I think the streak calculation has an error. It's showing as 7 for me, but I think it should be either 5 or 8. I got 30 three days in a row, followed by 3 days of not 30, and currently at a 5 day...
I think the streak calculation has an error. It's showing as 7 for me, but I think it should be either 5 or 8. I got 30 three days in a row, followed by 3 days of not 30, and currently at a 5 day streak of 30. So if it's just the total number of days I got 30, it should be 8, but I think it should just be 5, as that's my current streak.
Also, I have no idea how "rank" is supposed to be calculated, but the number doesn't really make sense to me. I'm currently rank 28, despite showing up in the various leaderboards.
The premise of the game is that you have 30 "toggles". Some are simply ON/OFF switches and others you set to a single number (in a range). The feedback you get is if your previous day's toggles were correct or not. Based on that, your job is to determine the pattern of each toggle. The winner is the one that can have a perfect score for 30 days in a row.
It does require that you log in since this is a game meant to be played over many days.
Please let me know what you think or if you have any feedback.
This is exactly the kind of weird stuff I love about the Internet. I'm signed up and anxiously awaiting the scoring. The only feedback I have so far:
I appreciate your feedback and will be incorporating some of this right away. As for the full history, I purposefully left that out. I want to encourage people to develop their own way to track the history and analysis the data. I think part of the game is the meta around how to track things.
BTW, this is one of the key reasons I made this. Just trying to add to some of the old school fun on the internet. The times when not everything was instant gratification and monetization.
Looks interesting in theory, though it's a long wait to see any sort of payoff. The first day's values are basically chosen at random, and you need another day to even begin to identify a pattern from them. So even though I just started now, it'll be another 48 hours until I actually start working on the puzzle.
I feel like there should be some sort of "initial" score available - maybe just the score for each day if all values are set to default/minimum. On the other hand, I can see why that could leak a lot of information, and someone joining later would be at a much greater disadvantage (or maybe you could publish the historic scores for the "default" set).
Maybe the waiting and no initial dataset is a good feature in the world of instant gratification. I don't know. I guess I'll find out.
One more thing - I (and probably most people) found the website from Tildes, but I tried using the website before reading your comment here. You might want to mention the login requirement in the "rules/how things work" page.
Thanks for the feedback. Yes, I definitely designed this where the payoff is in the longer term. The first rounds are guesses. Then, as you have more data, you make more educated guesses.
You could allow people to play the first rounds without registering, and then ask for them to register later on when they are already hooked.
It's more difficult to persuade someone to play a new game if they need to register beforehand.
Wordle didn't require login. Just saying 😄
Wordle is different in that you go there, play, and you are done. This is a game that you need persistence over many days. I also wanted to allow people to utilize different devices to access the game and update their toggles.
I, too, am dissuaded due to having to sign up. Got enough internet accounts trying to get info, and I don't need yet another account.
That's not to say the concept isn't interesting. I'd just rather make the bs account on my trashy laptop when I decide to boot it back up and maybe check it out.
But, also going to add, Universal Paperclips is playable over days without an account and uses cookies (I believe?) to keep score.
I do appreciate the feedback. I just checked Universal Paperclips and it looks like an interesting game (and one I'll waste some time on!). It appears to be only keeping a local score, which definitely can work cookie based. Toggles has a scoreboard and the calculations have to happen server side. If the calculations happens client side, then people could just view the JavaScript and win right away.
I just grabbed the app after reading your comment and could not put it down for two hours. I must make more Paperclips.
Seriously that game should have a warning it’s so addictive
I disagree, Wordle kept running stats over time. These are stored in local storage and don't require login.
Comparing scores against other players requires server based storage. Client based storage can't be trusted. I understand that a login puts some people off. I also understand that the email part of it is maybe the most off-putting. If/when I put something else out like this I will definitely remove the email requirement. I'm seriously considering making the necessary modifications to this game to remove email.
Could you not calculate the local player score, send that back to the user (without adding it to the global scoreboard)? The only issue I see would be how to store that info on the client side without cheating. I think (if you’re willing to possibly reprocess each day) you could just store the user’s daily state info in an array, then send that up to the server whenever the user submits the next day. And that’s only if storing the user’s state information is vital. If you just need the score for each switch, then you could easily just send back that day’s scores and allow the user to keep that info.
If a user doesn’t want to sign in, they can still play, but their stats don’t affect the global stats.
I will be honest, I have 0 idea how you are storing that data server side, how anything is being calculated, what data needs to persist from day to day, and how worried you are that non-verified users will cheat by submitting lots of requests/score checks on a single day.
The score is calculated once a day, on the server side. For that to happen the server must store the user's selections.
One of the foundations of the game is that the calculation only happens once a day. If a calculation was done every time a user submitted (and then handed back for local storage to the client), then someone would just submit 5,000 times in a day and figure out all the correct toggles.
I'm giving this a try! Just put down my first shot.
I will note that I feel like the binary 'toggles' currently leave me absolutely shrugging at what they might be, that feels like that will take quite some time to deduce.
The numeric numbers though give me the feeling like I have to immediately start categorizing what I know about them (being vague on purpose to not ruin anything for others reading this, OP feel free to DM me if you want more details as to what I'm doing to categorize already), and I'm already taking my shot at the correct value for 5 of them. I'm already/immediately enjoying that!
My toggle method is more basic, I will
spoilers
leave them all off for the next week and see what happens each day.Definitely an interesting concept though, and something maybe that would do very very well as an app with multiple 'levels'; for e.g. 99 cents or something? Just in case you felt like doing something more with it!
Hey mate, I'm interested in playing but find it odd that there's a requirement to provide email address to register. I get the point of tracking scores by requiring participants to log in but why do you also need an email address?
The honest reason is that I just used Laravel's out of the box authentication and it uses email addresses. I would have spent an hour removing the email address functionality. As a bonus, I figured it allowed people to retrieve their passwords, if they forget them.
I just simply promise that I'm a good guy, concerned about people's privacy, and hate spam.
Oh a small thing that might be fun - Maybe list the number of players that started playing on the same day you did? e.g. if I log in tomorrow, I see "you and 6 other players started their toggle adventure yesterday!"; and, I dunno, something in a week from now to let me know how many of my 'start group' are still going? That could breed a tiny bit of fun competition! Not saying usernames need to come into play here to be clear, but something small like the above might a nice add! You could even add the 'average' score of the start group?
Alternatively, maybe have something like "Welcome to day 7 of your toggle adventure - your score as of yesterday 23.00 UTC is [x]. On average, other players on day 7 have a score of [x]" to give you a clue as to how you're doing
Congratulations to Joey and Thorn! Great work to all the others that were close behind. And thank you to everyone for the interest you showed for this game.
I made this game not because I thought it would be wildly popular, but because I thought there would be some small number of people in the world that would find it interesting. To that end, I am very happy with the results. Again, thank you all!!
I will admit (and I think the calculations below will attest to) that I found it difficult to come up with 30 different toggles that were all consistently repeatable and didn't require info not available to the program itself.
I am considering a V2 that does make use of publicly available information (e.g., Was the DOW up or down at last market close?). Please let me know your interest in such a game.
Finally, the list of calculations. Please don't roast me on these. I know 24 is particular in impossible -- I don't remember why it went with it except to say that I was struggling to come up with more.
Spoilers
The good news about #24 is that
The good news about #24 is...
It'll always be 0 until 2030-03-02, so you have another 6 years to change it to something more reasonable before we notice (even if it's just always 0).
Regarding #7 and #15
Why were the ranges as big as they were? They can never use the highest number in their range. It obviously makes sense for #16 to have the full 26 options (so we can figure it out), but the 7 was a little misleading (there are never 7 Mondays in a single month), and the 366 made me worried about what the value should be on Christmas (0 or 366?).I think a similar challenge with publicly available information could be interesting, though the difficulty could range from "slightly harder than this one" to "basically impossible" depending on the criteria you choose.
Regarding #24
4202024 would be a palindrome date per the calculationOn #7 and #15
For #7, it was an error on my part.For #15: https://www.timeanddate.com/date/durationresult.html?m1=12&d1=25&y1=2023&m2=12&d2=25&y2=2024 -- Was the value for #15 not 366 on 12/25/2023?
On the publicly available info, the data points would need to be non-obscure. I think that some scoping would be a good thing as well. I was thinking if I could find a list of APIs that had a variety of data and then scope the game to those APIs (and publish the APIs).
Regarding #24
> 4202024 would be a palindrome date per the calculationOh wow. US-style dates without leading zeros would have thrown me off for a long time, especially for something as infrequent as a palindromic date. I guess the first two cases (May 20, 2024, and April 20, 2025) might give it away, but I doubt I would have been able to figure that out with only the first data point.
#15
On Christmas (2023-12-25), I entered "0", and it was marked correct. It was both 0 days until Christmas (2023), and 366 days until Christmas (2024). I don't know how your algorithm verified things, so I suppose it's possible that both values were judged to be correct.Since multiple people's streaks were broken when we switched months, I added a "CURRENT 30 SCORE STREAKS" widget on the dashboard to see only the current streaks of a score of 30.
Thanks, I've been doing it by hand for the last few days. It's like you're reading my mind :D
It's been amazing to see how many people have signed up so far. Thanks so much for the interest in this! I can't wait to see the daily scores rising as more and more toggle patterns are identified.
New month, so we've been able to collect a bit of data. Here are my thoughts so far (vague spoilers, but probably nothing useful).
Some of these values are based on the month, and I suspect some are based on the year. I'd want more than 2 datapoints to know determine a pattern, so we're looking at New Year's before figuring out some of these values.
Some of the ranges I still have pretty much no data on. I picked a number, and I guess I just have to wait until it shows up, which could take a year (or more, in theory). If it gets to the point where I've figured out all but one value, it will be super frustrating, and I may not stick around past that point just for a guessing/waiting game.
I'm not sure how "rank" is calculated (on the Dashboard), but I think it's wrong (maybe backwards, where a higher number is better).
@mattw2121: How long do you anticipate it should take someone to (a) get it right 30 days in a row; and (b) actually figure out what all 30 values represent? I'm thinking right now that (a) can be figured out in about 6 months if you get lucky with some of the bigger ranges and might take up to a year if you're unlucky, but (b) would take multiple years.
Adding some of my own data
Spoilers regarding how many toggles I have received correct matches on and how many toggles I think I have solved
Time will tell if my confidence is misplaced.
Another two weeks down. I messed up one day not hitting submit, because I was way too tired. Doesn't matter much as it didn't really affect any information I got and I'm definitely not on the top of the leaderboard.
Spoilers so far in the game
I have reasonable patterns for all but one toggle.
Some of the patterns (I would estimate about 4) I feel less confident about having down 100%, as they are either extrapolations (trying to find patterns in the patterns), or because they have multiple similarly simple interpretations which have been identical so far but would differ on certain dates in the future.
Maybe unsurprisingly, the one I have had no luck with is #15, with a range of 0 - 366. I don't expect anyone to discuss it here (figuring it out is the game, after all), but if I don't figure it out before someone has won, I would like to hear what people did to figure that one out.
30 days into the game for me, so I've put together a score overview of my own. It shows whether I guessed correctly for each toggle each day, but with the toggles unnumbered and sorted based on the most recent failure so that from the image alone it should not be possible to deduce which toggle is which. It does not contain any of my actual guessed values.
I'm sure it's technically possible to draw some conclusions from looking at it, but I honestly doubt it will be useful to anyone in that sense.
Expand for a link to the score summary
https://i.imgur.com/eWn4c9y.png
I have a similar spreadsheet. It's interesting to see the progression of red (or in my case white) to green over the days. I also fat-fingered a couple values the other day when I was away and tried to do it on mobile, so there's a patch of white in what I had hoped would be a good streak of 30s (until December, when I inevitably find out that I have no idea what some of these values are supposed to represent).
This game is interesting, as it produces a lot of things that I'd like to discuss, but can't for obvious reasons. I'll just say that I now think there's a non-zero chance that someone gets the 30-day streak in December, but if that doesn't happen, I think with the new year and February being a short month, I don't see it being completed until March.
Minor spoilers but nothing revealed
I am having trouble with #12 as I've never been correct with it. It has a range of 3-9 and I left it unchanged for a week without luck.
Then there are some toggles that's always been the same. I´m guessing something will happen there on January 1st.
I have figured out #15. Obviously, the range is to big to guess. Consider what it could be and try out different ideas based on that.
Comment on #12
I feel confident I have figured out #12 and did so fairly early. I would echo your comment on #15, except the range being too big to guess.
Comment on #15 (including some of my thoughts on how I'm approaching it)
Yes, that is what I have been trying to do, but to no avail. Given that people have managed to figure it out I assume it can't be too complex, I just can't see the measure that fits with such a range.
If it is somehow related to the day of year (counting up from something, counting down to something), I would expect it to be either 0-365 or 1-366, to include a total of 366 different values for a leap year, but it is not. It is however the closest I have thought of so far, so I keep trying more and more spurious things with it unless I can think of some completely different approach.
Sorry, I've been on vacation and not able to reply until now....
My thoughts were it would take a month or so for people to mostly lock onto the correct values. Another 2-4 weeks to 100% sort things out and then the final 30 days to obtain perfect scores each day. So, really was thinking about 3 months total. We've seen a couple of perfect scores already, so I think some people are getting really close to determining the patterns.
Congratulations to the winner(s)!
I was some days behind after having missed updating data for the 7th of December. Life has been hectic. Since I was behind, I took a gamble for the 31st, because even if it was risky it was really the only way I could possibly secure a victory. It did not pay off.
Below are spoilers on what I think each toggle is, and then a few questions I have, primarily directed at @mattw2121.
Toggle descriptions
(?) indicates uncertainty, because the values have not changed enough to be certain one way or the otherQuestion regarding all non-Boolean toggles
Was there some intent as to why some toggles had ranges that minimally spanned all possible values, while others did not? In particular, I am curious about why #7 and #15 were not reduced. As a side note, I think the range on #16 assists in figuring out the underlying pattern, so I understand why it would be as it is.
Question regarding toggle #24
This is the only toggle I feel acutely uncertain about in that it had never changed value and if the pattern repeats and is non-zero at any point, the duration of the pattern would need to be on the order of several months or more. Are you willing to share what it was?
Question regarding toggle #3, #18, #25, #26, #27, and #30
In pairs, these have been identical to each other; #3 and #30, #18 and #27, #25 and #26. Was this intentional? Were they different calculations that just happened to give the same output, or were they actually the same calculations?
Question regarding toggle #25 - #29
Was there some further semantic meaning behind this group of toggles, or were they each set to more or less random selections?
#25 and #26 could be first letter of name of day is in second half of alphabet
#27 could be parity of letters in name of day
#29 could be sum of alphabet index (A=1, Z=26) of letters in name of day > 100
It took me until 1 week ago to figure out what #16 was about, lost my first rank in average score I had since almost the beginning.
Took a gamble on the 22nd of December on the #9, thinking it was about seasons.
For 24, I think it is
(#24)
going to be about leap yearI think based on the rules of the game (the fact that it doesn't import any special libraries) it makes the calculation for seasons difficult or impossible without significantly more work from OP than was put in for any of the other calculations.
Congrats Thorn and Joey! I broke my 27 day streak because I was busy with family stuff at my normal time of filling this in, and then just completely forgot about it. Oops.
Toggle Descriptions
I have the same guesses for everything except #1/#24, #3, #5, #19, and #30, where I didn't really put too much effort into guessing what they were - they just don't change on a daily basis. Your explanations make sense, but we'll have to wait another 7.5 hours to find out.For 18, I actually just had the same guess as 27, rather than using parity, but you pointed that out in a later section. Doesn't really matter either way.
I don't know if the #3/#30 pair will continue. There's a lot of ways to get a single boolean value out of a month, and with only 3 points to form a pattern with, it wouldn't surprise me if these diverged within the next few months.
Regarding values that have never changed
You seem to have singled out #24 as the only one that hasn't changed, but I'm pretty sure #1 has always been 1, and #9 has always been 4.I think you're correct on the parity for #1, but #24 could be almost anything - it could be the opposite parity, it could be "is a leap year", it could be "year is divisible by 6". Depending on what it is, it could take any number of years to conclusively determine it.
I also agree with #9 being the quarter of the year.
Hardest to figure out
Of the ones I think I've figured out, I struggled a lot with #7, #15, and #16. Once I got a the first correct value for each of them, they were mostly fine to figure out.With #7, for some reason I started the whole thing by guessing 2 (because I thought the initial guess wouldn't really matter), and when that didn't change for 10 days, I tried 7. I could have just waited 3 more days and the 2 would have been correct. Instead, it took nearly a month for me to figure this one out.
#15 was just a lot of trial and error. It was clearly a span of a year, though I'm still confused as to why it's 0-366 instead of 1-366 or 0-365 (making the guess for Christmas Day a little harrowing), but I didn't know what the target date was or whether it was counting up or down.
Regarding the "singling out" and other toggles having that behavior, you are absolutely right. It's just that for the others I've to some extent based my guesses on context from other toggles. It's far from being certain, of course, but I have working hypotheses with some context so I don't feel as confounded by them (even if it may be mistaken and/or misguided). For the one I've singled out, I don't think I have any reasonable basis to make any specific prediction, so I'm curious about it.
Thanks for playing @thecakeisalime! I was wondering what happened when I saw your streak bust :(.
Thanks for playing Malle, I made a first level post with all the calculations.
Hey, I'm 'Joey' on the Toggles leaderboards. Good Game, everyone! I've never seen a game quite like this one, but I had a lot of fun riddling out everything. I spent my first week or so just collecting data and experimenting without worrying about scores, and once I had a good idea of what each control meant I went for it. Every day at midnight I would hand-compute my predictions until I was fairly confident in their meanings, then I wrote a program to compute them for me. I had hoped to automate the process of submitting my predictions, but Toggles lacked a submission API and had security in place to stop me from just CURLing my guesses in. I got off to an early lead like that, but accidentally fat-fingered a few of the inputs one day while traveling over the Thanksgiving holidays. I had always been worried that I would incorrectly enter my predictions (I was double and triple-checking my submissions every day lol), so I wrote a Chrome userscript that would display my computed guesses next to each control and highlight any controls that did not match my generated predictions so that I wouldn't botch my inputs again. Toggles' gameplay was interesting in that you couldn't do anything to get ahead once you fell behind - you just had to keep playing and hope that there'd be an upset that put you ahead. And we saw just that on 1 December when no one got a perfect score (probably because of input #19). I'm really happy this came down to a close race in the end - it wouldn't have been exciting if one person just led the pack the whole time. It was much more fun that the lead changed hands a few times before the field was leveled and Thorn and I could cross the finish line together. As it currently stands, I'm pretty confident I understand how 29 out of the 30 controls work. I can't say I fully understand input #19 - I have a guess but I won't know until tonight whether its correct. Other than that, though, great job @mattw2121 for writing the game and for using the numerical ranges as hints to their meanings. I had so much fun figuring out why input #10 specifically went from 6-9. Here's my understanding of the inputs:
Spoilers
Congrats, Thorn!
Congrats Joey!
Are you counting weeks as having started on Monday or Sunday?
Who says the calculator doesn't start weeks on Wednesday? :) This is the point of the game. Finding the patterns.
Ah, fair play :)
Hah, that's why I
Spoilers
set the two toggles that go from 1 to 7 to both 1. I think they might both be weekday counters, both starting on a different day. I set both to 1 because I have the feeling at least one of them counts starting Monday (and I think the other one counts starting Sunday most likely - so if I see one is correct tomorrow then I'll put the other to 3 to test if the Sunday theory is correct too!)Good question to think of!
Sounds neat, shame it requires a login.
Hey, I like the concept. I started yesterday and got a few hits right away. Some pure luck, and some I think I know what they represent. Allthough, there is one incorrect that seems obvious so there´s some shenanigans going on there.
I do have one question. Am I correct in assuming that the value ranges are static for each of the values? E.g. nr 10 will always be between 6 and 9?
Thanks for checking the game out. I'm glad you like the concept and are giving it a try!
Yes, the value ranges never change. Each toggle value ranges are static. Just the value itself changes based on some unknown (to you, right now) criteria.
@mattw2121, did you change the range for 17? I'm pretty sure I put 4 yesterday and it got changed to 3.
I started on 2023-10-26 and I have its range down as 0-3. Maybe you confused it with 9 (with range 1-4)?
No, I did not change anything. I can also promise there is no place in the code that could overwrite a toggle choice by a user.
@mattw2121 I would like a better picture of how well people are doing, and how close they are to potentially winning. Could you do one of the following (or something else which fulfills the same purpose):
Add a leaderboard score streak table, where entries show the latest score for a player and for how many days they have maintained at least that amount of points. Sorting would primarily be on descending score, with days maintained as the tiebreaker. I've uploaded a mockup on imgur.
Subsort the leaderboard top daily score on descending date. If a later score is listed above an earlier equal score, we can manually keep track of the streak of anyone who scores a high score (as long as it's fewer people than can fit in the leaderboard).
Adjust the leaderboard so that it is average score over the last 30 days (if it isn't already)
I agree with you and have been thinking similar things over the past few days. I'll make some adjustments to the leaderboards this evening when I get home from work.
Thank you!
One more thing to mention is that if I view the toggles on a vertical monitor (1080x1920), the numerical entries only have space enough to show a single digit. I added some custom CSS using an extension to fix it for me, but if you could handle it that would be nice.
This is my simple injection to have enough space for three digits:
Updates made. Thanks for playing and thanks for the suggestions!
Also, congrats on the perfect score today!
I think the streak calculation has an error. It's showing as 7 for me, but I think it should be either 5 or 8. I got 30 three days in a row, followed by 3 days of not 30, and currently at a 5 day streak of 30. So if it's just the total number of days I got 30, it should be 8, but I think it should just be 5, as that's my current streak.
Also, I have no idea how "rank" is supposed to be calculated, but the number doesn't really make sense to me. I'm currently rank 28, despite showing up in the various leaderboards.
I'll check into these calculations when I get home later. Sorry for any confusion it has caused.