Emulator Used: BizHawk 2.3.0
Frames: 34181
Re-record count: 3600
Time:9:22.29
Minnesota Fats: Pool Legend is a pocket billiards video game for the Sega Genesis and Sega Saturn, featuring famed billiards player Rudolf "Minnesota Fats" Wanderone. It was released as a sequel to Data East's earlier success, Side Pocket.
The Saturn version of the game largely plays the same as the Genesis version, but includes a training mode, a short documentary on Minnesota Fats, and a completely different plot in the story mode. In the Genesis version, the player takes the role of an unnamed rookie pool player seeking to challenge Minnesota Fats, and cutscenes are computer-animation. In the Saturn version, the player takes the role of Minnesota Fats himself, in his quest to challenge fictional pool hustlers from around the United States; live-action, full-motion videos (FMVs) are used for the cutscenes.
In Japan, the title Side Pocket 2 is only used in the Saturn version, whereas the Genesis version retains the Minnesota Fats: Pool Legend title.
Comments: Here's my second TAS of this game called "Minnesota Fats Pool Legend" on the Genesis. I love this game since I was a child, It has a good music, memorable pattern, Tournament mode, trick shot mode, and many more!!!
(Story Mode selected) next is trick game mode
I can't find any speedrun of this game, so I decided to TAS it and upload it here
Easy to TAS with, is 9-ball mode. The hard one is 8-ball which it slows the time, again.
Please don't give negative feedbacks or I'm not doin any TAS game that hasn't TASsed yet.
I apologize to my first speedrun.
Please give advice, im so depressed. im sorry
Samsara:
There are numerous issues with the optimization present throughout the run, ranging from mashed input to just suboptimal execution of strategies. I gave some advice in the thread that you already took to heart, but I'd like to repeat it here and expound upon it a little bit.
First, you want to make absolutely sure that you're not mashing buttons randomly at any point. You want to always find the first possible frame to do whatever it is you need to do. Even auto-firing a button can lose frames, so just keep trying things earlier and earlier until you can't possibly do it any earlier. This is time-consuming, but that's kind of the point of TASing: You have an infinite amount of time to optimize your submission, you should be using that infinite time to the best of your capability. Even if you only have 30 minutes a day to work on a run, the beauty of TASing is that you can just save your progress at the end of that 30 minutes and load it back up the next day, and you will eventually still make a proper, finished TAS if you keep it up. I often tell people that the greatest skill for a TASer to have is simply patience. I've spent upwards of a year on a single run, others have spent several years working on a single run. Patience is a blessing. Use it wisely.
Second, you picked a complicated game to TAS. I respect that immensely, but I'd also advise against it in this particular case. Pool's a really tricky thing to optimize, it either requires knowledge of the game engine or an immense amount of patience to brute force every possible option to see not only if the strategies used are the best possible strategies, but also if they're being performed as efficiently as possible. While it's unlikely that I would actually reject a run for not using perfect strategies, it should be clear that different strategies were tested in the first place, and I don't exactly feel that coming from this run. 9-ball is likely fine (though I imagine the same thing can happen from a faster point on the board), 8-ball just has too many possible variants to be confident that there were multiple attempts at finding the best solution.
I highly recommend openly engaging with the community instead of sticking to private messages as well. We're here to help, even if sometimes it comes off a little aggressive (and I'm personally sorry if anything I said came off that way). We don't mean to offend or be hostile or try to drive people away, we're just passionate about TASing and it occasionally doesn't come out quite right.
Rejecting for suboptimality.
Samsara: I've restored the original content of the submission after the author attempted to nuke it. Don't do this.
