New details on the officially confirmed upcoming LittleBigPlanet 2 have been leaked onto the web from the latest issue of Game Informer, and damn, this ain't your younger-self-from-just-over-a-year-ago's game. From what was relayed onto NeoGAFLBP 2 isn't just a platformer with a very, very robust level editor, but a simplistic basis to design almost any type of game ever. Game Informer was demoed an RTS style game made with LBP 2 to prove it, but Media Molecule says you can make anything from racing games to first-person shooters.
It's a little crazy all the advancements that are purported to be made in the sequel. Not only will you be able to assign controls far better, but you'll be able to design your own responses with a tool called the direct control seat. Level designers won't be constrained to using the signature gameplay mechanics of LBP. For instance, if you were remaking a classic Mario level you could even make the Sackboys jump exactly like Mario.
On top of this is an enemy creator that is far more robust than the original, and has an AI editor, a robust sound creator, PlayStation Eye integration for loading levels using QR codes, the ability to string levels together, a crap ton of gadgets, the ability to make cutscenes, and an overhauled storyline mode that at the moment features the same platforming style gameplay as the original's. The post at NeoGAF also has some level and plot spoilers if you're really tempted.
Looks like Sackboy has really sacked up... I'm sorry. I had to.
Get more destructoid: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.