Gruedorf Post 2021-04-11

• Figure out that I've been drawing maps to the wrong intended scale
• Figure out what the right scale is and how to draw them
• Start building out the first "dungeon" map

Maps

Maps! They're hard. I'm building them in a bit of a strange way.

Since I'm not building the final maps for the game at the moment, I am trying to develop a workflow that strikes a balance between a couple of points:

1. It has to be relatively fast
2. It has to be relatively easy to change
3. It has to be something that I can give to artists and they can understand it all well enough that they can see how to improve it (and hopefully enjoy it as-is)

I would normally just make some tiles and use tilemaps. That's something I pretty familiar with, but it turns out... I'm not actually very good at tile art. It takes me a long time and I fuss with it a lot. I could just use some coloured squares, but then I'm losing out on my third goal -- it's not clear what things are. I could FIND some tiles to use but I have a terrible problem that if I sit down to find "relatively good" tiles to work with, I end up looking for the PERFECT tiles. I also don't want to be constrained by what someone else decided to put into their tileset (and if I let myself start drawing my own tiles then we end up back at the beginning of this paragraph.)

While I'm not a great pixel artist, I am semi-competent with a pencil. All of the art you see in the game so far (in earlier posts) has been drawn by me (I primarly use a Huion tablet and Clip Studio). So I've also been pencilling the maps.

This COULD lead to a lot of terrible waste. The first part of the game is set in a forest, so rather than signing myself up to spend the next ten years of my life drawing trees (though I'm sure I'd be quite good at drawing trees by the end), and to avoid having to fight with pasting things in the right order, I'm still using a "tile" engine internally. Godot's Tilemaps, to be exact.

The other problem with pencilling something is that it is very easy to focus on one thing and ignore the larger picture. With tiles this is kind of okay (most of the time) because you're focusing on some details in a tile and then piecing together the larger picture late. If you're actually producing a map's layout and its "pencils" in one go, though, this isn't good. It's a work in progress, but I've been gradually refining the process...

The Process

First, I start in Clip Studio. I've got a file where I am drawing the entire game (well, it WILL be the entire game eventually) in one big image, with blocky pixels. It's drawing at roughly a one-fifth scale, and it looks kind of like this:

As you can see it is very light on details. I'm doing some mental planning as I work on this, and have some references within other documents (mostly in Google Drive so I can peck something into them from my phone if I come up with an idea while I'm not at my computer), but they're quite messy. The grid is a grid overlaid by Clip Studio and it is very very roughly set at about one tile per square.

Since I have all of the maps in the one image, I can also make sure that they line up and roughly fit with each other. This is important to basically no one in the world other than me, but I like that I can do it.

When I decide to move further with a map, I make a new image that is 1:1 full size for that map, and I clip out the section I'm working on from the big "complete game" image, and blow it up to the right size. Then I start pencilling in the shape of the map over it.

I actually work with the rough map more transparent than in the image, but I upped the opacity so it was more obvious. I'm drawing in red because there is a psychological effect that black lines seem more "finished" (or so I've heard), and I want this to feel like a draft. It's just a pencil drawing, so it's not set in stone.

You'll notice that there are some features drawn on the map, but I mentioned this is supposed to be a forest. There are no trees! Earlier in development, I pulled out three sizes of trees (cleverly named "small", "medium", and "large"), and I've divided them into the "below the player" and "above the player" parts. It turns out that Godot's Tilemaps have a very loose definition of what a "tile" is. It can be any image -- whether or not it's the supposed size of the tile. This means I can just treat my two pieces of tree as tiles on two layers.

So I import my pencilled map into Godot, and then start dropping in the reusable parts like the trees. If they are thing that should exist on the same layer as the player (e.g. a barrel that you can both walk in front of or behind) then I have a separate "entity" layer for them.

The last step to make it useful is to put in the obstructions. I use CollisionPolygon2D instances for this, which Godot has native editing support for. It makes things very colorful.

Then I run the game and wander around to see if I messed anything up! (Spoiler: I usually did.)

Going Forward

I've got a lot of map drawing ahead of me. I'm not really entirely sure about this process yet; I'm worried it's not quite fast enough. This won't necessarily make for very exciting Gruedorf posts!

But that aside, my next several weeks will probably be a bit constrained anyway. My wife and I are gearing up to move in the while, so we're doing the whole finding-an-apartment-and-packing-everything-we-own thing. I'm going to do my best to still post on Sundays, but I probably won't take the time to ramble nearly as much.

