Skip to main content

7DRL fail.

So close to being finished, but I don't think I'm going to beat the deadline.

I still have to do enemy attacks and put in the code for switching levels, but there's just not any time left. :(

I'd also have to do something about packaging it for people to play and getting people to test it to make sure it works.

Anyway, next year 'll give it a try again. I learned a lot and I'm sure I'll have a lot of useful stuff to put in to the mix next time, and so won't have to write so much from scratch.

The biggest drain on time has been testing everything and clearing bugs. It didn't leave much time for actual design, and like 70% of features didn't make it past the coding stage.

Stuff that i wanted to work on (parts of the code were there but not working):
Hacking, some drones have a hacking module making them able to activate repair booths or damage nearby enemies from a range.
Stealth, some enemies and player units should have stealth, making them invisible.
Weapon stats. Right now every weapon is 100% accurate and just blazes away at the enemy armour. I wanted so much more including hit location tables, ranged attacks and accuracy.
map nodes and AI nodes. Some computer booths where supposed to have a special effect if you activate them with a hacker, such as revealing the level map, or making every enemy drone inactive.

Here's a picture of the final result in all its not finished glory:
It was fun to join the competition anyway, I got a lot out of it and learned some stuff that's going to be really useful when working on my main project again.
Labels:

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.
6 comments
Read more

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...
3 comments
Read more

The basics of A Star Pathfinding

Someone wanted to know how the code works for basic A* path-finding. Rather than reply in Facebook, I've made a quick post for it here. 1. create an array of nodes to represent your level.  It can be nodes with connections, or it can be a list of co-ordinates where connections are assumed to be NESW where a node exists.   Example 1:   level = {"001":[["002", 5.0], ["003", 5.0]], "002":[["001", 5.0], ["003", 5.0]], "003":[["002", 5.0], ["001", 5.0]]}    This is a dictionary based "mesh" type array, for easy reading. You can see it has 3 nodes arranged in a triangle. Each node is connected to two others, and in this case, the distance between each is 5.0 units.    It's easy to see how this mesh could be expanded. You just need more points. Each point must include its two neighbors and the distance between them.   Example 2:   level = [[0,1,1,0], [0,0,1,1], [1,1,1,0], [1,0,0,0...
Post a Comment
Read more