Untitled

So, a little late for this but I hooked up the first bit of the actual game-play before work this morning and I now have a movable hero character. It was an exciting moment after a few weeks of laying ground work and so I wanted to share.

Why am I making a rougelike?

I'm a novice programmer using this as a way to practice and learn about C#. It's intended to compliment training I'm doing via work so I'm going with OOP and taking pages out of the MVC book. I'm using Unity, even if it naturally runs a bit counter to the approach, because I'm already familiar with it to some degree and I have other prototypes and project I want to / am using it for.

What's it's about?

I'm trying to keep the scope reasonable for the moment so I'm aiming for a classic structure of going down dungeon floors. I want a quick and relatively casual game over all for this first attempt so not aiming for anything too fancy other than maybe some destructible terrain and a time limit on levels before a mod horde starts spawning. This is narratively an Orc invasion of a dwarven mine as the player is forced down through the mine, and an old dwarven ruins, in an attempt to find a way out. My data structure naturally eneded

Where is it up to?

I've got the basics of the data structures in place, tiles in a world which can contain either Static Objects, Items, or a character. I've got sprite controllers that listen to events from the world to create and update the sprites as the game state changes. This actually already allows for destructible terrain when I actually want to do it down the line. No procedural generation yet, that stuff look as fascinating as it is intimidating, so I'm loading maps for testing from CSV files.

Started the Action system over the weekend and the above gif is the first example of it. The keyboard input is setting the characters next action and, for now, automatically triggering it. This will hook into the main game loop and is largely based on the pattern explained in this article by Bob Nystrom which is amazingly useful. I really need to buy the guys book.

Plans for the next week?

I want to get the game loop in and have the PC moving as part of that and sort out what I'm doing with the camera. Once I can actually move around the levels I'm going to dive into setting up the fov system.