Gruedorf Post 2021-04-04

• Rewrote how energy is used to power skills
• Made it possible to use skills outside of combat

Energy

I'm using the term "energy" in place of what you might more traditionally see as "MP" or similar in a jRPG. It's a small thing, but magic is not as plentiful in the world that Black Mountain is set as you generally see in the most RPGs; most people in the world (including characters in your party) do not have a great deal of experience with magic, and are much more likely to encounter it in the form of lightly-enchanted items than to be wizards themselves. I mentioned last week that the main character is a healer -- I mean this in the traditional sense, not a magical one. She doesn't have any magical healing ability, and such a thing is quite rare. (I actually hope to explore that, and the tension between traditional healing and magical healing (and the practitioners of the two) in more detail some day in Geas!) Anyway, point is: "energy" is a more general idea than a "mana" pool or something similar, it just represents the character expending internal reserves before they're exhausted, meaning it will be used for skills and powers that are not actually magical in addition to "casting spells".

Along with that, like any good epic fantasy hero, the characters have the option to overdraw themselves. You can continue to use skills even if your energy is depleted; you will start using your own health, instead. This could be dangerous but it might be a worthwhile tradeoff in the moment.

Right now, of course, there's the issue that using a simple First Aid skill causes less damage than it heals. I'll have to fix that, and I'm not exactly sure how yet; either I'll fiddle with the numbers and ratios so that isn't possible, or some skills will not be usable by burning life points. We'll see.

Interfaces

I've also finished up the interface work I started last time.

"Attributes" shows the characters stats and a list of any passive skills they have unlocked. Because of the complex and time-consuming nature of magic, a student of magic like Violet will not generally gain access to new and more powerful spells simply by levelling up -- the spells will be part of equipment, usually as gems/runestones/whatever that socket into a weapon, which anyone can use. Instead, someone with actual knowledge of magic will be better at using those spells, casting them better and more safely than others.

"Skills" is now a list of all skills the character has available. They're greyed out if they're combat-only skills, and they're red (not pictured) if using them would damage the character.

There were also changes within combat (including the ability to use ANY skill even if doing so will outright KO the character, just in case an old man ever needs to cast Meteo...), and I realized that I haven't really talked much about combat yet. It's actually in there, already; I built most of it before I started posting about the game. It's got some issues, though, and some things to work out, so I'll probably just try to dedicate a post to it in the future.

Moving On

With this sorted out, and a few last ideas that I've moved to the "maybe for a future game" category, I've actually sketched out the alpha/playtest version of all the mechanical building blocks of the game. I've got lots of bugs and other things to address, and I'll definitely need to build some more pieces as I figure out what I need, but I'm going to basically be shifting gears going forward to focus on building out the "draft" version of the game.

In my head (and in my notes) I have a handful of milestones that I've mapped out. Hitting this point is sort of a mini-milestone, I suppose, but the real first milestone is what I'm referring to as a "draft" (or version 0.1). It's going to have placeholder art, questionable UI, mediocre writing, and lots of bugs, but it will be the main story beats of the whole game, beginning to end. The point of the draft is to get it to a place that someone else can actually play the game all the way through and actually understand it as a game (and hopefully even enjoy it at least a little) with a minimal amount of me waving my hands and explaining things that there yet. Hopefully I'll be able to use this version to bring some other people on board to help me, especially with art. We'll see.

For what it's worth, this process might be a horrible idea, and I don't necessarily recommend anyone else follow it! I also know it's pretty unusual for how a game is normally built. A much more usual flow would be to build a very short slice of the game, polished to somewhere close to the "real" version of it, and use that to get a publisher on board or something like that. In this case, I have a reasonably clear(ish) idea of what I want from the game, and it's a passion project. I'm not really concerned with finding a publisher ASAP, but I do want to work with other people on it. It felt like the right course forward, then, was to focus first on getting the basic framework nailed down and the whole game sketched out so my vision is (hopefully) clear. It'll be interesting to find out if it works out as well as I want it to.

Gruedorf Post 2021-03-28

• Brainstormed about how I want to handle skills
• Start implementing that

Brainstorming

I wrote some last week about the trouble I'd been having with deciding how I wanted skills etc to work. I waffled a lot, and eventually started building pros and cons lists for various approaches. I ultimately ended up going with a fairly traditional route, and deferred a lot of the more unusual ideas I had for future games. I certainly could change my mind, but for now I at least have a way forward.

And Finally, Progress

