Reading all this has brought me tons more joy than watching the old run ever did. And the run is cool as hell. Good work, dudes.

Now you need to figure out how to beat the game without even starting it :)

This brings up an "interesting" problem... What is your completion time, if you never start the game? Is it infinite frames or 0 frames or what? Like, when the other guys shout "Last guy on the hill is a fag!" and one of the guys never runs to the hill, is he a fag or not? (When I was a child, the guys never understood this problem and told me I was a fag anyway.)

This post is so nice, I'd like to see it twice. asside: frames/time(s)=60 (you know, approximately) If your final time was infinite frames, then we'd end up with 1=60 assuming the final time in seconds is also infinite—and I wouldn't want to do that to the universe!

9.8 seconds!? I bet that will be the final time

I'm positive that's because the game keeps placing sceptre on wrong positions (where there's a building on the map), thus calling RNG many times after checking its position.

Then that means the fade time is not directly related to timing of the final luck-manipulation input, so it is indeed possible that 9-frame or 10-frame iterations produce faster result! So, gia, would you like to organize the task so that you provide us with bots set to work a predefined segment of 100 000 movies? People could then download one of your differently configured bots and just run the bot and report the results. People would not need to configure anything, so it would stay organized as long as people inform what segment they downloaded.

Download the bot at TAS laboratory, it has support for that. First guy run the generator, copies generator.save and sends to second guy. He generates second batch, and sends .save to third, etc. Each run creates +-25 000 movies and will tell how many combinations so far it has created, so you can use that number to config the bot of the next guy (as they will start with the next movie). So if you want batches of 100k just run 4 times and send the save to second guy, etc. To know how many segments there are (for me to offer downloads for each) I would have to either calculate or generate the movies. Both take time, and I bet 10 frames will be big enough so as to offering downloads for 100k segments will end up with a lot of segments, i prefer you copy/paste the save file and config the single line on the bot config. (hell as you go you could package the folder with the save and bot config in place so they just run the thing).

I generated all the 9-frame movies. It was only slightly over 400 000 files. Can that be correct? I could let the bot run all those easily.

hmm, oh crap, you used the one at tas laboratory right? that one only adds idle frames :) sigh i'll make a version for you...

Nope, I used the old one. Edit: Yes, these files that I generated have left/right buttons too.

Volunteering my cpu if needed :)

Ah, then its good, but this one may help with 10 frames, after running it just post the *.save so another can run from where you left. http://rapidshare.com/files/113086362/tas-movie-editor.rar.html

Thanks again. Well, I'll just run these 9-frame movies, even though the 400 000 seems a bit low number for them. I have lots of disk space still available, so that is not the problem. Is there a limit to how many files can be in the same folder? Well, if you, alden, want to try it out, just begin with the 10-frame configuration. Generate as many files as you like and then pass the generator.save file to the next person, whoever wants to pick it up. Edit: Oh, feel free to ask, if you have any questions. It took me some time to understand this tool too. :) Edit-2: If you have sound enabled on the playback bot, it should sound something like this: www.freewebs.com/aqfaq/giabotsound.mp3

gia, I would appreciate your help. I only have 2 to 3 frames that need manipulating (different game), but they access the RNG a god awful amount of times. Is there any way you could write your bot to attempt every possible input for those few frames, then check memory values? That means up, up down, up down left, up left, up down left right, up right.... i.e., all 256 different button combinations...

