This game has an in-game timer and IGT is shown on the leaderboard. It seems to be sorted by real time however. There are runs that would be higher up on the leaderboard if IGT was the default timing method. If this game has an in-game timer why is it not used to determine leaderboard position?
You can download the game for free here: https://z-bill.itch.io/eyeballs
If you can, please consider donating to the developer.
When you start a new save file you have to beat every minigame in each area to unlock the Mayor's "test" at the end of the area. That test consists of several minigames you have already done and you need to beat them all in a row without failing one to pass the test and advance to the next area.
In this run however, the test at the end of the second area just didn't happen. I could just go the last area immediately. I have no idea how or why this skip happened and I'm not sure I consider this a new WR.
Maybe I'll make a separate category for this but I'm not sure it makes sense before we figure out how this skip works.
There are timestamps in the video description to skip to the start of the run and to the moment when the skip happens.
Could you please provide the frames on which time starts and ends? Current rules say:
[quote]Timing starts upon entering the first level and ends upon finishing the last level.[/quote]
- Which frame is counted as "entering the first level"?
- Which frame is counted as "finishing the last level"?
Thanks!
EDIT: I just re-timed my current PB and just took guesses as to when time starts and ends and got the exact run time to the frame so I assume:
- First frame: when the first level become visible.
- Last frame: the first frame after Beeny/Toree disappear into the bee hive.
Correct?
Since this game uses milliseconds to time runs I would like to ask the moderators to provide the exact frames when time starts and end in the game rules. Thank you very much! 🌻🐝
Today I got a sub 15 run on Level 3 and while cutting the video for upload I noticed how quickly I killed Cobrabot, it just took 20 milliseconds. So I watched the "fight" frame-by-frame and I noticed the boss died before I even pressed the attack button which can be seen on the input display. Here's a video of the frame-by-frame view and my theory that the attack might be "stored" somehow when entering the level while pressing attack. This is worth looking into more because 20 milliseconds is hell of a quick kill.
As of today, the Beat the Game leaderboard uses time without loads. This change was made to ensure fairness among runners regardless of whether they play on PC or Switch (which has longer load times than the average PC) or in case they have a slower PC than other runners. The rules have been updated, please read them to be up-to-date.
The timing for IL runs has been changed to time without loads as well. This means you can now submit level PBs from full-game runs to the IL leaderboard.
Thanks and good luck!
Done with the Beat the Game category, will do Low% another time. The change to time without loads caused a change in the leaderboard positions: I'm back on 1st place while CaptNinja6 dropped to 2nd.
I'm currently re-timing all runs. Once I'm done I'll update the times and change the leaderboard to loadless.
No, I don't. For all games I have to do it, I do it manually: add all load times together and then subtract that from the whole run time.
This leaderboard recently got its first run on console. Since the Switch is known for having slower load times than PC I did a sample test to compare the load times of the console run to my own PB on PC. I compared the load times of the Prologue and of Levels 1 and 2. The timing goes as follows: the first frame the selected translation of "No!" starts spinning and shrinking to the last frame that text is spinning and growing after the level transition. Here are the results:
SWITCH: Prologue: 4.866 seconds Level 1: 4.733 seconds Llevel 2: 5.400 seconds Total: 14.999 seconds
PC: Prologue: 4.567 seconds Level 1: 3.633 seconds Level 2: 4.233 seconds Total: 12.433 seconds
That is a difference of 2.5 seconds on the first three levels alone. This will add up over the course of the run. Therefore, I see no other way to ensure fairness for all runners than to switch (pun not intended) the leaderboard to loadless time. If you have a better idea to time out loads than the timing described above please let me know. I'll wait a bit for feedback and then re-time the current runs and adjust the rules.
You mean all achievements except "Say No x times"? That would include achievements such as creating your own character which wouldn't really make sense in my opinion, let alone the fact it wouldn't be 100% without the 99999 tines saying no achievement. But a speedrun with all the "bonus" encounters could be fun, I just think we would need to think of a name that fits the category better.
The category I'm suggesting would include:
- Beating the game
- Playing the new video game of Alex
- Winning a staring contest
- Becoming staring contest champion
- Subscribing to the coach's channel
- Doing the parking ticket thingy
- Being nice to the janitor imp
- Delivering the love letter
That seems like a good balance between Any% and Low% because you can go fast while still swing all the "hidden" content. If anybody wants to run this, I'll add it as a category.
I really wanna run this game but the leaderboard has no clear rules regarding the timing and several runs have the time shown in LiveSplit as their actual time which is absolutely not correct. Please fix this. I am happy to help re-time runs.
This run is listed as being 3:39:31 hours long but it's actually 3:39.310 minutes. I guess that should be corrected?
When I became moderator for this game I did not know how runs were timed since the rules did not specify the exact timing. I made rules for frame-perfect timing which don't match exactly with the older times on the leaderboard. So I'm asking the community how to solve this issue. Here are two proposals:
1. Re-time all runs according to the current frame-perfect timing.
OR
2. Change the timing to full seconds, removing milliseconds.
The issue with the first option is the fact that the runs of kojlax don't have video proof anymore and their account has been deleted so there's no way to contact them. How should we solve this problem?
Please answer which option you would prefer. If you have another proposal feel free to discuss it. Please answer until July 8th. Thanks!
Thanks for bringing this to my attention. The current timings might all be a bit off because they have been verified before I became a moderator and I'm not sure how the runs were timed exactly. For the run you are talking about the time shown in LiveSplit has been entered as the actual time which is definitely not correct since LiveSplit is timed by human button presses which are not accurate. We might have to re-time all runs (that are still availaible), I'm gonna evaluate the situation.
