Deadpool is really difficult to kill, thanks to his regenerating abilities. This is something that comes handy when you are a mercenary. However, Marvel has now revealed that his powers are not what you think they are.

Deadpool may belong to the X-Men family but he is not a mutant. He is a Mutate. The difference between the two is that while mutants manifest their powers naturally, the powers of a mutate are triggered by some sort of an experiment.

Deadpool gained his powers after the Weapon X program. The infused Wade Wilson with Wolverine’s regenerative abilities. This did help him cure his cancer but left him with a scarred body.

Now let’s get back to the present day. Black Panther is working on an experiment called “star cells”, a kind of nanites that can be used in a laser-like form to heal cells instantly.

Meanwhile, Deadpool makes an Unexpected visit to Wakanda hoping to get a chunk of vibration to save his friend, Willie Lumpkin. However, Black Panther doesn’t trust Deadpool as he believes that he would just turn the vibranium into a weapon. This leads to a fight between the two.

The fight stops when Black Panther slices off Deadpool’s arm using a star cell beam. Usually, Deadpool heals from his wounds but this time that doesn’t happen.

Black Panther further explains that Deadpool’s cells were healed by star cells and his now-healthy cells are not regenerating. This means, that it’s not a healthy tissue that replaces the lost part, it’s cancer. Deadpool doesn’t have a healing factor; he has a dying factor.

This raises some intriguing questions. If cancer is what grows back in Deadpool, shouldn’t he be 100 per cent tumour by now? Perhaps we all have to wait for the upcoming issues.

Either way, it seems like Wade will be coming back for T’Challa’s throne. Stay tuned for more.

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 ========================================