So I’m experimenting with scattering a handful of placeholder props and things around in sensible places, to make village huts and stuff feel a bit more lived in.

In towns, chests and enemies (and other NPCs) are going to try and spawn in houses rather than out in the streets and fields.

One major aspect I’m pushing with CQ2 is bringing a sense of geography and place into the mix. It’s still a way off that mark, and my temporary graphics shouldn’t be around for long… but the systems are getting there to support it, and that’s the main thing. 😀

Cardinal Quest’s tilemaps were pretty straightforward. Each 16×16 tile was a different image: wall, floor, door, stairs. The boundaries between tile types didn’t affect the graphics at all.

If we apply this approach to forests, we’d end up with Forest Tiles and Not Forest Tiles. Something like this (though obviously with better art):

That’d work, sure. But we can do better.

The approach I’ve decided to take is to stick with 16×16 tiles generally, but allow applying a variation to just a quarter of a tile – meaning the system can use 8×8 tiles where it counts.

Continue reading »

I’ve been working on a few new kinds of level for CQ2. The first is a forest to traipse through and kill things in. Forests are messy, confusing places! The main features in these forests are trees (that get in the way) and bushes (which you can’t see through). Your sight lines are pretty limited, except when you find the odd clearing, but there are plenty of opportunities for leaping out of the bushes and stabbing people.

Please excuse the placeholder graphics. It’s essentially grey boxing: I’m roughing the levels out with dumb coloured blocks to see what works and what doesn’t, and the pretty art comes later when we’ve settled on level features worth keeping. So for now, trees are solid orange blocks; bushes are mottled grey and orange; and the forest floor is grey.

You’ll just have to use your imagination a bit. Trust me, this is more forest-like than using the old tileset and having bricks everywhere!

Continue reading »

Fixing text layout issues is extra fun when you can’t actually read what you’re fixing!

Almost every single displayed string in Cardinal Quest is loaded from a text file. I wrote a tool to embed these text files in the source code, so the whole thing’s entirely self-contained as a .swf or .exe, but the game can also load the text files on the fly so we can modify strings and just relaunch the game to try new stuff faster.

All of this supports Unicode. Doing a translation has pretty much just involved sending off these text files to be translated.

The only real problems were fonts and layout. Cardinal Quest uses two different fonts throughout. The Japanese version, now, that uses a single font almost exclusively. It’s not like you can knock up a useful Japanese font easily or cheaply – a usable font would need thousands of glyphs! As a result, there aren’t nearly as many fonts around to pick from.

On the layout side, most of the text is only loosely framed by artwork around it. The font sizes of some stuff needed tweaking, but only really a handful of things in the UI. If you’re ever designing something which you think you’ll have translated later, just remember that tolerating a little whitespace around your text goes a long way. 🙂

I’ve been messing around with level generation. The big plan at the moment is to get various generators up and running – for things like dungeons, caves, towns, forests and so on – meaning that we can have a whole bunch of different-feeling levels. One of the core features of CQ2 is going to be a sense of place, a feeling that you’re carving a way through different areas on a journey and that there are new things to discover up ahead if you persevere.

First up was messing with a cave generator of Ido’s that was already in the codebase. I played around with the settings a bit and then, thinking of NetHack, tried pulling the view distance all the way in so it feels a bit darker and more threatening:

It certainly feels a bit different! (Ignore the tileset :D)

One thing I’ve realised is that, even with procedural generation like this, the different areas of any given level type tend to feel a bit bland due to being all pretty much the same. We’re going to need a range of level features, like special rooms and so on, so there are things to find when you explore. I’m not sure what to do on that front yet. I’ll work on it – I don’t just want to stick in shops and treasure rooms, though they might be part of the solution.

For now, I’m going back to raw level generation. These villages and forests aren’t going to make themselves!

Since the game was starting to come together okay, I put a version out to a few people for testing yesterday.

The main thing this found was a whole bunch of bugs – I broke mouse control entirely! However, another common point of feedback was that the Found Item dialog was confusing and a bit rubbish, like it not being obvious at a glance which is the new item and which is the old one.

All the clues are there – sort of – but it’s still something that took a while to interpret, and this is stuff you need to be able to parse in a split second. I’ve been revising it today and it’s now leaner and clearer:

It’s a pain in the arse redoing work you thought was done, but hey! If it’s broke, it needs to be fixed. Hopefully this version will playtest better or I might have to reconsider removing the inventory altogether.

Time to code it… again 🙂