Stay with our rules, and the spread of information around the rejection of this run may help to encourage knowledge of better emulators to use. There are many outside of TASVideos who like to produce their own TASes, and they don't necessarily know the best emulators to use. To accept a continuance of an obsolete emulation, when it was not asked for in the time window given, means we are not making this push, and that we do not strictly adhere to advancement of emulation accuracy.Ĭommunity. I have seen the site as a whole pushing for emulator accuracy and console verification as an ideal. New rules are set to encourage what we can truly see when things are done on console. Whatever the precedents, this does not mean we must follow them. Do we accept this run, knowing it flies against the rules, or reject it, and continue to present a slower run, still on this sub-optimal emulator and grandfathered into its position after new emulators are available, as our best for who knows how many more months? We have a nice run on a sub-optimal emulator available here. Even if we have a team working on trying to copy the strats onto BizHawk, it's not something I'd expect to see in one week. A run like this takes a very long time to produce. Should we continue a precedent, allowing an aged standard to continue where today's standards wouldn't take it?Įffort. In this case, we have a prior run with a low standard. Mupen runs trying to obsolete BizHawk runs should be rejected in half a heartbeat. Mupen is below those standards, and I should expect that optimized TAS to go rejected in a heartbeat. This means we only have the standards the rules set. ![]() Suppose I somehow manage to produce a good enough syncing and extremely optimized Jet Force Gemini, on Mupen. This softens the impact, but as I understand it, the pressure to keep with the rules is still strong, and bending from it will give signals that we don't respect the rules ourselves. We're attempting to obsolete a Mupen run, which is itself already obsoleted by an RTA run, with another Mupen run. There is very strong pressure to ensure we're using the best emulator, and I'm almost completely certain obsoleting a BizHawk run with a Mupen run will never happen. ![]() In emulation quality, the two are similar. The run this TAS attempts to obsolete was done on Mupen. Hence, "if" accepted, not "when" accepted. If accepted, there's little doubt it's in Moons, possibly Stars.Īcceptance itself is being contested on the grounds of which emulator is used, however. Enjoyable to watch, and definitely has good feedback in terms of entertainment. ![]() In terms of what the run aims to do, it does it well. This new method of getting the Mirror Shield is faster, and also saves a lot of explosives that can be used later in the run. After the Hookshot Jump, I pull out a bomb and do an A-Slide to reach the seam and hookshot the Silver Gauntlets chest and finish with a SuperSlide to reach the Mirror Shield chest. After the text dialog is closed, or if the camera somehow moves, Link is propelled at a height depending on how high the hookshot was targeting. I then use the enemies again to reach the flag very fast, then I hookshot the flag at a spot where I look at the token right before obtaining it, so it takes the token. The Skulltula is then killed, and its token is collected in mid-air with a sidehop during which I pressed the fish bottle (can be any cutscene item) to delay the token obtaining as long as I don't look at the token. Here comes a very funny and interesting trick that is the Skulltula Hookshot Jump: I first wait a little bit because night is not yet reached, but extremely close (the waitings before were worth).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |