#but I've been getting it multiple times a week | Explore Tumblr posts and blogs

thankskenpenders · 2 days ago

Text

Thoughts on Sonic 3!

On December 10th, 2018, I was on the last day of a trip to Milwaukee. The night before, I'd attended the wedding of one of my best friends, Jake, who I've known since high school. Even though half of us were sick the whole trip, it was a great time. Derek had asked the wedding DJ to play "One Week" as the first request of the night, and proceeded to lip sync the entire song on the dance floor. On that cold winter morning in a hotel room hundreds of miles from home, Derek and I groggily checked Twitter on our phones and saw the shocking news: Paramount had teased the design for Sonic from their upcoming live action film. Even in silhouette, the shape of his face and the realistic curvature of his limbs made him look like a grotesque little homunculus. This movie was going to suck.

Six years later, I've now seen the third entry in what's become a hugely successful Sonic film franchise. It features Keanu Reeves as the voice of Shadow the Hedgehog in a fairly faithful adaptation of his story from Sonic Adventure 2. At the time of writing, it currently sits at a whopping 86% positive rating on Rotten Tomatoes, vying for the title of the best-reviewed theatrically released video game movie of all time. Critics are saying nice things about the emotional journey of Shadow the Hedgehog. Never in a million years did I think I'd see this day.

I, too, have now seen this movie, and... yeah, it's pretty good.

I'm gonna get deep into spoilers here, so I'll just say up front that I liked the movie. It feels like just about the best possible execution of this version of Sonic. But that's also damning it with faint praise, depending on who you ask.

If you're a fan of the games who didn't like the second movie, you probably won't get much out of this one, either, unless you just really love Shadow so much that nothing else in the movie matters to you. It doesn't reinvent the wheel for this film series. It's still got a heaping helping of broad comedy, cheap pop culture references, bad one-liners, and characterization that diverges greatly from the source material. This is not high art, nor is it a direct adaptation of Sonic Adventure 2. If you're the kind of person who hates this portrayal of Sonic and Eggman, or a lore nerd who'll hate that they let Shadow do Chaos Control without an Emerald, then just don't bother with this.

On the other hand, if you did enjoy the last movie, then you'll probably have a fun time here, too. Shadow is very cool. The action is the best it's ever been. There's a bit more focus on characters from the games, and less on human characters invented for the movies—with the exception of Agent Stone, who's in this a lot because everyone likes him. There's a lot of SA2 fanservice. They even play "Live and Learn." It's a fun time! Be sure to stick around through the end credits.

And now, to dig deeper, let's get into the spoilers! I'm gonna jump around a lot and talk about different aspects of the movie, spoiling everything along the way.

Shadow and his reams of lore

Here's the main thing you came for: Shadow is great in this! They really did him justice. Keanu Reeves is extremely solid in the role. He can be a bit flat as an actor sometimes, but I think he did well here. He can be tough and menacing, but he can also be earnest and emotionally vulnerable. Good casting call. Excited at the prospect of seeing more of him in the future.

Really, as a Sonic Lore Nerd I'm most interested in discussing the changes they made to Shadow's backstory. I'm sure there will be many fans upset with the changes, but for the sake of streamlining a complicated backstory that was subject to a bunch of retcons and multiple layers of amnesia and fitting it into a 110-minute movie, I think they generally made smart choices.

