Background
I started working on a best ending run once I had recorded my normal ending run. At first I wanted to do a no death, no warp run to differentiate it from the normal ending run and show off as much as possible of the game. However, I soon realized that all the levels are just like others. There is not much in terms of "level themes" (fire, ice etc) to make the game interesting to look at. The enemies are the same from level 1 until the last level. There are no new obstacles, no cool items to collect etc. The difficulty stays the same throughout the game. It looks like the developers have just more or less randomly scattered chests and obstacles and then rolled a die to decide which room should go where... I'm exaggerating a bit, but the design is just really uninspired imo. I then decided to just go for the fastest solution (with deaths and warps), even though a good portion of the run is then pretty much identical to the normal ending run.

There is more than meets the eye in Mighty Bomb Jack. In order to document these aspects of the game, I have a created strategy wiki with focus on speedrunning. I will therefore not repeat myself in these comments. The interested reader is asked to go here:
https://kb.speeddemosarchive.com/Mighty_bomb_jack_(nes)
For increased viewing pleasure, I recommend to at least check out the game map:
http://www.vgmaps.com/Atlas/NES/MightyBombJack-Pyramid.png
The path taken in this speedrun is: 1-1->Palace room 1->2->3->4->5->6->7-1->7-2->7-4->7-5->7-7->7-8->7-9->7-10->7-9->10-1->10->11->12-1->12-2->12-3->12-4->12-10->12-13->12-15->12-16->12-17->12-18->12-19->12-20->12-19->12-18->12-22->12-23->12-26->12-27->12-28->12-29->12-30->[death abuse]->12-1->12->13->14->15->16-1->[death abuse]->16-1->16-2->16->17-1->17-2->17-1->K->Q->P->B. Easy, right? :-)

Run comments
I won't go into too much detail here. Mostly point out a few mistakes. If there are faster solutions shown in the speedrun wiki, it's mainly because I wasn't consistent enough at them and decided to trade time for safety.

• 13 - Everything had gone surprisingly well up to this point. Unfortunately, I jumped slightly too early in the lower right corner and got an unfavorable spawn. Ideally, there will be two fireballs and two bats. Here I got one bird instead of a bat. That requires a small detour, which costs ~1 second. This room doesn't look hard when seeing it played like this, so I know you will have a hard time believing me saying that it's such a pain in the ... I therefore don't have too many regrets about the lost time.
• 14 - Small mistake at the beginning. Maybe the nerves kicking in (not many good runs get past palace room 13)? It is actually pretty difficult to pick up that bomb on the fly though. Maybe half a second lost.
• 17-1 (1st visit) - I missed the first double jump when destroying the blocks above the sphinx. It looks ugly, but is unfortunately something that happens at least once in most runs. Around half a second lost.
• K, Q, P and B - Several minor mistakes in the end gauntlet and also some cautious playing. I absolutely wanted to avoid bumping the head into any of the platforms when going for the exit (easily done). I think these rooms could be done around 2 seconds faster with more aggressive playing and less mistakes.

