Skip to main content

A Narrative Analysis of Dragon Ball Super: Broly Part 1

Yes, I know: analysis like this really isn't very necessary for what is essentially a shonen. The Dragon Ball franchise utilizes an incredibly simplistic narrative structure. This is still true for Dragon Ball Super, and Dragon Ball Super: Broly. But it's still fun to take a look at in detail, especially at the things we might otherwise miss during the spectacle of it all.

A few quick notes to think about before going in. Mainly it's that Akira Toriyama, the creator of Dragon Ball, has a very lax way of writing his stories. In essence, he writes stories specifically for the chapter, not necessarily for the arc as a whole. This in turn results in multiple retcons across the story's entirety.

The official excuse is that he is forgetful, which may or may not be true. I believe that the real reason is that he just doesn't care - he is more invested in his characters' future than he is in their past. While this does suck from a plot cohesiveness standpoint, it has its upsides as well. Because the writing is lackadaisical, it means we should enjoy it similarly. Which is a cheeky thing to say, when a good portion of the Dragon Ball fandom takes it far too seriously.

For example, there are too many people out there that are obsessed with how powerful the characters are, and must know what their capabilities are in a numerical sense. Of course, Toriyama is the cause for this technical obsession with 'Battle Power'. His initial usage of it is designed to heighten tension. It's a cheap shot, but very very effective. He has since come to the realization that the device he once employed will become its own narrative barrier. Though he does his best to distance himself from the Battle Power thing, the damage is already done. There are far too many fans who crave it at this point.

In short, Dragon Ball has two sets of fans. The first set of fans typically love the story's quirky, weird, colorful characters and their arcs. The second are also obsessed with the characters, albeit more about how well they fight, how strong they are, and how unstoppable they can become. There's nothing wrong with either set, but you can already see the fundamental differences that guides almost all creative decisions.

For the most part, Toriyama caters to his first set of fans through the manga, which is now drawn and developed by Toyotaro. As as aside, and to help lend credence to my viewpoint, Toyotaro is arguably Toriyama's #1 fan. What they do with the manga is stunning.

This must mean that the second type are catered to via other means - specifically the anime. On top of that, the movies in the Dragon Ball Z era take it up a notch. Most of the type two fans love the films, especially classic Broly. This is especially true of DBS:Broly. The only difference is that this new Broly has the official stamp of approval from Toriyama himself.

There's an interesting technical facet to any fandom, and that's determining what parts of what story is canon, and which are not. In the case of the Dragon Ball franchise, only stories that Toriyama himself has written are counted as canon. This has put the entire fandom into overdrive. Although this movie is clearly made to be serious fan service, there are still parts of it that the first type of fan can enjoy. For example, the classic renditions of Broly represent him as just a mindless, all-powerful animal. The new Broly has much more pathos, and thus far more narrative potential.

Stay tuned as I delve a little deeper into the characters next week!


Popular posts from this blog

Resolutions Schmesolutions

When I was in high school, I had a somewhat chaotic approach to cleaning. It began when I got frustrated by a cluttered desk, and dumped everything on the floor. I put back only the things I absolutely needed, shelved a few other things, and threw away everything else. This turned into a cleaning ritual where everything was classified as "keep", "store", or "discard". The goal was to discard as much as possible while treasuring only the things I truly wanted to keep.

Over time, that habit of mine evolved into something different. It became the cornerstone of my minimalist lifestyle. I learned to judge who and what I needed to treasure, and who and what I needed to discard. But it wasn't only about surroundings - it was also about self. I always found the idea of a classical hermit living on a mountain somewhat appealing, and I made many decisions to reach a reasonable interpretation of that. The path was much rockier than anticipated.

Anyway, at the b…

Coding schmoding: Populating Levels

Apologies for not updating last week. I ran into a number of problems while trying to put items in levels. It certainly sounded simple enough, right? If there's room for something to spawn, then spawn it. Boom, done.

Of course it's more problematic than it first seemed. Long story short, last week I spent a good chunk of time trying to figure out why functions I wrote weren't spawning anything at all. I don't recall all of the problems, but it was just one thing after another. You should have seen my browser tab - it was filled with Unity reference pages.

In any case, I decided to pick it back up this week, and finally got some progress forward.

Lots of learning and coding these past couple of weeks. Been trying to randomly spawn objects in the game world. Took longer than I wanted, and it's still wonky. Making progress, though. My sanity thanks liquor and pot. Read the Devblog in bio. #gamedev #gamedesign #indiegame #indiedev #solodev #indiestudio #prototyping #bsp…

Sorry for being MIA

Soooo there has been an inordinately long pause since the last update. Many things have taken my attention away: my day job, bills, projects, family, women. You know, everyday stuff.

As a result of all those other things taking my time, development on Eclipse Perilous has been nonexistent. But as I've been handling the other stuff, ideas surrounding the game have been percolating in the back of my mind. I've come to realize that much of what I'm doing now is off, and that my approach needs to be adjusted.

First and perhaps most important is that I don't have proper project management set up. Though I have time blocked off in my calendar, it simply isn't enough to keep me on track. Not having the project mapped out allows other things to steal time from it. In an effort to combat this, I'm setting up AsanaHacknPlan. I hope that better project structure will lead to a more productive schedule.

The art process is also flawed - I've been using a tablet and styl…