After hearing this question a few times in the discord channel, I decided to give the newest version of the asset and Unity 2019.4 LTS a run to make sure I could do the URP "upgrade" and get rid of that giant HDRP warning that comes by default.

Here is the document that steps you through that process.

Note that I did this with Unity 2019.4.14f1 and Sci Fi Top Down Game Template Version 2.11 (last updated Jul 7, 2020). If you have different versions of either, your mileage may vary.

As far back as Diablo (and really even before that, with the ORIGINAL Gold Box D&D: Pools of Radiance), I've always wanted to create my own top down combat game. I absolutely loved the player experience of the Dungeon Siege games, and I wanted to implement as much of that camera control and party mechanic as I could in Unity.

So when I saw the Sci-Fi Top Down template in the asset store, I decided to give it spin as a springboard to implement that kind of mechanic, but in a sci-fi setting.

Starting with the basics of this template, it has animated soldier and 4 legged procedural walking robots, along with animated turrets. I went in and immediately changed the weapon selection mechanic to be hotkey based (1 - 4 for the 4 item slots) and I added camera controls that suited my Dungeon Siege inspired plans. I even added the "zoom way out, but still be able to control your avatar for movement and combat" mechanic that most games now-a-days have replaced with an overlayed map. I still prefer the Dungeon Siege method, and went with that, though I did not get to add in the LOD changes, or the worldspace UI overlays I wanted to add due to time constraints.

Once I was confident I had the basics of all of the game mechanics sorted (movement, camera, weapons, and inventory), I decided to give the included dungeon generator a try. The one in build 2.1 of the asset was almost ready to use, though it appears to be broken in the newer 2.11 build, but I have only spent a few minutes in that build, and reverted when I couldn't get the dungeon generator to work.

Now I've generated a half dozen dungeons, I figured out how to randomize the setup of items in the rooms, and I added in a "boss" room at the end of the map. There is still a bug where the boss room gets "locked" from the player getting to it. I'd planned make a game mechanic where you have to clear all the other enemies first and then the boss room gets opened — but right now, I'm just removing that lock and saving the dungeon with the boss room.

I spent a lot of time and finally abandoned building my own boss character. Something about the movement mechanics was making my boss character bounce all over the room at rapid speed and I couldn't track it down. I fought with it and finally lost steam. I even asked for help and people with much more experience than I have at this point, but they were also baffled ... so that was the end of that.

For the boss, I just modified the existing 4legs robot, made him bigger and gave him a different type of gun. He still needs a lot of tuning to be a "boss", but since the room has so much going on, it makes it pretty tough even without him being a good boss.

I started with a lot of excitement, since I was starting with a template which seemed to have a lot of the top down game mechanics I wanted to build on top of. WASD movement, mouse aiming, npcs that walk around and have basic player hunting behaviors.

But upon importing the asset, my excitement got quashed quickly. The asset only worked out of the box with the old rendering pipelines previous to Unity 2018. With all the confusion around the various rendering technologies (Read my

After I read enough forum posts and figured out how to make everything stop being pink, I moved onto the game demo scenes. Loading the various ones in order, the main menu was clickable, to load the next scene, but then the character selector was not clickable — and it didn't make it obvious which keyboard key to press (E in this case) to select my avatar. Going with the built in menu system wasn't going to be part of my plan.

Moving right along, I loaded the survival demo scene and right off the bat, the enemies weren't respawning after the first wave. I then spent a good hour learning how the spawn system works, fixing the spawn counter for the level, and then finally being able to spawn more waves of enemies.

After I got the enemy respawn system working, I realized that none of the player keys were documented. Neither were the joystick controls. I wrote my own instead. Note that my docs reflect changes I've made to the template as well.

Lastly, the overall feel of the engine layout just wasn't what I was hoping for as a basis for any longer term project, so I decided to stop at the point which I have in the videos with one boss room and a multi-story dungeon randomly generated.

A quick bullet point all of the game mechanics in this prototype.

Things I was testing with this prototype:

Though I swore to myself I wouldn't write any more music for my own games until I had a team of developers making the game awesome while I wrote awesome music ... I slipped up once during the development of this prototype and created this first mix of a track I named Diddle Foo Top Down (for no obvious reason).