Marble Blast Levels: The Matrix Maze Series
Contents:
Overview
History and the revision model
Revision 1
Revision 2
Revision 3
Individual level notes
The scrolling “credits”
Bloopers
Figures
Concluding thoughts
Overview:
Ever since I made a YouTube account (April 2009), I have made a major Marble Blast compilation every summer. To recap, my major compilations in previous years were as follows:
2009: Marble Blast: No Gems,
2010: Marble Blast Levels X,
2011: No Gems: The Second Compilation,
2012: Marble Blast Levels 20.
This year, my major compilation is on the Matrix Maze series by CyberFox.
History and the revision model:
I probably first saw the Matrix Maze levels in the CLA some forgotten time ago, but until last December I never thought much about them and had never seriously tried them (I remember getting 2 minutes and stuff on them in the past). At around the December timeframe I was thinking about what sorts of videos I would release the following summer, and a compilation on the Matrix Maze levels seemed a nice one to have. I
chose the Matrix Maze series because of 3 reasons:
C1. It consists of a number of levels under a unifying theme (I would have preferred some more variation in the levels though),
C2. I could work on pathfinding skills because the levels have numerous possible paths,
C3. They were just complex enough to avoid being dull while simple enough so I would be able to have precision runs without too much frustration.
So, I had MBL: C25, the Matrix Maze series, and a 3rd video whose theme I will not yet disclose planned for the summer of 2013. From the start, I decided to not watch any videos of anyone else’s runs of any of the Matrix Maze levels, so that I could find paths by myself. (I do not recall if I watched any back in 2008-2009 when I watched many Marble Blast videos. I know I haven’t watched any for at least the past few years.) I asked calebsoong (a.k.a. eNetro, SPIKErock) for all the times on Imperial’s Matrix Maze series video from 2008 so I could be sure to beat all those times. I also searched YouTube for more videos, and all of them had the times in the title, which made it easier for me. Since most if not all of the existing videos are from 2008 I think, I also knew that I should demonstrate considerably lower times than what was shown in the videos, and I think I have done so for all the levels except for MM 02.
I quickly decided on a revision model while doing runs for the video. The revision model works as follows. I spend a certain timeframe making .recs for all the levels in the Matrix Maze series. After all 13 levels are .rec’d, the outcome is known as revision 1. Then I redo all 13 levels for better times, the outcome is known as revision 2. I continue to do so until I reach a natural number X where I consider myself done with working on .recs for the compilation. In this case, X = 3. The
reasons for a revision model were threefold:
R1. Marble Blast was no longer the only game I played regularly, I got to know more games, so I did not usually feel like dedicating 2-3 or more hours in one day to one level.
R2. I may not find a good path the first time I play a level, and if I get off the level, have it in the back of my mind for some time, and go back on later, I have more chances to find new paths. The revision model works well with reasons 1 and 2 since I can think of and introduce new paths and tweaks regularly and most of the levels are of similar difficulty so I wouldn't have one MM level top out at revision 2 and another level go to revision 5.
R3. I seem to improve my skills better in a level if I work on it over a period of time instead of all at once. A step-by-step approach can let me spend more time on a level in total, and also helps limit how frustrated I get during a session when I make too many mistakes and/or don’t perform as well as I would like.
From one level revision to another, I was constantly
surprised at how often at least one of these two phenomena happened, even with no new path:
S1. I beat my time on the previous revision easily, given the amount of time I spent on the previous revision,
S2. I beat my time on the previous revision by much more than I thought would be realistic for me, given the amount of time I spent on the previous revision.
I chose to do
three revisions for 2 reasons:
T1. 3 revisions would give me ample opportunities to introduce new paths and tweaks as necessary,
T2. If I use too many revisions, I may get to a point where I have a run in revision X that is too difficult to beat for revision X + 1 and no new path or tweak is in sight, and I wanted to avoid such situations.
Due to R2, I didn’t encounter a situation where I “needed” more than 3 revisions or no more than 2 revisions in a run. However, the total amount of time I spent on each level did vary significantly from level to level, but in the end, they all worked within the 3-revision system. I did consider a modification allowing 4 revisions for some levels, though.
I may do a revision system for future MBL: Compilation videos, but to save time, only two revisions on average per level instead of 3, and I'll only create and upload the final revision video. The revision system in this case will be more of a way to spread out my playtimes than to necessarily spend more time per level than before.
Revision 1: —
The runs were made during this timeframe: December 2012 to March 2013.
In this revision, many of my runs were done so I would have some sort of decent run that I could build upon in the future. Many runs did not beat Imperial’s times (most likely due to slower paths), but that’s okay since I had two revisions left. I also got a good feel for the levels so I knew where to focus my efforts in the second revision. I noticed that the MM Platinum levels seemed hard so I put those off until March (see Figure 1), when over half of the MM (Gold and Platinum) levels were done before 2013 started.
Revision 2: —
The runs were made during this timeframe: May 2013 to July 2013.
New paths: MM 01, MM 02, MM 07, MM 09.
Some of the runs were done in May because they seemed “natural” to do and I had faced little difficulties in revision 1. Two exceptions were MM 10, since I did not do the “obvious” edge hit at the end in revision 1, and MM P03, since the revision 1 run was not particularly well done and also much higher (42.35) than the time I saw on YouTube (34.86, WhiteBoomerang). I managed to get a lower time (34.31) but I still knew from watching the run that there would be more to do.
Revision 3: —
The runs were made during this timeframe: July 2013 to August 2013.
New paths: MM 02, MM 03, MM 06.
As you can see in Figure 2 below, I did not spend as much time on revision 2 as I did on revision 1, since I figured that I could just make up the difference in revision 3. That didn’t turn out to be a good move, since I spent more time on revision 3 than on both previous revisions combined, since I wouldn’t have a “revision 4” to fall back onto later if I had a less-than-satisfactory performance on a revision 3 run. My thought in T1 was partially subverted as it now seemed like I had not enough opportunities to work on some levels, but for most if not all levels, the path and most tweaks were finalized after at most 30 minutes to 1 hour into the session, and I just had to spend extra time if necessary trying to get a better time.
I also pushed some levels back until near the end so that I could make use of the extra experience I would get on the earlier levels. A notable example is MM P03, which is tied for 4th earliest in the revision 2 date, but ended up being the last run recorded for revision 3 [Figure 1]. If I had gone for 4 revisions for at least some levels, then MM P03 would have been one of them, and the 2 hours and 43 minutes I spent on it for revision 3 would have been broken up into two sessions [Figure 2].
Individual level notes:
Matrix Maze 01: I did the revision 2 of this run early [Figure 1] since I didn’t like how my revision 1 run of the very first level in the Matrix Maze series was slower than Imperial’s run—I was clearly starting out on the wrong foot!
Matrix Maze 02: This is the only run in revision 2 that doesn’t beat an existing video time (that I know of), in this case, Imperial’s. I had some trouble finding good paths for this level, and I doubt the path I used in revision 3 is optimal.
Matrix Maze 03: I got very annoyed especially during the revision 3 recording because after the 18th gem, I would constantly fall off the platform.
Matrix Maze 04: This level caused me some trouble in revisions 1 and 2, but I got past that and finished the revision 3 run with a nice ending.
Matrix Maze 05: I thought I wouldn’t be able to beat my 29.80 in revision 2, or if I did, beat it by 0.05-0.1 second or so, since I had high 30’s during my practice runs for revision 2 and the 29.80 seemed very well done.
Matrix Maze 06: I know the revision 3 path is 2.5 seconds faster than the revision 2 path, but I can’t ignore the edge hit in the revision 2 path!
Matrix Maze 07: I got a surprise 24.85 after all my runs for revision 2 was over while I wasn’t recording. I spent nearly two hours afterwards to get just 0.02 better on .rec. I got so many 24.95-24.99’s it wasn’t even funny.
Matrix Maze 08: The ending of this run has a strange history. I first tried to get the last gem without bouncing on the platform beforehand, but I couldn’t, hence the bounce in the revision 1 run. Then I tried again during revision 2 and I managed to get it to work using a long run-up before leaving the platform with the second-to-last (13th) gem. It was a bit annoying since half the time I still wouldn’t make it to the last gem. Later, I realized that the reason I couldn’t get the last gem without bouncing was that I was leaving the second-to-last gem platform too close to the “wedge” and the marble was hitting the grey top of the wedge, pushing it down and making it land on the last gem platform too early. So, for revision 3, I exited the second-to-last gem platform slightly away from the wedge, and then I can make it to the last gem with even a relatively short runup.
Also, my original path for this level was getting the gems in basically the opposite order to this path. That path didn’t seem to go below 38.xx.
Matrix Maze 09: One of my favorite edge hits. I didn’t know if the edge hit would really work until I tried the level for revision 3.
Matrix Maze 10: Many edge hits. The one after the 8th gem might seem like just another no-skill edge hit, but it is surprisingly easy to hit it too fast, which results in the marble having too much air time or even missing the 9th gem entirely.
Matrix Maze P01: Sonic claimed that he spent 3 hours finding a good path and 15 minutes getting his 18.34. I spent much less than 3 hours finding this path, but much more than 15 minutes to get even my revision 1 16.52 [Figure 2]. The revision 3 run took less time than I thought given how much I struggled on revision 2, see R3, S1, and S2. 15.46 is also my best final TM catch on that level.
Matrix Maze P02: I honestly thought the combined edge/wall hit (it counts as 1 edge hit and 1 wall hit in the credits) wouldn’t work until revision 3. Even then, my previous idea of just a wall hit wouldn’t and didn’t work, and the marble has to rebound at the right angle for it to even get to the next part of the path.
Matrix Maze P03: I spent more time on this level than on any other level in the Matrix Maze series, and for good reason. This level seemed overwhelming when I first tried to even find all 10 gems and some path that would let me get all of them. It seems natural that this level saw the greatest improvements in final times (and perhaps paths too…) from revision 1 to revision 3. The edge hit after the 4th gem was surprisingly hard to do for me. A successful edge hit gives one of two outcomes:
1. The marble will bounce on the small platform right before the slope with the 5th gem, then one jumps to get the 5th gem.
2. The marble will go straight to the slope and the 5th gem.
#2 is obviously faster but also harder to do.
The scrolling “credits”:
I made the scrolling credits at the end of each revision video as a homage to the Left 4 Dead series of video games which has similar credits (and of course, I use the same soundtrack). Note: I count hits on a steep slope as wall hits, they are functionally very similar.
Bloopers: —
Here, you will see (besides the usual kinds of bloopers) two kinds of bloopers I haven't really shown before.
1. Rarely (it seems to be more common when I'm at a critical part of a run), my Marble Blast screen will skip for a fraction of a second without any warning before going back to normal gameplay. That split second is enough to screw up many runs, including the ones you see here.
2. If the marble sticks to a wall, it is not possible to make it unstick or control its left-right movement—one will just have to wait until it hits another part of the level or it exits from a boundary of the wall.
Also, the last MM P03 blooper was the last run I recorded on .rec. It was after my revision 3 run (recall that MM P03 was the last level done for revision 3), since I wanted a sub-30. Some time after the revision 3 run and before this blooper, I told myself that I would finish the Matrix Maze Series after I finished the next run with a successful edge hit, no matter what happens after the edge hit. It turned out to be this run.
Figures:
Figure 1:
Figure 2:
Note: These times are from the .rec timestamps, which means they
do not include a lot of the time spent pathfinding, “trying” the level, or thinking up a new path or tweak before I get into the .rec’ing for a session. That’s partly why the times are somewhat less than I thought they would be (I was expecting closer to 40 hours for the total time for all 3 revisions), another reason is that I probably overestimate the time I spend on a level if I don’t look at a clock or something.
Figure 3:
Concluding thoughts:
I kinda wish I had spent more time pathfinding.
After my final blooper for the Matrix Maze compilation, I wrote on the .rec description,
“Well, that's the end of the Matrix Maze Compilation. I hope you'll enjoy on YouTube.”