I still have a big feature to do and that is UI navigation using all the input devices — keyboard, mouse and controller. I want these done in a way that I can easily modularize, yet keep concrete pipeline that
MicroRogue DevDiary #83 – Controls UI
With the addition of my new UI sprites, I tried to update the Rewired plugin’s UI that they provide. And I realized two things — it has way too many elements and I want to do certain things differently. In
MicroRogue DevDiary #82 – Modular UI elements
So Unity added nested prefabs in their newest (stable) release. All my games are usually very code-centric and I don’t build complex scenes, so I never really cared about nested prefab features as they apply to designers. But now I
MicroRogue DevDiary #81 – UI Sprites
Time has come to make sprites for UI. This involved me opening Photoshop and emerging 3 days later with a couple barely passable sprites. Anyway, here are all the sprites I will use (for now) in the primary UI elements:
MicroRogue DevDiary #80 – Goal UI
Continuing on the goal stuff, I need UI to let the player see their progress. First thing’s first — I need a “place” to show the goals. They can presumably have their own panel or page, but this page has
MicroRogue DevDiary #79 – Goals
So far, I’ve not talked much about design in my posts. Or, rather, I have implied straight-forward design in most of the features. I’ve also implied that the features work together. Occasionally, I’ve clarified my intentions. But (besides some weapon
MicroRogue DevDiary #78 – Goal framework
As part of my player progression, I decided to make a “goal” system. A goal being broadly defined as some sort of simple objective to be reached. Kind of like mini-achievements or challenges. A lot of games do these and
MicroRogue DevDiary #77 – Tile lighting
Okay, I need something visual and pretty to happen in the game as I’ve been staring at the same boring assets for too long. Even animations are now just a bunch of numbers. So let’s add lights the game! This
MicroRogue DevDiary #76 – Animation-based effects
In this prolonged post I will implement effects that semi-automatically spawn based on the animation, so that I don’t have to specify fiddly values for every mob and such. Time traveler note: Half-way I realized I am doing things wrong
MicroRogue DevDiary #75 – Improvement interlude
There’s a lot of minor stuff I am doing all the time that doesn’t really fit anywhere or makes other posts bloated. So I’ll go over some important but small things that I am working on. A lot is to
MicroRogue DevDiary #74 – Player gear-based parts
Now that the player has gear — individual items in designated slots — I might as well have the player “model” correspond to these parts. Now, this is easier said than done. I need to adjust my part animator logic
MicroRogue DevDiary #73 – Loadout UI
Now, all of this new gear and loadout stuff leads me to needing all-new UI. And this is a tough sell (read: feature creep). UI takes time, art takes time, it implies all sorts of input requirements and visual feedback
MicroRogue DevDiary #72 – Gear and loadout
I mentioned that I want to have the player select gear to equip. There are some design directions I want to go with this that I will likely talk about later. The main idea is that the player gets a
MicroRogue DevDiary #71 – Experience
Continuing on the upgrade system, I am implementing an experience system. Experience and levels are an indirect way to adjust difficulty for the player. Regardless of player skill, there will be some location in the dungeon where they reach their
MicroRogue DevDiary #70 – New upgrade system
My upgrade system is very lacking at the moment. I also have no controller-usable UI for upgrading. My upgrade terminal is currently broken. An upgrade can be summed up as (cost, stat boost, level): Barring pretty UI, this is pretty
MicroRogue DevDiary #69 – Sound effects
I’ve been somewhat dreading adding sounds to the game. But I have to, there is no question. This just means finding sound assets, choosing them, and all the tedious finicky work that comes with it. Thankfully, the technical details (which