Skip to main content

Treasures Of The Deep Dwellers: A Real Time Grid Based Roguelike?


Hello again!

It's been quite a while since I posted here. I've been working on other projects, and spending a lot more time with my family, but the core reason is that I just lost interest in the project as it stood.

But wait! I haven't given up. I just needed some time and some ideas to remake my vision in to something that:
A: I can finish.
and
B: Is actually fun.


So read on for the next chapter in the development hell of:

TREASURES OF THE DEEP DWELLERS!

 
This time last year I took a break from this project since it was wearing me down.

I realized I was making a game for me, with stuff that I liked. But which I would probably never play.


What I really wanted to do was capture some of the excitement and joy of playing an RPG / Roguelike for the first time...

And package that as something that modern players would actually find enjoyable.

So it's clearly time to start over.


 Where do I go from here then?
Well, one idea I had was for making the game real time, and grid based.
I've made two complete games lately using this system, so it seems to improve my productivity anyway. Everything is just so much simpler. 

But single tile grids give too much of a blocky feeling that real world players complained about. I decided to make the grids more granular.

So now a default agent takes up a 2x2 chunk of the grid. They still move one square at a time though. You can see the debug function showing which squares are occupied by the agent. I talked a little about how I did this in an earlier blog post

  
The system makes it easy to scale up agents to 3x3 or even 4x4. A giant spider, a dragon or daemon perhaps? This is something I've wanted in the game from the very beginning. Different size monsters really add a great deal to an RPG. If everyone is human sized it gets boring fast.

Pathfinding has also been greatly simplified. I found a nice form of dumb AI which makes for quite interesting encounters, as the characters spend behave more unpredictably. 
The basic premise is that monsters will try to get closer to a seen enemy and will not backtrack until they get stuck. It's like water running downhill. It just keeps draining down until it gets blocked and then it tries to find a way around. Eventually it can overflow and fill backwards.
The most important point is that it allows for a large number of agents working in real time with no noticeable logic drain. So it's great for a python based game.


You might wonder why I chose 2x2 as the default character size. Why not 1x1? Well I'm saving that size for smaller creatures, like rats or insects which can swarm through small gaps... You can imagine the small creatures darting in, making an attack and running away again. Better pack a crossbow on this adventure!

Overall the game is going to be simpler. It's aimed at teenagers or kids playing a classic RPG for the first time. I want to make it fun. I want the thrill of an arcade game with some of the deeper options of an RPG.

Essentially though I want to get it finished! I'm going to be focusing on game play and functionality. No more wasted time on graphics which I might or might not use! 
(Final last words of an artist!!)


Comments

Post a Comment

Popular posts from this blog

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.

Automating Level imports from Blender to Godot

  Recently I've been making some levels in Blender an importing them into Godot. There are only about 7 or 8 shaders for each level, not counting dynamic objects which will be added later. But to improve rendering performance, it can be a good idea to split the meshes up into sections. At that point you might be faced with a list like this: Or it might be even more chaotic, if you didn't use simple names for the objects in your level. So it can take a long time to sort out all the meshes, make them unique and add textures and so on. Blender imports with simple Blender textures, or with placeholder materials. This is sometimes OK, but if your Godot shaders are very different to those used by Blender, it means applying new materials to every mesh object in the level when you import the scene. I found that during the design process, I was importing and readying a level several times before I was happy with the final layout. So at first I was wasting a lot of time. In Blender, I us

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra