Vote on the next frame inputs in the comments below, using any of the provided keys with a space between them. Note, if you're discussing things instead of voting put a '?' at the start of your comment to make it ignored for voting. One voter per project/profile
What text converts to which buttons can be found here https://cohost.org/CohostPlaysFramePerfectly/post/1479578-inputs-and-the-contr
Like, okay. Twitch Plays Pokémon always takes a long time to beat the game, right? It took them over 16 days straight just to beat Pokémon Red. That's a crazy long time to spend just playing through the main story of a Pokémon game! Except for TPP the input stream is consistent, and even in democracy mode the inputs are coming in way faster than one frame at a time. The game runs continuously.
Meanwhile, this bot advances one frame every hour.
So, let's do the math. I'm not entirely sure what framerate the original Link's Awakening runs at (it's hard to Google because of the Switch remaster), but it's safe to say that it's probably either about 30 fps or about 60 fps. I'll go with 30 fps for now.
So, 30 frames per second, times 60 seconds per minute, times 60 minutes per hour. This gives us the number 108,000. In other words, we're running the game at 1/108,000 speed.
Okay, well, that's pretty big already, but how long is Link's Awakening? It's an old Gameboy game, it can't be too huge, right? Let's check How Long To Beat.
Oh.
That's longer than I thought, at least. Certainly no Tears of the Kingdom, but fairly long for a Gameboy game.
But, alright, 14 hours can't be too bad, right? Just multiply it by 108,000.
Fuck me. Alright. What's that in days?
... I mean years.
...
Christ alive.
And, by the way, I lied to you. Because during the process of working all this out, I thought to look up the framerate of the Gameboy itself. The Gameboy has a framerate of 60 fps. All of this math doubles. We're playing at 1/216,000 speed. We will be playing Link's Awakening for 345 years.
And all of that is assuming we don't play the game significantly worse than the average player, which if you know anything about these kinds of things... We absolutely will play the game poorly. Not to mention, who knows if Cohost will still be in use 300 years from now, if it'll even be up 300 years from now. If the internet itself will even still be up 300 years from now. Plus, y'know, the fact that none of us will be alive at that point to see the game get completed.
So, uh. Maybe we should up the framerate a little bit.
I'm working off and on on an emulator specifically to run as a discord bot and realized this would be an issue. Instead of Link's Awakening, it was going to be Castlevania: The Adventure
To overcome these things, I came up with a "simple" solution
- a person can input up to three commands
- these commands can include button/dpad presses, a dpad/button hold (measured in milliseconds, and a wait command where they could also input a millisecond value
- the hold/wait commands are capped at 1000ms
Now BECAUSE this is a discord bot in its own channel, I'm not held to the standards of a site like cohost where you don't want to completely flood a feed, but I think multiple commands and a wait/hold system might make things slightly less... uhhh... centuries long
