This thread is intended to demonstrate how MININIM's replays aid in sharing walkthroughs and mechanically validating solutions for entire level sets. All videos made available here were recorded from replay playbacks and are grouped in a dedicated YouTube playlist at my channel. The replay chain provided here is distributed alongside the latest MININIM release in data/replays directory. For a user level description of MININIM's replay feature see its announcement. For a technical perspective of its design decisions see this post.

A MININIM replay file corresponds to one and only one level and possibly presents a solution thereof. A replay chain is a sequence of replays sorted by increasing level order, which possibly present a solution to an entire level set. In this case we say the replay chain is complete and valid. MININIM can be used to mechanically verify the validity of replay chains. When replays are specified in the command line (as opposed to loading them in-game using F7), the error status returned by MININIM indicates the validness of the provided replay chain.

Notice that a null value for --time-frequency disables time frequency constraint, allowing MININIM to use all the CPU power available for replaying as fast as possible. Probably, invoking MININIM like this in your own computer will yield a much faster and smoother playback than what's shown in the videos below, for two reasons:

Capturing video consumes a significant slice of CPU time, as does uploading to YouTube in the background .

My video capturing software is setup for 12 frames per second (to match the default MININIM time frequency).

Naturally, more demanding rendering settings (like high multi-room resolutions) slow down replays considerably for sufficiently high time frequencies. Providing --rendering=none, which disables video and audio rendering altogether, is then ideal for batch processing of replays.

Wildcards are useful for specifying entire replay chains at once in command line invocation. In GNU/Linux the job of expanding them are performed by the shell. In Windows, MININIM has to take care of it using C's glob function. Therefore, there might be differences on what is accepted by each port. For instance, data/replays/{01..14}.mrp has to be replaced by the ad-hoc equivalent data/replays/??.mrp under Windows (this latter being usable on both platforms).

This replay chain has been verified to be valid on both GNU/Linux 64-bit and Windows XP 32-bit, confirming the architecturally neutral replay format design and MININIM's consistency in replay reproducibility.