For one, Gerald didn't create Shadow using Black Arms DNA, because Gerald didn't create Shadow at all! Instead, Shadow arrived on Earth inside a meteor, and Gerald was merely the prominent GUN scientist who studied him after he was captured. (That meteor does have very strong Black Arms vibes, though, so I wouldn't rule out the possibility of them exploring that stuff in the future.) This simplifies things a lot and allows Shadow to be a direct foil for Sonic, kind of a version of our hero who was treated as a lab rat and lost the only human he considered family instead of finding happiness like Sonic has. Then later Shadow hurts Tom and Sonic wants revenge, and it mirrors Shadow's feelings about Maria, and after they fight they can empathize with each other over this, Shadow sees the error of his ways and helps save the world, yada yada yada. You get it. People predicted 95% of this movie's plot from the trailers, but it's effective.

Likewise, all of the stuff about creating Shadow as the ultimate life form who's immune to all disease to cure Maria's illness is completely cut out. Shadow's still called the ultimate life form, but he's treated as more of an energy source than a genetic research project here, playing off of the stuff about Eggman wanting to harness Sonic's natural Chaos Energy in the movies. The original intent behind the ultimate life form project was always hard to explain in the games and doesn't even come up that much, so I don't blame them for cutting it.

Because Gerald isn't doing genetic experiments and creating artificial life, the Biolizard also doesn't exist. It does, however, appear in an old monster movie Shadow and Maria watch in a montage, with Shadow later commenting that he worries he's a monster like the one he saw in the movie. That's a clever way to include it, I think.

The ARK sort of exists. There was no space colony back in the '70s, all of the events of Shadow's flashbacks just took place at a secret GUN base on Earth. Fair enough for a version of the story ostensibly set in the real world. The big space laser in the third act of the film is obviously supposed to evoke the ARK, but it's referred to as simply the Eclipse Cannon. It's still not a full-blown space colony, just a weapon of mass destruction Gerald designed for GUN in exchange for his release (while also secretly planning to use it to blow up the planet in an act of revenge). I am, however, pleased to report that the Eclipse Cannon still has a giant Eggman face on it.

And as for Maria: I like her in this! She's obviously not going to get a ton of screentime, and she's always going to be a very straightforward character, but she's more playful and lively here. She teases Shadow for being grumpy and plays with him a lot. She feels less like this perfect embodiment of everything good and pure in the world and more like an actual kid. She's still not a complex character, but it works.

And the most important question: do they show a child getting shot and killed by the military? The answer is almost. In the flashback, GUN soldiers chase Maria, Shadow, and Gerald and ready their guns, but the young Commander Walters (who's in his 20s rather than being a kid) grabs them and tries to stop them from firing on a child. In the chaos, a soldier fires, missing Maria but hitting a generator that then blows up and kills Maria. So, y'know, close enough I suppose.

So, yes, many of the details change here, but they captured the gist of Shadow's story from SA2. The emotional core is there. I will say, though, I almost feel like Shadow isn't in this movie as much as I thought he'd be? I think he's used effectively in all of his scenes, and they make room for his backstory, and BOY does he get to kick ass in his fights, but for much of the middle part of the movie he's overshadowed by Ivo and Gerald. Though this might be a compromise to leave more screentime for...

Tails and Knuckles

I'm relieved to report that Tails and Knuckles both get a good amount of cool stuff to do in this! They don't feel like an afterthought.

I was worried that Tails in particular would completely fall by the wayside, since even his debut movie didn't entirely know what to do with him. But he's good here. He pretty much just feels like the Tails from the games at this point, especially since they dropped that fawning admiration he had for Sonic with that running gag of him going "Only Sonic the Hedgehog could do that!" He often chimes in as the one who wants Team Sonic to stick together when Sonic and Knuckles bicker. He particularly gets to shine in the Mission Impossible-inspired heist sequence at the GUN headquarters in London that serves as the climax of the second act, which feels like it was tailor made to let him shine as the tech guy of the team. He also gets several opportunities to swoop in and catch someone for a save in an action scene. He's good in this!

Knuckles is... fine. He's definitely fallen into the role of the comic relief dumb bruiser since joining the good guys, but he's at least a little better than he was in his own streaming show. The jokes lean more into him just being really brash about his strength and skill, rather than him being this archaic warrior who doesn't understand anything about the modern world. He also gets a few more serious bits in the back third of the movie where he gets to shine a little more, so overall it evens out to him being fine. They could've done way worse.

As for the relevance of the Knuckles show: Knuckles is now said to be the guardian of the Master Emerald, like in the games, though with no Angel Island this amounts to him hiding it somewhere for safekeeping. It's eventually revealed that he just gave it to Wade, who gets exactly one scene (sorry, Wade-heads) for a joke about him using the Master Emerald as a hockey puck. So, the miniseries explained why Knuckles has a connection with Wade. That's it! Also I think Knuckles might use the Flames of Disaster a bit in fights, but they never called the technique out by name, so I never really thought about it. So, yeah, the six-episode streaming miniseries about Wade bowling has zero meaningful relevance to the Shadow movie. Who could have seen this coming?

Miscellaneous humans

For that matter, the human supporting cast is MASSIVELY downplayed in this one. Tom and Maddie are there for two key sequences (the beginning of the movie and the GUN HQ heist), but otherwise they disappear for long stretches of the movie. They don't go to Japan in act I, nor do they go to space in act III, and there's no subplot for them during those periods, either. There's nothing like the wedding subplot in Sonic 2 where they'd constantly cut back to Hawaii for comic relief with the humans and only reveal why this was relevant to the plot near the end. (There's also no random dance battle in Siberia.) If a human character is here, it's because they have something to contribute to the plot right away. Most people will probably consider this an improvement, and I'd certainly say it makes for a much tighter script, though I have to remind everyone that I thought the wedding being a GUN sting operation was such a funny twist that I'm a defender of the Hawaii subplot.

On the subject of Tom, something funny I've noticed is that they've just completely downplayed the fact that Tom and Wade are cops. Tom being a cop never comes up once. Wade being a cop only gets referenced via the fact that he's practicing hockey on the roof of the police station in his one scene, but he's not in uniform or anything. They clearly got the memo that we don't want Sonic to hang out with cops.

Here's something else funny: Rachel and Randall got character posters, but they're actually not in the movie! Not technically, anyway. During the heist sequence at GUN HQ, Tom and Maddie use some gadgets Tails invented to holographically disguise themselves as those other characters. But the real Rachel and Randall never show up in the flesh. It's a very odd way to shoehorn the actors into the movie. (Jojo is also absent. They did not give her Amy's role of being the girl who reminds Shadow of Maria. Instead they just let Sonic have the big heart to heart with Shadow that makes him switch sides.)

You know who IS in this movie? Krysten Ritter. Not as the voice of Rouge, as the fandom once hoped, but as a director for GUN. She gets like three scenes and she feels completely checked out the whole time. Can't say I blame her! She's not really a character, just a plot necessity. Commander Walters dies in Japan but gives Sonic one of two keycards needed to activate the Eclipse Cannon, and then Ritter's character assumes Sonic stole it and labels him a bad guy. So that's why they have to break into GUN HQ in the second act instead of just talking things out with them. Still, I am at least relieved that Sonic doesn't work with GUN for most of the movie.

I gotta be honest: when Walters pulled a credit card-shaped object out of his pocket, I thought he was about to give Sonic another Olive Garden gift card as his final act before dying. Part of me wishes that happened.

The supporting human character in this who really gets to shine is Agent Stone, which I'm sure most fans will agree was the correct choice. There's a LOT of Agent Stone in this. He's good. I don't have much to say about him, but he's fun as usual.

But, of course, the ones who steal the show are Jim Carrey, and his costar Jim Carrey.

The Robotniks

I've gone back and forth on whether or not I can actually see movie Robotnik as Robotnik. I think with this third and final entry in the Jim Carrey Robotnik Trilogy, I've landed on... yeah, that's just Jim Carrey playing a Jim Carrey character. He's absolutely having fun with the role, and I enjoyed watching him, but I think a lot of that comes down to the fact that I'm a millennial who grew up watching Jim Carrey movies. If you didn't like him before, this movie will probably be nails on a chalkboard to you, because now there are two of him.

Ivo's arc here leans very heavily into the fact that he grew up as an orphan and never knew his family, a thing offhandedly mentioned in the first movie that's never been a thing for any other version of the character. Here, he learns that he has a living grandfather who's also a mad scientist, and it feels like a hole in his heart has been filled. It certainly makes sense for a place to take this version of the character, and it fits with the movie's themes of finding and losing family, but the cartoonish, childlike affection Ivo feels towards Gerald and all the scenes of them frolicking and dancing together have basically nothing to do with the characters from the games. He's a fun villain for this movie, but he's overwhelmingly used as comic relief this time rather than as a serious threat. He doesn't particularly feel like Sega's Dr. Ivo Robotnik, the arch nemesis of Sonic the Hedgehog who'd take over the world with an army of robots and a fleet of airships in the span of a day if Sonic wasn't around to stop him. He's a guy who lives in a big crab robot and has some drones. He has more in common with Carrey's depictions of the Grinch or the Riddler or Count Olaf than Dr. Eggman. Though he does, at least, finally get his outfit from the games by the end of the movie. So that's something. And also he's in a fat suit now. They only make jokes at the expense of his weight a little. Hooray...?

Gerald, meanwhile, is... largely the same character as movie Eggman, but older, so they can make jokes about him having saggy flesh and smelling funny and needing dentures. (Also, his voice kind of sounds like Homer Simpson sometimes?) To his credit, Carrey absolutely nails the handful of more serious scenes Gerald gets, whether it's Maria's death or his sinister turn when he reveals that he actually wants to destroy the Earth. But then it's right back to goofs about there being two of the same guy. Even the final battle features a lot of slapstick shenanigans with the two Robotniks fighting each other. I was able to enjoy the absurdity of it all, but if the humor doesn't land for you the dual Jim Carrey schtick is a hell of a lot of the movie. I wouldn't be surprised if there was more Gerald than Shadow in the movie, when you go and tally up their screentime. I was able to enjoy the sheer absurdity of it, but your mileage will vary.

I will, however, say that the split screen stuff they do with the two Carreys is EXTREMELY impressive, from a filmmaking perspective. They were absolutely flexing with their ability to pull the effect off. They don't rely on cheap tricks like cutting a lot, or having shot/reverse shot scenes where you're looking at the back of a body double's head. Instead they have a lot of long takes where the two Robotniks are talking to each other, you can see both of their faces, and they'll even hug and touch each other a lot, and the whole time the conversation maintains a natural pace like it really is two actors playing off of each other. It's really well done. It's an incredibly silly idea, but boy did they commit to it.

Sonic

I've hardly said anything about Sonic himself in all of this. It's his movie, isn't it! Well... I don't know, he's fine.

I feel like movie Sonic is a known quantity at this point, and either you like this take on the character or you don't. There was some speculation early on that this was supposed to be a younger Sonic who would grow into being the character we know from the games and comics, the one who's still got lots of quips but is also kind of aloof and cool, a free spirit who goes where the wind takes him, a figure the other characters look up to. And... no, that didn't happen. Once again he gets more serious as the stakes are raised, and he's totally badass when he goes Super, but the rest of the time he's still a little goober with tons of generic one-liners who learns schmaltzy lessons about the importance of family. He's still constantly going to undercut the tension of most scenes by cracking a pop culture reference that will make the average American parent go "haha I've heard of that." I don't think they're ever gonna change that. I think this just what the writers think Sonic is like.

And, again, for what it is, it's fine. He's a little annoying. You already know how you feel about movie Sonic. This third entry won't change that. But they do, at least, have him say "Talk about low budget flights, no food or movies... I'm outta here!" before jumping out of a helicopter. As my thoughts on the climax will show, I am not immune to fanservice.

The climax

God, the climax is SOOOOO fucking good. It's fantastic. Easily the best action these movies have ever done.

Rather than saving Super Shadow for the team-up with Sonic at the end, they have both of them go Super to fight each other first, and they just go full DBZ with it, fighting across the entire planet. It absolutely rules. I think this is the new coolest fight the two of them have had in anything ever. And then they have to stop the Eclipse Cannon together, and sure, there's no Biolizard. But Gerald DOES release a swarm of GUN Hunter robots, and the ensuing space battle turns into some Gundam shit. It's good! It's so good!!! The movie's flaws kind of melt away for me here when I'm watching Super Shadow take out an army of robots with Chaos Spears on the big screen. What a timeline we're living in.

And yes, they play "Live and Learn." They had to. They knew the assignment. They actually play a slight remix, but it's still got the original vocals, so it's perfectly recognizable. Actually, the tune of the song is used as a leitmotif for Shadow throughout the movie, first introduced via an acoustic guitar version played by Maria, and I really love that. I've been begging these movies to use more music from the games the whole time, and I'm glad they finally did so here. (They also use the traditional level clear jingle early in the film, and Eggman's theme from SA2 is very briefly used as a ringtone.)

... Anyway, uh, meanwhile Eggman, Tails, and Knuckles straight up just kill Gerald to save the world? They unceremoniously knock him into an energy field at the end of their slapstick fight aboard the Eclipse Cannon and he disintegrates like he hit a bugzapper. It's over in an instant. It's not graphic or anything, but it's, like... I didn't expect them to show it, or for it to be such a casual murder! Eggman has one quip about it and then immediately moves on.

Shortly after this, Eggman and Shadow sacrifice themselves to stop the Eclipse Cannon. Shadow's sacrifice doesn't stick, obviously (he's revealed to be alive by the end of the second stinger—pretend to be shocked), but Eggman's probably dead dead. I seriously doubt Jim Carrey's gonna come out of retirement for these movies again. His final moments before the big explosion are also SO dragged out and belabored. He has a dramatic final line like ten times in a row. It really just feels like the series saying goodbye to Carrey. And, again, it feels like a fitting enough end for this Eggman's arc, but it's an odd adaptation of the character from the games.

And so, that's what we're left with. This is far from Sonic Adventure 2: The Movie. It's not that, though there are many, many references made to that game in particular. It's a sequel to the film Sonic the Hedgehog 2 that has a similar tone and style, but Shadow and Gerald are in it, and Shadow gets some really cool fights, and there's a liiiiiittle more focus on stuff from the games than last time, and the script's a little tighter. If that sounds fun to you, you will have fun with this. I know I did. If it doesn't, you're probably better off waiting for them to inevitably do an animated reboot whenever this live action series runs out of steam.

It hasn't quite run out of steam yet, though...

The post-credits scenes, and the future

One of the big questions going into this was: what's next? How do they top a Shadow movie with heavy Sonic Adventure 2 overtones, in terms of hype for the fans? How do you fill Eggman's shoes after Carrey retires, for real this time? There are still more fan favorite rival characters to get through, but how many movies in a row can they introduce a furry foe for Sonic who inevitably turns good and helps him stop a larger threat by the end? And when the hell are we gonna see the girls?

Well, we now have our answer, and it's one I'm cautiously excited for: a whole army of Metal Sonics, and Amy!

Yes, Amy! Finally!! It's an absolute crime that we've gone three whole movies and a streaming miniseries without including the female lead of the series. I've complained about this ad nauseum (and also the fact that they cut Rouge from the story). But at least now they're finally doing something about it.

But now the question is, how will they characterize Amy? Sega's struggled with her for years, and there's a million different directions you can take her. Her one scene here has her smashing a bunch of Metal Sonics and wearing a cloak for the sake of a dramatic reveal, which gives her the vibes of a mysterious, badass action girl. This is, of course, completely different from how Sonic and Amy met in the games. What will her personality be like? She doesn't speak here, so who will they get to play her? Where did she come from? Will she even have a crush on Sonic? All of these have yet to be determined. So, like, I'm hyped to finally see Amy, a character who should've been in the movies from the start, but they could so easily end up playing it safe with an incredibly boring girlboss version of Amy who's no fun at all. We'll have to wait and see.

(My prediction: they're going to try to cast either Zendaya or Ariana as Amy.)

Metal Sonic, likewise, is very exciting, and he looks perfect. He looks just like the design from the games. But the question is: what will they do with this army of Metals? Will they be lead by one main Metal Sonic, perhaps Neo Metal Sonic, who gets to be a proper bad guy? Will they take some cues from Sonic CD, Heroes, and the OVA, or do something completely original? Where did they come from? Were they activated as a failsafe after Eggman died? Did they and Amy come from some sort of bad future, riffing on Sonic CD's time travel? Will they explore the fact that Metal wants to be the one and only Sonic? Or will they just be an army of disposable robot grunts for Sonic and friends to mow down like it's a Dynasty Warriors game, while some other villain takes center stage?

It could go so many different ways, and some prospects are more exciting than others. I mean, the Knuckles show had endless possibilities for what it could do with him, and none of the options on my bingo card were "Pachacamac's ghost tells him to help Wade win a bowling tournament." And while I'm a sicko who thinks it's funny that the Knuckles show is what it is, forgive me for keeping my hype about Amy and Metal Sonic in check here until we learn more.

Regardless of what they do, it'll still be hard to top the hype of Shadow, and it'll be hard to fill Jim Carrey's shoes for general audiences. So despite this clear statement of intent, I have no idea what the future of this film franchise holds. But regardless of what they do, I can say one thing for certain: the kids in my theater were hyped as hell for it. They popped off over Metal Sonic, and they were screaming their heads off with excitement over Amy. I heard a teenage girl on the opposite end of my row of seats say "finally!" over Amy's reveal, verbalizing my exact thoughts. She also said that this movie was "peak," though it diverged from the games, and she hoped they'd do a movie with Silver and Blaze someday.

The kids are gonna be okay.

#tkp post #other media #sonic 3 spoilers

240 notes · View notes

qwertyprophecy · 2 days ago

Text

Mortholme Post-Mortem

The Dark Queen of Mortholme has been out for two weeks, and I've just been given an excellent excuse to write some more about its creation by a lenghty anonymous ask.

Under the cut, hindsight on the year spent making Mortholme and answers to questions about game dev, grouped under the following topics:

Time spent on development Programming Obstacles Godot Animation Pixel art Environment assets Writing Completion Release

Regarding time spent on development

Nope, I’ve got no idea anymore how long I spent on Mortholme. It took a year but during that time I worked on like two other games and whatever else. And although I started with the art, I worked on all parts simultaneously to avoid getting bored. This is what I can say:

Art took a ridiculous amount of time, but that was by choice (or compulsion, one might say). I get very excitable and particular about it. At most I was making about one or two Hero animations in a day (for a total of 8 + upgraded versions), but anything involving the Queen took multiple times longer. When I made the excecutive decision that her final form was going to have a bazillion tentacles I gave up on scheduling altogether.

Coding went quickly at the start when I was knocking out a feature after another, until it became the ultimate slow-burn hurdle at the end. Testing, bugfixing, and playing Jenga with increasingly unwieldy code kept oozing from one week to the next. For months, probably? My memory’s shot but I have a mark on my calendar on the 18th of August that says “Mortholme done”. Must’ve been some optimistic deadline before the ooze.

Writing happened in extremely productive week-long bursts followed by nothing but nitpicky editing while I focused on other stuff. Winner in the “changed most often” category, for sure.

Sound was straightforward, after finishing a new set of animations I spent a day or two to record and edit SFX for them. Music I originally scheduled two weeks for, but hubris and desire for more variants bumped it to like a month.

Regarding programming

The Hero AI is certainly the part that I spent most of my coding time on. The basic way the guaranteed dodging works is that all the Queen’s attacks send a signal to the Hero, who calculates a “danger zone” based on the type of attack and the Queen’s location. Then, if the Hero is able to dodge that particular attack (a probability based on how much it's been used & story progression), they run a function to dodge it.

Each attack has its own algorithm that produces the best safe target position to go to based on the Hero’s current position (and other necessary actions like jumping). Those algorithms needed a whole lot of testing to code counters for all the scenarios that might trip the Hero up.

The easiest or at least most fun parts for me to code are the extra bells and whistles that aren’t critical but add flair. Like in the Hero’s case, the little touches that make them seem more human: a reaction speed delay that increases over time, random motions and overcompensation that decrease as they gain focus, late-game Hero taking prioritising aggressive positiniong, a “wait for last second” function that lets the Hero calculate how long it’ll take them to move to safety and use the information to squeeze an extra attack in…

The hardest attack was the magic circle, as it introduced a problem in my code so far. The second flare can overlap with other attacks, meaning the Hero had to keep track of two danger zones at once. For a brief time I wanted to create a whole new system that would constantly update a map of all current danger zones—that would allow for any number of overlapping attacks, which would be really cool! Unfortunately it didn’t gel with my existing code, and I couldn’t figure out its multitudes of problems since, well…

Regarding obstacles

Thing is, I’m hot garbage as a programmer. My game dev’s all self-taught nonsense. So after a week of failing to get this cool system to work, I scrapped it and instead made a spaghetti code monstrosity that made magic circle run on a separate danger zone, and decided I’d make no more overlapping attacks. That’s easy; I just had to buffer the timing of the animation locks so that the Hero would always have time to move away. (I still wanted to keep the magic circle, since it’s fun for the player to try and trick the Hero with it.)

There’s my least pretty yet practical solo dev advice: if you get stuck because you can’t do something, you can certainly try to learn how to do it, but occasionally the only way to finish a project within a decade to work around those parts and let them be a bit crap.

I’m happy to use design trickery, writing and art to cover for my coding skills. Like, despite the anonymous asker’s description, the Hero’s dodging is actually far from perfect. I knew there was no way it was ever going to be, which is why I wrote special dialogue to account for a player finding an exploit that breaks the intended gameplay. (And indeed, when the game was launched, someone immediately found it!)

Regarding Godot

It’s lovely! I switched from Unity years ago and it’s so much simpler and more considerate of 2D games. The way its node system emphasises modularity has improved my coding a lot.

New users should be aware that a lot of tutorials and advice you find online may be for Godot 3. If something doesn’t work, search for what the Godot 4 equivalent is.

Regarding animation

I’m a professional animator, so my list of tips and techniques is a tad long… I’ll just give a few resource recommendations: read up on the classic 12 principles of animation (or the The Illusion of Life, if you’d like the whole book) and test each out for yourself. Not every animation needs all of these principles, but basically every time you’ll be looking at an animation and wondering how to make it better, the answer will be in paying attention to one or more of them.

Game animation is its own beast, and different genres have their own needs. I’d recommend studying animations that do what you’d like to do, frame by frame. If you’re unsure of how exactly to analyse animation for its techniques, youtube channel New Frame Plus shows an excellent example.

Oh, and film yourself some references! The Queen demanded so much pretend mace swinging that it broke my hoover.

Regarding pixel art

The pixel art style was picked for two reasons: 1. to evoke a retro game feel to emphasise the meta nature of the narrative, and 2. because it’s faster and more forgiving to animate in than any of my other options.

At the very start I was into the idea of doing a painterly style—Hollow Knight was my first soulslike—but quickly realised that I’d either have to spend hundreds of hours animating the characters, or design them in a simplistic way that I deemed too cutesy for this particular game. (Hollow Knight style, one day I’d love to emulate you…)

I don’t use a dedicated program, just Photoshop for everything like a chump. Pixel art doesn’t need anything fancy, although I’m sure specialist programs will keep it nice and simple.

Pixel art’s funny; its limitations make it dependent on symbolism, shortcuts and viewer interpretation. You could search for some tutorials on basic principles (like avoiding “jaggies” or the importance of contrast), but ultimately you’ll simply want to get a start in it to find your own confidence in it. I began dabbling years ago by asking for character requests on Tumblr and doodling them in pixels in whatever way I could think of.

Regarding environment assets

The Queen’s throne room consists of two main sprites—one background and one separate bit of the door for the Hero disappear behind—and then about fifty more for the lighting setup. There’s six different candle animations, there’s lines on the floor that need to go on top of character reflections, all the candle circles and lit objects are separated so that the candles can be extinguished asynchronously; and then there’s purple phase 2 versions of all of the above.

This is all rather dumb. There’s simpler ways in Godot to do 2D lighting with shaders and a built-in system (I use those too), but I wanted control over the exact colours so I just drew everything in Photoshop the way I wanted it. Still, it highlights how mostly you only need a single background asset and separated foreground objects; except if you need animated objects or stuff that needs to change while the game’s running, you’ll get a whole bunch more.

I wholeheartedly applaud having a go at making your own game art, even if you don’t have any art background! The potential for cohesion in all aspects of design—art, game, narrative, sound—is at the heart of why video games are such an exciting medium!

Regarding writing

Finding the voices of the Queen and the Hero was the quick part of the process. They figured that out they are almost as soon as writing started. I’d been mulling this game over in my mind for so long, I had already a specific idea in mind of what the two of them stood for, conceptually and thematically. When they started bantering, I felt like all I really had to do was to guide it along the storyline, and then polish.

What ended up taking so long was that there was too much for them to say for how short the game needed to be to not feel overstretched. Since I’d decided to go with two dialogue options on my linear story, it at least gave me twice the amount of dialogue that I got to write, but it wasn’t enough!

The first large-scale rewrite was me going over the first draft and squeezing in more interesting things for the Queen and the Hero to discuss, more branching paths and booleans. There was this whole thing where the player’s their dialogue choices over multiple conversations would lead them to about four alternate interpretations of why the Queen is the way she is. This was around the time I happened to finally play Disco Elysium, so of course I also decided to also add a ton of microreactivity (ie. small changes in dialogue that acknowledge earlier player choices) to cram in even more alternate dialogue. I spent ages tinkering with the exact nuances till I was real proud of it.

Right until the playtesters of this convoluted contraption found the story to be unclear and confusing. For some reason. So for my final rewrite, I picked out my favourite bits and cut everything else. With the extra branching gone, there was more room to improve the pacing so the core of the story could breathe. The microreactivity got to stay, at least!

A sample of old dialogue from the overcomplicated version:

Regarding completion

The question was “what kept me going to actually finish the game, since that is a point many games never even get to meet?” and it’s a great one because I forgot that’s a thing. Difficulties finishing projects, that is—I used to think it was hard, but not for many years. Maybe I’ve completed so many small-scale games already that it hardly seems that unreasonable of an expectation? (Game jams. You should do game jams.)

I honestly never had any doubt I was going to finish Mortholme. When I started in late autumn last year, I was honestly expecting the concept to be too clunky to properly function; but I wished to indulge in silliness and make it exist anyways. That vision would’ve been easy to finish, a month or two of low stakes messing around, no biggie. (Like a game jam!)

Those months ran out quickly as I had too much fun making the art to stop. It must’ve been around the time I made this recording that it occurred to me that even if the game was going to be clunky, it could still genuinely work on the back of good enough storytelling technique—not just writing, but also the animation and the Hero’s evolving behaviour during the gameplay segments which I’d been worried about. The reaction to my early blogging was also heartening. Other people could also imagine how this narrative could be interesting!

A few weeks after that I started planning out the narrative beats I wanted the dialogue to reach, and came to the conclusion that I really, really wanted it to work. Other people had to see this shit, I thought. There’s got to be freaks out there who’d love to experience this tragedy, and I’m eager to deliver.

That’s why I was fine with the project’s timeline stretching out. If attention to detail and artistry was going to make this weird little story actually come to life, then great, because that’s exactly the part of development I love doing most. Projects taking longer than expected can be frustrating, but accepting that as a common part of game dev is what allows confidence in eventual their completion regardless.

Regarding release

Dear anonymous’s questions didn’t involve post-release concerns, but it seems fitting to wrap up the post-mortem by talking about the two things about Mortholme's launch that were firsts for me, and thus I was unprepared for.

1. This was the first action game I've coded. Well, sort of—I consider Mortholme to be a story first and foremost, with gameplay so purposefully obnoxious it benefits from not being thought of as a “normal” game. Still, the action elements are there. For someone who usually sticks to making puzzle games since they’re easier to code, this was my most mechanically fragile game yet. So despite all my attempts at playtesting and failsafes, it had a whole bunch of bugs on release.

Game-breaking bugs, really obvious bugs, weird and confusing bugs. It took me over a week to fix all that was reported (and I’m only hoping they indeed are fully fixed). That feels slow; I should’ve expected it was going to break so I could’ve been faster to respond. Ah well, next time I know what I’ll be booking my post-release week for.

2. This was my first game that I let players give me money for. Sure, it’s pay-what-you-want, but for someone as allergic to business decisions as I am, it was a big step. I guess I was worried of being shown that nobody would consider my art worth financial compensation. Well, uh, that fear has gone out of the window now. I’m blown away by how kind and generous the players of Mortholme have been with their donations.

I can’t imagine it's likely to earn a living wage from pouring hundreds of hours into pay-what-you-want passion projects, but the support has me heartened to seek out a future where I could make these weird stories and a living both.

Those were the unexpected parts. The part I must admit I was expecting—but still infinitely grateful for—was that Mortholme did in fact reach them freaks who’d find it interesting. The responses, comments, analyses, fan works (there’s fic and art!! the dream!!), inspiration, and questions (like the ones prompting me to write this post-mortem) people have shared with me thanks to Mortholme… They’ve all truly been what I was hoping for back when I first gave myself emotions thinking about a mean megalomaniac and stubborn dipshit.

Thank you for reading, thank you for playing, and thank you for being around.

#so that got a bit verbose. you simply cannot give me this many salient questions and expect me otherwise tbh #the dark queen of mortholme #indie dev #game dev #dev log

89 notes · View notes

redgoldblue · 2 days ago

Text

so assuming Avery is actually pregnant / doesn't early-trimester miscarry (which is not a given), there's two reasonable ways this can go, right. number one is she gets an abortion, the plotline is used to pull them all back together again, and they all have some collective hurt/comfort about it. number two, the one i would write - don't get me wrong, i'm all for women getting career-driven abortions, but hear me out - is the one where she does have the baby. under the cut bc it got long.

she goes to med school at first while pregnant - Max is right, it can be done, people in my cohort did it - and either gets lucky with the timing of the actual birth being during holidays, or just works her way to getting time off for a few weeks around it. And then... there's a baby. And you know what else there is? There's two dads (because we're 100% Mamma Mia-ing this bitch. they never find out who the bio dad is and they never seriously try. Baby comes out with Avery's exact skin tone so that's no clue.), and an entire cruise ship worth of backup babysitters. So Avery goes back to med school, and leaves the baby with Tristan and Max.

And, yes, raising a baby while also running an infirmary with a rotating cast of temporary substitute nurses filling Avery's role isn't the easiest thing they've ever done, but Robert loves fulfilling grandparent duties any time he's not on duty; Rosie gets one of those strap-on baby carriers and walks her (i don't know why i've decided the baby is a her but i have now) around the engine room pointing out parts and explaining concepts and hey, the baby never complains about her Michigan stories; Corey gets a cart and a bundle of clean sheets and pushes her down the corridors until the smell of laundry powder automatically makes her start laughing.

Max and Tristan make a pact to send Avery at least two photos a day - which ends up getting supplemented by everyone else who's with Baby - and FaceTime her most days, and whenever she gets a few days off she meets them in port. (The most expensive part of baby-raising ends up being her flights to wherever the Odyssey happens to be at the time, at least until Robert finds out and figures out a way to start paying her 'maternity leave', despite her insistence that the whole point of this is that she isn't maternity-leaving and he should probably be paying himself that and anyway, isn't she technically not an employee right now?)

And the thing is, during this time, Max and Tristan start... realising some things. Like how neither of them feel like they've lost their only partner, because they.. haven't. Like how the co-parenting's been working out better than either of them expected, because they fell instantly (minus a few minor bumps) into a shared rhythm. Like how sometimes they look at the other one holding Baby and feel like their heart's about to explode.

Also, they've both started sleeping in Max's bed. Because Baby's spent so much time sleeping in the corner of the infirmary that now if she wakes up at night and can't see both of them, she starts crying inconsolably. And obviously Max's suite is more suited to multiple inhabitants, and they're usually too damn exhausted to even remember the first time they were in this bed together.

(usually. most of the time. and when they're not, they don't make it the other's problem)

So at the end of the first year of this, the last two days of the year's last cruise have been packed with crisis after crisis after demanding patient after crisis, and as soon as they finally wave the last passenger off they hand Baby gratefully over to Robert and go crash out in Max's bed.

Avery was supposed to be meeting them on board tomorrow, but her last exam gets unexpectedly moved up by a day (believe me, med school loves to pull that kind of shit on you), so a couple hours after the passengers have gone, she shows up to surprise them. And finds Robert (a known ody3 shipper) first, who lets her take Baby with minimal captainly sulking about it, and while she rocks and kisses Baby, tells her (as a known ody3 shipper) that the two dads will be on the Pelican deck, but they're probably asleep.

Avery kinda frowns at him, but doesn't question it, and takes Baby up with her to Max's suite to find them. And they are both fast asleep, on either side of Max's bed with a space carefully preserved between them (because it's usually where Baby would be and they're both terrified of accidentally rolling onto her in the middle of the night). She's also exhausted after exams, so she crawls into it, lies on her back with Baby on top of her chest, and goes straight to sleep.

Tristan and Max wake up before her, and when they look across at each other, at Avery and Baby between them, they both simultaneously realise, oh. oh. oh, this - this three, two-and-half, four people, all together - this is it. this is the love, this is the children, this might even be the home - the second, third, fourth bucket list items to happen in this bed.