I spent basically all week reaching the decision and finally came to it today. So I started implementing SOMETHING so at least I'd have a little to show off.

I've had a "Status" section in the menu just kind of hanging around with debug information in it. I wasn't really sure what to do with it, but I realized that I could finally put it to use. The status section will have three (for now?) sections in it: the default info section, the "spend XP" section, and the attributes section. I may actually move these around and change what the default is, but that's going to need some playtesting to figure out how these actually flow in practice.

The info section is pretty straightforward -- it shows you info about the character. I'm undecided exactly what I'll put here, but I've written a couple sentences of backstory for each character. I may add more random "demographic" information here, or I may add other interesting stuff. Not really sure yet.

Spend XP is where you'll be "levelling up" your characters. There isn't a traditional level system in Black Mountain; instead you use XP to buy skills and passive upgrades and such. It isn't displayed super well at the moment, but there's a hierarchy of upgrades you can buy, as well as levels of each. The available trees of upgrades depend on the character's available classes and equipment. I had actually built this interface a while back, but it lived under "Skills". I've moved it here, though, and will repurpose the Skills section into where you actually use your skills outside of combat.

Speaking of skills based on equipment, as I rambled about on twitter a while back, Black Mountain and later games will not have the standard jRPG equipment "treadmill". I wanted to avoid the classic jRPG silliness of "Here is this amazing legendary sword! ... That you will sell to a merchant in two hours because the sword you bought at a merchant in the next town is better", and strive for something a little more in line with epic fantasy books. A characters' core equipment will be a part of them, and will grow along with them -- changing equipment will happen only very infrequently, and usually as an "upgrade" to an existing piece of equipment or as an expansion of options, rather than replacing them. In Black Mountain, for instance, Kiel uses the sword that her father left behind when he died; it would be ridiculous for her to just toss it aside partway through the journey. Since the equipment is more-or-less fixed (or, in later games, a very small pool), it functions partly as the character's "class", and so the character will have skills associated with that particular weapon. (Coincidentally this also happens to mean that I don't have to worry about inconsistent art for different weapons.)

The last section, Attributes, isn't done yet. It's where I'll show the character's stats, but I haven't started work on it yet, so no screenshot. I'm considering switching this to be the default screen, rather than the info section, since the info section will be (relatively?) unchanging, while Attributes may have things the player wants to check on every now and then.

At Least I'm Moving Forward Again

The last two weeks haven't been great, but I'm glad to have made a choice. Hopefully I'll be back to my usual productivity next weekend.

Gruedorf Post 2021-03-21

• Made a liftable block
• Changed my mind about how some things should be implemented
• Fixed liftable to fit the new way
• Angrily stared at some docs and my todo list, a lot

Lifting Blocks

To go along with pushing and pulling things, you can also now lift them, and then put them down.

The "liftable" entities play a quick lifting movement animation, which will eventually be accompanied by an animation from the character, and have the player character lift up their arms, but that's for later. When the character puts the pot down, it triggers floor switches just like a pushable block.

Changing My Mind

Pretty much immediately after getting liftable entities working, I realized that I wanted to implement them in a different way that is more flexible. There was something more pressing to work on, and they worked! So I decided to move on.

But then, once I actually confronted the next thing to work on (see below), I decided to switch back to it and see how well the different implementation worked, and whether it was a lot of work. If it worked out, then I'd probably want to make the same change for pullable/pushables. And it did work out! I haven't made the change to pullable/pushable blocks yet, but I will. I decided I needed to stop putting off the bigger decisions I needed to make.

Decisions

So far I've been implementing a lot of stuff that I'd already decided on, or seemed obvious to me -- things like how equipment would work, or just basic navigating around a map. I'm starting to run out of the obvious things, and a big core part of the design that I've been been putting off is now an impediment to getting more done.

Black Mountain is intended to be the first in a series of games. As such, I'm building as much as I can with an eye toward re-use in the future. I am not making myself build everything I might ever want in Geas, but I am trying to at least work in that direction. Part of what I want is to have a world that's a little more reactive than your average jRPG; rather than just invisible monsters, things that wait around to have a button clicked at them, and the ability to script some cutscenes, I want the world to have a bit of logic and physics to how the player interacts with it.

This is what's been driving my attempts to let you maneuver gaps and cliffs naturally, pick things up, push things around, etc. Some of the things I've got planned for the bigger picture I have intentionally put off for this game, which is fine, I can fill them in later.

What I need to actually figure out, though, is whether there are items and skills that the player has that they use out "on the field". Think of tools like the hookshot or the hammer in Zelda; they can be used as weapons, certainly, but they add specific and meaningful ways to traverse and manipulate the world. I don't have a clear vision for how I want this part to work; either what tools and skills I want available to the player outside of combat, how different characters and equipment play into it, or even whether I even want to deal with them at all. Once I decide that, I can probably figure out a reasonable stripped down version for Black Mountain, but without a strong guiding idea I've been floundering a bit trying to figure out how to begin figuring it out.

After a few days, I am making slow progress on the decision, so I'm not completely stuck at least. I'm currently mapping out the choices I have to make, what options I could choose, and working out the implications of said choices. What I decide will end up tightly intertwined with building maps, combats, and the general minute-to-minute tension of the game, so I want to at least come up with something that feels right on paper, even if it has to change later.

Gruedorf Post 2021-03-14

• Added wall climbing
• Added block pulling
• Made a floor switch that clicks down when the player steps on it or puts a block on it
• Added push/pullable block constraints
• Broke wall climbing somehow
• Fixed wall climbing

Unfortunately screenshots don't demonstrate most of these super well, but I'll do what I can.

Wall Climbing

I can now define an area as climbable. If you push against the top or bottom of it, you'll switch to climbing mode (which currently does not have different art) and you will be able to climb around on the surface. It's a bit jittery and weird and I haven't fully put it through its paces so I'll have to revisit it at some point, but it's working for now.

Block Pulling

I'm not making a sokoban game. I don't necessarily want or need to derive a lot of difficulty from constraining exactly how the player can move blocks around, so some (most?) of the time I'm going to want to allow them to pull blocks when they're able to push them. This will cut down on the possibility for the player to get stuck on puzzles; it'll also severely curtail the actual allowable difficulty for the puzzles, so it's something I can toggle individually for a block.

While I was at it I also made it so you can toggle pushability as well, so I can have pull-only blocks. The screenshot may be a little hard to parse, but that block has a sort of debug-graphics black bar that stretches into the wall; when you let go of it, the whole thing will slowly retract back into the wall.

Floor Switch

Having step events (as described last post) isn't new, so this isn't that novel, but it's got a satisfying click to it when you step on it, and it visually changes to show it's depressed. More importantly, the block can also push it down (but it's even harder to get a meaningful screenshot of that than it was with the player stand-in sprite).

Block Constraints

I am able to add solid obstructions to a pushable block that constrains it from moving. These constraints are in addition to any normal solid walls, but they don't block the player (or any other entity) from moving around. The dark polygons on the ground below both blocks in the above screenshots are just visible polygons to help me ensure they're working correctly, the space constraint obstructions are normally invisible.

That's All!

That's it for this week. After the debacle of last week's collision stuff (and the knowledge (which turned out to be correct) that I would have to delve back into it a bit for this stuff), I kind of dragged my feet on getting into it this week. I've got a few more map-interaction "primitives" like this stuff that I need to build, and a few that are on my "maybe" list, and then I'm mostly left with a few small features, a bug list, and "actually building out the story". I'm looking forward to getting to that part.[0_1615760291123_climbing.mp4](Uploading 100%)

Gruedorf Post 2021-03-07

• Finished cliff hopping
• Added gap jumping
• Added block pushing
• Added blocks being pushed off cliff kind of
• Broke everything, rewrote collision handling/movement code
• Shouted my frustration at the cold, uncaring universe

Different Events

There are two classic, straight-forward styles of events in RPGs: I call them "step events" and "triggers".

Step events are your classic events (like Verge's zones) where when the character enters the event area, some sort of effect happens. This is good for map boundaries, stair cases, triggering cut scenes when the player character steps in a particular place, etc. (Technically my step events have some configuration which mean I can differentiate between events that I want to happen when the character just touches the edge of the event area, or if their center-point has to be inside of it; which one I use will depend on how I want to tie it to the visuals of the world.)

A trigger is something where the character must face the event area, and press a button to trigger it. These are often solid (though they don't necessarily have to be), and are used to model doors, switches, people to talk to, soemthing interesting lying on the ground, etc. They're something that the player is choosing to interact with directly, by pressing a button, rather than something that just sort of happens to them because they stepped in the right (or wrong) place.

I decided to add a third event that seems to be most prevalent in Zelda games, that I'm calling a "push event". The push event has to be solid, and when you bump into it at first it acts just like a wall. After you continue pressing against it, though, then I run the event code. It's not rocket science, but it gives me some fun things I can do with it, like requiring you to commit to jumping off of a cliff before actually doing it, or adding weight to blocks you can push -- things that are in between just moving around and intentional interaction. They can keep moving through the world with only a brief interruption but also where they won't just be flinging themselves off of cliffs or kicking boxes out of the way just because they stepped a touch too close.

So, with that I have a couple of things working now...

Hopping Off of Cliffs

I mentioned this last week, but it's finished now. When you push against the top of the cliff polygon, it figures out where the bottom is and plays an animation of you hopping down. Right now the height can be arbitrarily tall, but it wouldn't be difficult to add a check for height if I wanted to. If you push against any part of the cliff that doesn't have a "bottom" below it (e.g. the bottom of the cliff) it ignores the push and just treats it as a wall.

Jumping Over Gaps

Similar to cliff jumping, you can also define a "gap" that can be jumped. Rather than jumping vertically to the bottom, it projects across the area instead and jumps you to the other side if it's close enough. Similar to the cliff height caveat, the jumpable gap size is currently fixed (to one tile) but could be modified by an item or skill or whatever in the game.

Pushing Blocks

Entities can also be set up to receive pushes, and they work like a push event but can also be moved by the event handling. I haven't tried it yet, but these could be set up to trigger (some) events when moving, so it should be pretty straightforward to make the classic "push a block onto a floor switch" kind of puzzle! I just need to make sure I don't inadvertently create the "push a block out of the map and it's gone forever" kind of puzzle. I could probably leverage this for general NPCs; there's nothing more annoying than a villager standing in the way and you just kind of have to wait for them to decide to wander out of the way.

Pushing Blocks... Off of Cliffs

I said that I haven't tried to set up a block "stepping" on a button yet, but I wanted to immediately tackle having blocks that are being pushed trigger other push events -- specifically to have them trigger a cliff jump. It actually just kind of worked once I got everything hooked up! Except when it didn't.

Sometimes, the push just wouldn't register with the cliff. The player kept being able to trigger it, but the block was inconsistent. I narrowed it down a little -- it seemed like the more "flat" the cliff edge was to the block, the less likely it was to trigger the event. It seemed like the issue was rooted in using Godot's move_and_slide(), a built-in function for kinematic physics bodies which produces (close-ish to) the kind of movement I wanted out of the box... except that it for some reason it was now causing issues.

Rewriting Collision, Again

I hate writing collision and movement code. When I was building SimpleQuest I actually just kind of stopped working on it for weeks (maybe months) when I hit this wall. I didn't want to ruin my streak of work so I just plowed in. Thankfully, things are a bit easier for me this time. But not much.

It turns out move_and_slide() is a wrapper around a lower-level movement function, move_and_collide(). I didn't especially want to write all of my own collision detection code (since it would be an enormous waste and of time and it would almost certainly be slower than using the built-in facilities, and most importantly it came with the risk of just killing my forward momentum entirely) so realizing there was a lower-level thing to fall back to was a relief. I just need to deal with the collision resolution, not the detection.

So I re-wrote the resolution. Unfortunately, push events and push events triggered by pushed objects present a lot of issues. In particular, the sliding block will begin colliding with the player first, when squeezed between the player and a push event. This means the push event never really gets the collisions. I suspect this is what was happening internally within move_and_slide() as well. Maybe! Who knows?!

Anyway it was very frustrating but after a few hours of trial and error and reams of debug logging, I think I have it mostly working now. I'm sure I will (unfortunately) have to revisit it some day (I already know it's not working exactly how I'd like), but at least it's kind of there now, and I can move on to the next thing. Hopefully next week will be smoother sailing.

Gruedorf Post 2021-02-28

• Can now add water polygons to the map
• Set up z-indexing so I can have multi-part entities that sort correctly
• Built a "follower" system for having party members on map, but commented it out
• Can now add shadow polygons to the map
• Drop shadows on character entities are not part of the sprite now, they're an actual shadow
• Started work on hopping off cliffs

Water Polygons

While Black Mountain is a relatively low resolution game and the end result will probably be mostly pixel art, I am not trying to mimic any particular old hardware, nor am I holding myself to any sort of purity test. I am doing my best to avoid actual mixed resolution (because I personally hate it), but I am not going to avoid using modern conveniences like shaders or polygons to do things. The water can be added to a map similar to an entity, but by drawing out a polygon (which Godot's built-in tools make pretty easy). It is animated, rippling slowly and wobbling the underlying tiles of the background, and I am able to give it a direction for the movement so I should be able to use it for (slow-moving) rivers as well.

Multi-part entities

One thing that I always find annoying with making maps is dealing with thin upright pieces -- things that you want the character's head to render in front of when they're standing in front of them, and you want the character's feet to render behind them when they're standing behind them. To make this easier on myself I actually have a lot of "placeables", which are basically furniture, and are just entities like the character sprites. I put them in with the sprites on the map layer and they get sorted appropriately.

Unfortunately, this means that you have to be careful with exactly how it's drawn. Every entity has an origin -- for the character it's the space right between their feet. The origin is the y-position used to determine render order. If the character's origin is higher on the screen than the placeable's origin, it gets rendered behind. If it's lower, it gets rendered in front.

But what about things like rubble strewn on the ground? A treasure chest with coins spilling out of it? This is fine as long as the "floor" layer of the sprite is entirely contained to below its origin, but that's not always the case, and when that happens you end up with rocks, seemingly lying on the ground, floating on top of the player when they walk there.

To allow for this, entities can now have other parts. Godot has a built in z-index system that gives you an extra means of control over the render sorting that's happening. It's a little bit brittle; it'd be easy to make something draw entirely wrong. If I were worried about other people using this I would probably try to do something about it, but if I shoot myself in my own foot, well, I know who to blame.

Shadow Polygons

I feel like any game where you can see the ground beneath the feet of the character benefits from having a drop shadow. I had a drop shadow under the character before, but it was just a hand-sketched partially transparent circle.

The problem with partially transparent things, of course, is that when they overlap, you get a darker spot. This is fine for Venn diagrams but not so much for shadows. So to fix that, I added a shadow layer to my maps.

The shadow layer can have shadows added to it by an entity that lives on the map (or is placed there), and it can also just have shadows added directly to it by the map maker. It works by drawing all of the shadow polygons to a separate surface, and then drawing that surface all at once with transparency. As you can see in the screenshot, the shadows lie underneath the sprites and on top of the background layer of tiles... but it is underneath the foreground layer of tiles. The real assets for the game are going to have to be constructed to deal with this; I'm not exactly sure how I'll do it but I'm confident I'll figure it out and that's good enough for this stage of development. Also for the future is to figure out the best way to make them softer-edged.

Because it was easy, I also added a way to look up if an entity is currently standing in a shadow (other than their own). If they are, I draw them darker too.

Showing Followers on the Map

I always go back and forth on how I feel about having the rest of the party shown on the map as you explore. I could do the classic thing where everybody marches in a line that perfectly follows the leader, but I don't feel like that would fit with Black Mountain. I put a bit of time into testing something where there are other sprites on the map and they try to catch up to you, but I didn't really care to make the pathfinding work correctly so they just kind of got hung up on things (I'm fine with monsters getting hung up on things, since it means the player can be clever and escape from them... it's less great when your party members are too dumb to walk around a tree to catch up to you). I also realized that having them on the map complicates some of the things I'd like to add later... so I turned them back off. I've still got the code so you never know, they might come back, but for now you're just driving the leader around the map.

Hopping Off of Things

One of the things I'd like is for Black Mountain to be a game that feels better to move around in, and involves the characters doing things outside of combat on the map. This is driving a few of my core decisions about the game, and in a sense it's pushing it a bit away from your traditional jRPGs towards an action RPG -- getting a little Zelda in my Final Fantasy, if you will.

To that end, I'm going to be adding some of the staples of more action-oriented RPGs. The first was to add the ability to jump down off of cliffs. The intent of doing this is actually what drove the shadow separation work I rambled about above (along with wanting to deal with the overlapping polygons), so that I could lift the player sprite up off of their shadow to make it seem like they are falling or hovering.

This isn't quite done. I have the hop and the fall, the shadow separation, etc working, but I'm stuck on the nitty-gritty of figuring out exactly where the character needs to land when they jump off. I know roughly what I want to do, I just need to make sure that the plan doesn't wind up with the character stuck in a wall or being annoying to set up. Since I'm largely ignoring the grid for a lot of Black Mountain, I can't just cheat by saying "jump down by 3 tiles".

That's it for now! It was actually a pretty productive week, all things considered, even though it felt like a bit of a slog at times. See you next week!

Gruedorf Post 2021-02-21

THIS again.

I've actually been pretty diligent about development for a while now (despite all of the... everything). This year, I've resolved to start being more vocal about what I'm up to, so I can try to build some momentum for an eventual release, and I've started by doing biweekly #screenshotsaturday posts on my Twitter account, https://twitter.com/shamuspeveril. After seeing a bunch of people posting here, I figured I'd join in. I'm trying to be protective of my time so that I don't just end up spending all my time talking about the game instead of making it, but here I am for now. I'm going to be a bit indulgent of my rambling side in this first post; later posts should be more focused.

So, what am I working on?

Ancient History

Let's start way back in the halcyon days of early 2004. I was feeling the game-making itch again. I decided to look up this old game engine I'd spent a lot of time chatting about and messing around with (and accomplishing very little) years before - Verge! I happened to load it up just a short bit after vecna had made an update saying that Verge 3 was right around the corner. Exciting! What a great time to dive back in!

Journey to Black Mountain

When V3 did actually release a month or so later, we all had a compo (known these days as "a game jam") to celebrate the release and do some bug-finding. In a week, I built (with my then-girlfriend-now-wife, tulokyn) a small game, Journey to Black Mountain. It was about Kiel, a young healer, setting out to find a rare healing component to help her friend's sister. It was pretty rough. It was basically a 2d walking simulator with some light puzzles, well before that genre was anything close to established or respected. It didn't look great, but it had some interesting ideas (at least so I thought) and I liked the characters.

Geas

A few months later, mid-2004, there was another compo, but this time we had two weeks. I wanted to do something about the further adventures of Kiel and her friends, so I came up with another story about them, set five years later. With twice as much time, I obviously planned roughly 10 times as much game, and it went about as well as you expect. We got something submitted but it was very, very far short of what I wanted to do. There were rudimentary bits of the game in there -- a combat system, a shop system -- but it wasn't anything remotely complete.

Post-compo Development

After the compo, I did not want to let it go. I liked the characters, and I liked the idea. Worse (?), I had some MORE ideas. I decided I'd keep working on it, and if I'm going to keep working on it, why not expand it into a full game? Why be beholden to the idea I had for a two week game jam? So I kept working on it, developing the systems further and further. I also expanded the story; the original game idea became the first chapter of seven, four playable characters became twelve, and the world ballooned in size (though I will say that I kept myself to a relatively "manageable" world size; the game was contained mostly within a few relatively small kingdoms which I wanted to make fairly dense and interesting, rather than spanning a whole planet with exactly six towns on it).

I released a tech demo of this version in late 2004, and generated some mild excitement!

Rewrite

Unfortunately I started to hate it. As I worked, I got better at coding and art and wanted to bring it up to speed. I brought some people onboard to help me, and as is the way with things, they drifted away. Verge3 got the ability to use Lua instead of VergeC for scripting, and it's just a much nicer language to work in. Rather than convert everything, I started over from scratch; according to file dates I think it looks like I started new sprites in mid-2006. I drew new sprites and new tiles, made new maps. I ported over some of the systems and rebuilt others. At this point I started numbering my attempts at Geas, optimistically starting with "01", so just in case I hit my 10th rewrite the directories would still sort correctly. This version looked nice, I still think it does. I worked on this for a couple of years, until some time in 2008. I sat down and worked out that at my current rate of work, it would take me dozens of years to finish.

Cutbacks

That was more than a little disheartening. I decided to change tack, and mercilessly cut huge swaths of what I'd added. I didn't want to go back to the single "first chapter" idea, because I'd thought too much about the rest of the world, but I cut back the seven chapters to three, and the twelve playable characters to only five, and you'd only ever have access to four at once. The broad strokes of much of the story was there, but I cut out a lot of the later parts of it (which, conveniently, were also the least fleshed out anyway). I cut back the resolution to my old friend 320x240, and started over again.

This was version was what I posted about primarily when I was doing Gruedorf the first time. I made some decent headway, and worked on it until some time in 2010. As with the other versions, though, work on it (along with Gruedorf participation across the board) kind of petered out. Other projects, and other life things, started taking up more of my time.

It's Just Sleeping

It stayed dormant for a long time. It never really left my thoughts, really, but I wasn't actively working on it. It was always something I would do in the future, when the time was right. One of the things that I decided wasn't right for it, anymore, was Verge. Like Geas, it had dried up and development on it basically ceased. There were enough eccentricities and problems with it that I didn't want to go back to it. I started investigating other things, with the idea that I would eventually get to it.

I tried a few engines, I built a few, even. The most recent was Cozy, a web-technology-based engine. It owes a lot to Verge, really, both in the way I structured things, and many of the things I made them the way they are because I wanted to fix a problem I'd always had with Verge. I built SimpleQuest in that engine, but in the back of my mind what I was building was the Engine That Would Be Used For Geas. I built it, and I released SimpleQuest.

I'd poured a lot of time into building Cozy into the engine I wanted to use for Geas, and I love a lot about the engine. Once SQ was out and done, though, I took some time to really look at it, and see if it fit what I wanted for Geas, and I decided that it didn't. I was also sick of spending time building engines; looking at Cozy, I saw years of tinkering and tweaking and support, not jumping into more games. That's why it's on hiatus, and hasn't been touched in some time.

I learned a lot building Cozy, though, including what parts of making the game I enjoy and am good at and can do quickly, and which parts I fail at one of those. It also helped me realize that I just do not want to build my own engine. It's not that I can't (obviously), it's just not where I find joy in making games. So I went back to looking at engines. I made myself pro-and-con lists for various engines. There were strong contenders, and I started building prototypes, but I ultimately settled on Godot. It's not perfect, but it's the best fit I've found so far.

So, back to Geas!

Well... not quite.

What

When I decided to work with Godot, I built an RPG prototype. A little dungeon-y thing that had no real "game" or "story" to it, just a map that had the various things you might do in a Zelda-style game in it. I was satisfied that I could build an RPG in it, and would be reasonably happy doing that. And then I built something else.

I was still looking for excuses not to start on Geas. At this point, there'd been 15+ years of thought and work building it up into a Very Big Thing, and so I looked for reasons not to start on it. Last September, though, in a conversation with friends I realized what I was doing, and I decided it was time to just stop. To stop looking for a reason to avoid it, to look for other unrelated games to make first, and to make a real step towards it.

First thing was to finally document some things. I've been holding a lot about Geas in my head, and not keeping it written down. Don't be like me, kids. I know have the majority of the plot and other ideas I've had kicking around written down (unless I forgot them, in which case they are lost to time).

One of the thoughts I'd had in the years about Geas is that Journey to Black Mountain, the initial game, is actually pretty important to the overall character arcs of many of the main characters. The further Geas got from "the next compo game I made" the more it seemed important to make that story accessible in some way other than digging an ancient Verge game out of the archives. I toyed with the idea of making it a small game-within-a-game as a flashback, or something like that.

I decided that, to really make progress toward Geas, I would start with remaking Journey to Black Mountain. I'm keeping the setting, the characters, and the overall point of the plot from the original and throwing out the rest. I'm using this as a way to build a "chapter" of the larger story, and I'll release it as its own thing. The idea is to cement my understanding of the engine, build myself a library of code and art to lay the foundations for Geas, and to get something out there so I can tweak the foundation so Geas has the best shot it can get.

Black Mountain

So to that end, I'm now building Black Mountain, a complete rewrite and rebuild of the original Journey to Black Mountain story.

I'm working with placeholder art now, that I'm making entirely myself. Current goal is to get a complete end-to-end "draft" version of the game done as quickly as possible, and then figure out how to polish it into a real game. Future plans include potentially another "prequel" game, and then Geas, broken up into chapters and released as such. I'm not entirely decided on whether I'll keep a stripped down version of it, or go back to the full thing, but I'm leaning toward the latter at the moment. For now, I'm focusing on making Black Mountain stand on its own and to learn as much as possible from it.

At this point, I actually have a lot of the foundational programming work done. Godot does a lot for you but it's still a generic game engine, so I've been focusing on building all the parts I'll want -- maps, exploration, combat, items, equipment, shops, skills, etc etc. It's pretty close to a real game. I have a bug list as long as my arm (and that's WITHOUT extensive playtesting with others) and a few core things left to figure out (and procrastinating on those is why I'm here writing my Geas auto-biography). Once I get those sorted out, it'll be full steam ahead on the draft assets and writing.

See you in a week, maybe.

The site was dead and now it's not! Thanks, Grue.

Hey, Silencer. It looks like you CAN download it from the old site archive...

https://archive.verge-rpg.com/downloads/view/232.html

Just right-click on the Download button and Save As -- it thinks it's an "index.html", but that's actually a zip file. Rename it to aol_chronicles.zip (or whatever), and it seems to open okay.

I haven't tried to run it yet (on the wrong computer right now!) but it does unzip properly.