GermanyStats of my main emu account: 33 deaths 2053 jumps 1:26 playtime
surely not because the game deleted all my saves for a while, I estimate I have about 160 emu hours in reality
The run was timed after running by determining the first and last frame instead of trying to hit those frames as accurately as possible by hand while running. This provides more accuracy.
I did a run of Monkey Meadows Easy Co-op just now and we lost time (nearly 30s) to the current WR despite popping the bloons earlier (you can see the bloons far less). The rounds start earlier for them too despite the bloons being longer on screen. Can someone explain if we made some mistake or how we could save that time? Our run: Current WR:
Sorry to say it: Start press to timing start is kinda bad, because you incorporate loads into the time that way, which I want to eliminate in close-to-perfect situations like ILs. The end at rainbow idea isn't bad (I also thought about it, its really fine actually), but I want to keep all lw timing rules as similar if possible (exept lw1 ILs, those are a wild ride).
Also, not to be mean or anything, a mod should be able to reliable retime frame-perfectly. Cubz is correct with the fact that we have so little runs (less than just Archero) that more mods aren't needed and could probably only improve verifying time, although you'd have to be as active or more active than me for that. Maybe one day in the future we need more mods and you are an option, then you might become a mod. Currently it wouldn't really make anything better if you'd be a mod. (Also just hitting verify-mods are kinda useless (although I believe you wouldn't be one of them)
3 things:
- You have no runs of any of the lw games
- Do you know how to reliably retime (frame-perfect, duh)?
- Do you have any reasonable improvement ideas?
(Also I can't make you mod, only the super-mod can)
Since now pnps and some other stuff seems to have changed, you might have updated, but want to try pnps and don't care about your savefile (It's only the play time really, you can get everthing else in 30 mins), here is an apk for the old version: https://drive.google.com/open?id=1F7-LNoyvZMgtWDDuA4rRFQjmgVJ5OseC
These two leps world games still need the "mobile" tag, the other two (LW1, LW3) already have it: Lep's World 2: https://www.speedrun.com/lw2/ Lep's World Z: https://www.speedrun.com/lwz/ I'm moderator of both.
Turns out, even more differences in levels with no tree. The sign in 0-2 for example, is earlier on iOS than on Android.
Since I now discovered that end fading starts at different times for some people, the end is changed to passing a specific close-to-end object to remove the different ends and end slowdowns. Also old runs with a different tutorial etc had to be removed.
Timing by starting with the first move or no black bars at the bottom/start removes loading time from the timing. Most (maybe all) runs will be retimed for this additional accuracy.
Like the title says, this game (and even more the other games of this series) have problems: Missing categories, for example the ILs. This game at least has the tutorial and World 1, but all other worlds are missing. The other games don't even have those ILs. Also new category ideas like All Gold seem to be ignored. I know (from my own experience) adding new categories takes a while, so the solution at the bottom would take work off of @ClingingTomcat8, while still supplying the players interested in new ILs/other new categories with these. The next problem: Missing timing optimization. This problem grows bigger and bigger, the more optimized levels get. Mainly, it is unclear when the time should start. Starting it pre-first movement adds loading time into the time, making the timing unfair for people with slow phones (that don't lag, because lagboosting, you know). Unifying those timings to first-movement eraticates that problem. But there is another part in this: Because of @ClingingTomcat8 s choice to switch to ms (smart choice), old runs are still on the leaderboards with second-accuracy instead of millisecond-accuracy (which has a problem too, but more on that later). To make the leaderboards fair to people of both sides (down-rounding in s in unfair to ms-runners, up-rounding is unfair to s-runners), the old runs could be retimed for more accuracy. Again, this takes time, but the solution at the bottom takes this extra load off of @ClingingTomcat8 as well. A problem partially caused by unclear timing start: Retiming. While every runner tries to submit a run with the best accuracy they have, retiming is a necessary step to ensure no runner accidentally mistyped a number or switched two times of runs with each other. Currently, most runs with ms look like this: X.YZ0 (X, Y and Z stand for random one-digit numbers). Seems ok, right? No. The most common recording framerates, 30 and 60, both only produce X.Y00 (and X.Y50 for 60) as times. X.YZ0 mostly appears when using normal timers, for example livesplit while running. These are often a good approximation, but do not reach the accuracy of frame-perfect timing. Even if players (like me) provide frame-perfect timing, they should be double-checked (like every other run, since this game has no IGT and players could accidentally upload the wrong run). I know this takes time (even more in the case of "broken" framerates, which would require downloading the run for "perfect" accuracy [instead, all runs should be rounded to 60 fps times, to allow for ties]), especially if the run is not on youtube. Again, the solution at the bottom helps here. "Wrong" runs: Runs like the current 1-3 WR, that are simply in the wrong category (that run is a 0-5 run) or do not provide the necessary complete recording, for example because the runner accidentally uploaded the wrong run or chose the wrong category. These runs are the smallest problem of all mentioned, but still exist. Verifying time: This is a bit more nitpicky, because there are other games for which this is worse, but runs not being verified despite the mod being online, is annoying. Like in all the previous problems, the now following solution will reduce this time while increasing accuracy and taking this work off of @ClingingTomcat8, if he simply has no free time left to verify runs, especially when multiple runs are submitted in a day.
The solution, which is so simple while solving basically all current problems in less than two minutes (for @ClingingTomcat8): Make @TheHSbF6Leo (me, duh) and @CubZ (super)mod for the Lep's World games (Lep's World, Lep's World 2, Lep's World 3, Lep's World Z). Why? We both play at least one game of the series (pretty) actively. We both mod multiple games (3 games as a Super Mod in my case, two as a normal mod in @CubZ case). We both are online (nearly) every day and verify runs for our games on the same day if possible (that's what I do, but I believe @CubZ does so too). We have experience retiming runs (for me my 200 runs that I timed myself + runs in games I mod, should be similar for @CubZ). And the last point: We both are interested in playing ILs for the games (in my case, I already played and uploaded all currently available (on the leaderboard) ILs for this game, and @CubZ is playing the other games like LWZ more than I do and wanted to submit ILs, but can't, because there are simply none on the leaderboards. (Also I'd probably retime most current runs, I've gotten pretty fast with that now) That's it for this long forum post. Hopefully @ClingingTomcat8 considers that option. Thanks for reading!
Is using lag purposefully in runs allowed? Because I had my pc under some load when i practiced some levels and noticed you get a significant speed boost if playing with lag (the World 1 does this). Isn't that unfair to people who can't create their own lag?
Can somebody explain how the WR can take 700ms less from falling off the block after the last water to the end than me? Also he meets the bug so much later (for the bug, since it is farther down [for me it is still on the 2nd block , for him on the 1st]), wouldn't that mean he is slower? Also he accelerates when jumping (like, a lot) and I don't, which is even more confusing.
Can someone explain the timing to me? Its so vague and for example the 1-1 WR has an unreachable time (30fps recording, time .440, unreachable with 30 fps).
