Currently, it’s almost impossible see a comic book film in theaters without having to see some sort of a tease stuffed somewhere during or after the credits. Aquaman starring Jason Momo has finally arrived in theaters and it comes with a post-credits scene too. And believe us when we say, you’ll want to stick around for this one.

While the main villain of Aquaman was Orm, Aquaman’s comic book nemesis Black Manta also had a significant role in the film. After Aquaman left Manta’s father to die, Manta vowed to kill him, and he spent all the time in the film trying to do just that. However, in their final encounter, Manta was sent off a cliff and to what seemed like his death.

However, the post-credits scene revealed that he isn’t dead after all. The character is seen floating on a raft, with his armour and helmet broken. But his problems are soon solved when he’s discovered by a character named Stephen Shin.

Dr. Shin is seen in one short scene earlier in the film, and is also obsessed with Atlantis. When Black Manta comes back to his senses, he finds Shin working on his mask, impressed with its (Atlantean) technology. After seeing the weapon’s power, Shin agreed to work with Black Manta, who is still hell-bent on getting his revenge on Aquaman. With someone like Shin working with Manta, it’s safe to assume that he will be a danger threat again.

This scene teases the Aquaman sequel. After Orm was defeated by Arthur at the end of the film, its likely that he will have to deal with attacks from the man who hates him most, powered by the one human who knows more about Atlantis than any other. They will be a thorn in the king’s side, to say the least.

Facebook comments:

Leave a Reply

Adcodes and Instructions provided for: ============================================== ============================================== ======================================== SID 15564 ======================================== PLACE THIS CODE BEFORE THE TAG Edge Ad Code: ======================================== ======================================== ***EDGE Trafficking Instructions:*** ======================================== EDGE ad code should be placed directly on the site within the body at the end of the page. The default EDGE configuration is described below. If you have requested a custom configuration, please disregard default settings below. EDGE can be trafficked through ad servers via javascript tags, 1x1 javascript pixel, or DFP/GPT synchronous tag. In DFP, make sure that SafeFrame is disabled (it is automatically enabled by default), otherwise the tags will not work properly. For DFP/GPT, see this link to "Traffic and serve out-of-page creatives": ======================================== ======================================== ***EDGE Default Configuration:*** ======================================== SLIDER - Rails w/ Content Detect and Footer w/ Ad Detect: - Serve rail placements (160x600, 300x250 and 300x600) for Desktop when open space is available. All sizes are located at the bottom of the window by default. - When rail space is not available, serve 728x90 or 970x90 footer. With Ad Detect enabled for desktop footers, a 728x90 or 970x90 will not be served when it covers a standard IAB format (728x90, 300x250, 160x600, and/or 300x600). ======================================== ======================================== ***EDGE Default Settings:*** ======================================== - Device Targeting: Desktop, Tablet, and Mobile Phone - 100/24 Frequency cap - Minimum Time between EDGE sliders: 3 seconds is the minimum time allowed; may be increased ========================================