Final thoughts
Once I had the route pinned down and started to get a few finished runs, I set a goal time of 12m05s, with the hope of maybe even getting a 12m04s with some luck (I knew it could be even faster than that, but I didn't have the ambition to continue pushing down the time forever). I'm therefore a bit ambiguous about the 12m06s. I feel there is maybe one or two mistakes too many, but at the same time I don't feel like grinding out this game for one or two seconds. I hope it was still an enjoyable watch!

Disclaimer
I did this run on a Powerpak. In case it matters for future reference, I used a ROM with checksum afa6d274a86d33cfb519515061704af3.

SDA history
09-Sep-2013 - 0:06:57 by ktwo (http://www.archive.org/download/2014-02-20-SDA_Speed_Runs/)

Speedrun information
For information about speedrunning Mighty Bomb Jack and to get a better understanding of what's going on in this run, go to the guide in the SDA knowledge base (referred to as sdakb in my comments below):
https://kb.speeddemosarchive.com/Mighty_bomb_jack_(nes)

Background
Last time I played this game was more than 10 years ago, which resulted in a 6:57 run. In 2018, the Japanese runner 'msm_smtn' posted a 6:42 (when converted to SDA-timing). Almost every room had different solutions than what I used in my run. It's often surprisingly difficult in this game to tell which room solution is the faster just by watching. But given the time difference, I assumed there were many route improvements over my run. I made a mental note that I one day wanted to better understand the new routes and possibly even work on improving my pb.

In 2023, 'SpaceColonizer' submitted an any% TAS to tasvideos. Seeing the submission, I engaged to see if I could help with information about the game and reviewing the submission. Several iterations later, we now have for the first time a solid any% TAS and several route improvements found over the ones 'msm_smtn' used. The biggest one coming from 'SpaceColonizer', who "rediscovered" a shortcut that had been published and available on the net for a long time, but had simply been overlooked. Triggering the shortcut is very obscure and it's doubtful whether anyone actually found it on their own without the help of a strategy guide. Equipped with new route improvements, 'SpaceColonizer' and 'threecreepio' did real-time attempts and soon lowered 'msm_smtn's time.

With the any% TAS finally being done for this game, the rediscovery of the new shortcut (saving ~9s?) and several new room solutions having being found, I decided it was finally time for me to work on improving my pb... With easy time saves throughout the whole run, I quickly lowered my pb to 6:51 (if memory serves me right?) and 6:36. Neither recorded or worth remembering. The next pb was 6:31 in mid-Februari, which started to look like a speedrun, but still with several major mistakes. At this point I started to do attempts more regularly, which eventually resulted in a 6:30 at the end of February. Still with unacceptable mistakes. The 6:31 and 6:30 runs are linked to in the forum. I increased the sessions doing attempts even more, which resulted in two more 6:30 (both with major mistakes in the last rooms of 17). On top of that, I had two more attempts on pb pace that ended in the last rooms of 17 (which normally shouldn't pose any problems, except when on pb pace) and numerous attempts ending in 14-16 before I completed the submitted run.

Run comments
For the general game mechanics, please refer to the sdakb. The room solutions in this run is a major overhaul of the ones I used in my previous SDA-run. A couple of the room solutions (or tweaks of existing ones) were found by me, but most of the improvements were found by 'msm_smtn', 'SpaceColonizer', 'hisatoki' and 'threecreepio'.

While the shortcut will be explained in the sdakb, I will still say a few words about it here. There are two main points to open up the shortcut. The first is to find a hidden sphinx (an item used throughout the game to open locked doors) in 5-2 (room name from the game map, linked in the sdakb) to 5-5. 5-5 appears to be a dead end with the only open exit being back to 5-2. However, if you die in 5-5, then repeat the process and die a second time in 5-5 and then finally return a third time, a secret passage has opened at the top to "5-X", which then leads to room 11. Other than being convoluted, opening up the secret shortcut costs quite a bit of time. The alternative is to warp from palace room to palace room and get to 11 that way. The shortcut turns out to be ~9s faster though.

While the execution could be tighter throughout the run, I only made two noticeable mistakes. The first was in room 13, where I accidentally landed in one of the alcoves on the right side, which cost a few tenths of a second. The second mistake was canceling the jump too early in the King's room (the last room of the game) and accidentally landing on temple roof, instead of directly dropping down to the breakable block. This mistake cost about the same as the mistake in 13.

Final thoughts
I think this run is a fair representation of the how far the routing of this game has come since my previous SDA-run. This game is definitely not the most difficult run to complete runs in, but it's not easy to optimize the movement. A lot of the actions are of the type "direction changes". Many mistakes are doubly penalized, by both losing time in overshooting and then time to go back the same way. And there is generally speaking a lot of "cornering" type of movements, where squeezing as close as possible around an obstacle will save time.

While it was a bit discouraging to lose a fair number of attempts near the end, it did give me a good idea of what time I could expect for a completed run. The submitted run had the best pace of all the attempts reaching far into the game on pb pace, so I'm actually happy I didn't complete any of my previous runs. However, to give an idea of there still being a lot of improvement potential, 'threecreepio' has at the time of writing a pb (performed on emulator) that is almost 5s lower than my submitted run.

Credits
* 'SpaceColonizer' - Completing the any% TAS, finding route improvements (including the rediscovery of the shortcut to 11)
* 'threecreepio' - Route improvements and an extremely solid pb that I used as timing reference
* 'hisatoki' - I did not use some of the room solutions from the 2007 best ending TAS in my previous SDA-run, but they made their way into the new submission.
* 'msm_smtn' - Re-routed almost every room in his 2018 run. Several of those room solutions are still in use.