Table of contentsGame Objectives
Introduction
Mechanics and Routing
Level-by-Level Comparison Table
Other Notes
Suggested Screenshot
Game Objectives
Beats the game as fast as possible
1 player
Uses a game restart sequence
Genre: Puzzle
Introduction
“Mario’s Super Picross” is a nonogram puzzle-solving game developed by JUPITER and published by Nintendo for the Super Famicom on the 14th of September, 1995. Originally only released in Japan due to the poor international sales of its predecessor “Mario’s Picross” earlier that year, it would eventually be released in PAL regions on the Wii Virtual Console in 2007, and then in North America through Nintendo Classics in 2020.
This game first came to my attention in March last year, where I decided to give it a try on my Switch and quickly got hooked, completing all of the puzzles in the span of about a month. A while after that, my friend vichisuki suggested that I could potentially try TASing the game, and I decided to give it a shot, initially starting work on a 2-player TAS in August 2024. I quickly learnt that optimisation was much more complex than I had initially assumed, causing progress to slow down and eventually stall around January while I focused on other projects.
In April, UndercookedRice submitted a 1-player all puzzles TAS of Super Picross to the site, which reignited my interest in TASing the game. After it was published and I had some more free time on my hands, I noticed that many of the optimisation techniques I had previously used working on the 2-player TAS could be applied to save time. I subsequently started creating the 1-player any% TAS you see now, working on and off over the course of about 6 months before finishing up a few weeks ago.
Mechanics and Routing
There are a few quirks of how player input is handled in this game that make optimisation less trivial than it initially seems. Both the A and Y buttons can be used to mark squares, and their input is handled independently from one another. As a result, alternating between A and Y allows the player to chisel up to 60 times a second instead of 30. Consequently, the D-Pad becomes the main bottleneck, as we’re unable to move in the same cardinal direction two frames in a row. Using zigzagging movement patterns wherever possible is crucial for saving time and minimising wasted frames, and diagonal movement becomes more risky due to using two directions at a time.
To make planning my movement between squares easier, I opted to use graph paper for my routing, using a pen to draw the solution and a pencil to draw my planned route. This helped me to identify mistakes and efficiency problems and adjust things accordingly before I even started inputting anything into TAStudio, and it also helped me better visualise ways to tackle some of the more complex puzzles and break them down into smaller sections.
Additionally, the hammers that appear when you mark squares follow animation cycles (8 frames for Player 1 and 7 frames for Player 2), and those need to finish before the game can start the end of puzzle animation. This particular mechanic was first discovered by mohoc when he was giving me feedback on my first 2-player TAS WIP back in October last year. I later discovered that it’s possible to interrupt and restart the hammer animation by using B or X to cross out a square, which is useful for ensuring they finish as soon as possible after a puzzle is completed. In a lot of cases I was able to set things up such that I didn’t have to waste any frames getting the hammers to finish on time, though this wasn’t always possible.
Level-by-Level Comparison Table
Level 1Level 2Level 3Level 4Level 5Level 6Level 7Level 8Level 9Level 10SpecialMinimise UndercookedRiceInputEvelutionFrames saved1-A8267151-B8167141-C8669171-D8769181-E167123441-F171114571-G149104451-H162108541-I245158871-J174128461-K142112301-L12910227 UndercookedRiceInputEvelutionFrames saved2-A150127232-B153110432-C150112382-D140103372-E321222992-F344284602-G336241952-H3052041012-I3932761172-J294222722-K297220772-L30426737 UndercookedRiceInputEvelutionFrames saved3-A320256643-B226186403-C259202573-D256212443-E277197803-F287226613-G208142663-H259169903-I288227613-J292196963-K277204733-L27624036 UndercookedRiceInputEvelutionFrames saved4-A176134424-B282208744-C227162654-D255218374-E198171274-F258241174-G232176564-H259213464-I178138404-J266212544-K322244784-L299199100 UndercookedRiceInputEvelutionFrames saved5-A329245845-B200162385-C201167345-D221166555-E280220605-F307250575-G210169415-H250174765-I268225435-J236180565-K237174635-L26719275 UndercookedRiceInputEvelutionFrames saved6-A230184466-B252203496-C245185606-D232171616-E246185616-F229171586-G212158546-H250190606-I324230946-J195144516-K287218696-L26519570 UndercookedRiceInputEvelutionFrames saved7-A225180457-B250188627-C210170407-D234184507-E280212687-F258221377-G264208567-H201152497-I214183317-J217167507-K250203477-L21718037 UndercookedRiceInputEvelutionFrames saved8-A547479688-B5313801518-C4503281228-D3552291268-E350271798-F5003651358-G4662901688-H4253011248-I453366878-J411329828-K335247888-L390275115 UndercookedRiceInputEvelutionFrames saved9-A328297319-B3982621369-C3512471049-D331232999-E4363271099-F3582471119-G396307899-H4463171299-I4873821059-J4823501329-K4102841269-L478330148 UndercookedRiceInputEvelutionFrames saved10-A39928711210-B51234017210-C38827611210-D37626311310-E2862285810-F3752819410-G40328611710-H4113179410-I41026214810-J43729813910-K46034111910-L490338152 UndercookedRiceInputEvelutionFrames savedSP-A532370162SP-B540378162SP-C42934485SP-D425309116SP-E490344146SP-F642448194SP-G567450117SP-H579425154SP-I587425162SP-J47138190SP-K509367142SP-L525398127The timing used above uses the selection of “No” to the hint roulette as the starting frame, and the puzzle timer disappearing as the ending frame. On top of the puzzle-by-puzzle improvements, I also reset the game between completing each level, as this saved time over simply watching the congratulatory cutscenes from Mario play out. This comes out to about two and a half minutes saved in the puzzles themselves, and about one and a half minutes saved in menuing.
Other Notes
All of my routing was done by hand, and so it’s possible that some puzzles could be further improved by using a custom solving program or brute-force to find the optimal solutions instead. However, I didn’t have the necessary programming abilities or experience to create such a program myself, and learning how to do so might well have taken me as long as it took to make this TAS, if not longer, so I opted to solve them manually here.
I really enjoyed working on this project, and I’d like to do some more Picross TASing in the future, either in the form of a 1-player all puzzles improvement or a 2-player any% TAS. For now though, I’m probably going to take a break and focus on some other projects for a while.
Suggested Screenshot

(frame 96089)
nymx: Claiming for judging.

Ver todos los episodios