yawn, there's the source, if you can't use it, finish that code and i c/p into the source you say something like not adding any extra frames just using the ones already available and you got their numbers right? just complete this: switch( j ) { case 0: baseinput[startpointf4 + i].Controller[0] = ""; //idle break; case 1: baseinput[startpointf4 + i].Controller[0] = "^"; //up break; case 2: baseinput[startpointf4 + i].Controller[0] = "Z"; //select, this is the only button different than usual tas-movie-editor syntax break; etc } change "case" numbers and what's between ""s

yawn, there's the source, if you can't use it, finish that code and i c/p into the source you say something like not adding any extra frames just using the ones already available and you got their numbers right? change "case" numbers and what's between ""s

I sent you the completed code, and hopefully this will benefit more people than just me. Essentially, I have the first 6 seconds of input. The bot needs to do 3 frames of input, and then frame advance once, and check 3-5 memory values.

The bot has finished running the 9-frame luck-manipulation patterns. There were 401 328 files to run. (I'm not sure if that was all of the 9-frame movies, but as mentioned earlier, that is all the generator generated for me.) It took about 24 hours to run all those movies with frame skip set to 50. There are 17,8 MB of .txt logs, if somebody wants to analyze them. :) Here are the not-so-exciting results: 83 movies got coordinates {12, 4}. I believe this coordinate might be a good shot for a console speedrun, since it is seen "often". (Oh, but that might not be the case, when more frames are wasted in the beginning.) Coordinates {10, 4} were achieved once. It was movie 335068. Rather strange how there was only one of these coordinates so far, of all the 1-9 frame luck-manipulation patterns. All these 84 movies (with Y-coordinate: 4) require 12 frames of walking and complete the game around 607 frames at best. That is not a good time anymore. Two movies managed to get 597 frames completion time with coordinates {11, 5}. These two movies were 238455.gmv and 323348.gmv. There were four other movies that got coordinates {11, 5}, but those four had 1 frame more fade time, thus achieving 598 completion time. That is not a promising result. With inductive reasoning, I would believe that some of the 10-frame movies will complete the game in 598 frames and some in 599 frames, but I can't see the possibility for 595 there, maybe not even 596. But who knows before the 10-frame movies are tested... To achieve 595 frames, some of the 10-frame combinations must achieve 3 frames less fade time than the winning 8-frame combination got. Maybe it's not possible. An awfully lot of the movies get 0,0,0 and are not reported as FAILED. I suppose all of those are the movies that press Start immediately after Left or Right and the game fails to begin. I would strongly recommend reducing the tested patterns so that there's always an idle frame before the start button. But ofcourse, as you (gia) mentioned, it is not a bad thing to run extra movies. There's just so many of them... I would like to let other people run the bot for now, if they want to. I've already run more than 520 000 movies. It was fun and I learned new things. I'll consider running bots for other games in the future, if opportunities arise. Oh well, if the ball gets rolling with the 10-frame movies here, then I might run some of those just for fun. In conclusion, the project has been a huge success already! Congratulations to gia for a great TAS achievement! Also, many thanks to people who joined the happy discussion and offered help. I would not hurry with the submission-package yet. I also still don't care who is the "author" of the movie, but I bet gia did the hardest work to achieve it. P.S. The 401 328 movie files take some disk space, but I'll keep them available a few months, if somebody wants to see a specific file. Same goes for the bot logs.

I would not hurry with the submission-package yet.

Good idea. I think that AKA can improve the movie by over 600 frames.

I would not hurry with the submission-package yet.

Good idea. I think that AKA can improve the movie by over 600 frames.

You, sir, just made my day. Thank you.

The bot has finished running the 9-frame luck-manipulation patterns. There were 401 328 files to run. (I'm not sure if that was all of the 9-frame movies, but as mentioned earlier, that is all the generator generated for me.) It took about 24 hours to run all those movies with frame skip set to 50.

You only set frame skip to 50?!?! Man. How slow is your computer? I'm running it at 5000. It's not over 9000, but it's still fast. I'm running about 60,000 418 frame movies in a half hour.

I studied the fading time a bit more and guess what! After the final Start button (before the game begins): The old published movie has 174 frames of screen fade time. By a lucky coincidence, the new best movie has only 173-frame screen fade! The hypothetical optimal movie, which starts the game as fast as possible, has 174-frame screen fade! In order to achieve 173-frame fading time, the optimal movie needs to idle 1 frame, negating the gain. :D So, you could say that in a sense our new movie plays the screen fading part faster than optimally. LOL? But not quite... If I'm right, the winning 10-frame combination would need 171-frame fading time. By testing manually, I know that this kind of fade time is possible. So, ok, I'm willing to run some more movies, because I know for sure that there is still a (very small) chance for an improvement. The bot can run with the same old configuration. I will pick up the .save file at some point, if it gets tossed around here. Thanks.

You only set frame skip to 50?!?! Man. How slow is your computer?

I used frame skip 4000 first, but I wanted to do other stuff with the computer too, so I changed it to 50 at some point. If I had let the computer run without touching it, it would have worked much faster.

So, whatever happened to a new submission of the improvement?

I generated all the 10-frame luck-manipulation files recently. It is 1.3 million files. I'll run those files someday soon and if no improvement is found, we will likely submit the 596-frame movie.

Definately waiting for an improvement of this. Once you have that all figured out, will it actually be the fastest it can be? I guess there's still no way to tell.

Once you have that all figured out, will it actually be the fastest it can be? I guess there's still no way to tell.

Your guess is right, there is no way to tell it for sure. In any case, it is definitely VERY close to perfect. I finished running the bot and there was no further success. So, 596 frames is likely the new record. I have sent a PM to gia about submitting the movie, but he has not received it yet.

YouTube encode: Link to video https://mega.nz/file/GwsyVAbL#9K-RsAY1ti-AIUGAY0EGc_2CRSZ4HN8g-d4Q7pEj1vw