On 3/18/2012 11:50 PM, edenicholas wrote:
> On 3/18/2012 2:02 PM, edenicholas wrote:
Wrote a quick post-mortem. Biggest wrong: Not being roguelike (or is it
roguelike-like? (or is it Binding of Isaac-like?)) enough. Any
suggestions or ideas on how to improve would be appreciated. (besides
"make a turn based game" :P)
What went right:
It's well documented and when I had questions, a quick Google search
(eg. "unity 3d how do I obtain a random rotation around the y axis")
would turn up what I needed. This is the 5th project I've made in Unity
in the past 4 months, so I was up to speed and needed very little lead
time to practice.
2. Simple art style
I stuck to the simple art style that I adopted in Dead Night Forest 1
and just didn't worry about it. And the enemy's beady eyes make me want
to hack and slash them all that much more.
3. Got the combat system working fairly early
I really love roguelikes and have for many years, but these days I
really want something more twitch based, but not a mash fest like Elder
Scrolls has become. That was one of the goals of this project and I feel
I accomplished much. It's a nice proof of concept that the system I had
in my head would work in practice. I can take what I've learned here and
start work on my Skyrim-killer roguelike fps hybrid in earnest.
What went wrong:
1. It's barely a roguelike
A pretty major factor in a roguelike dev challenge. While I created a
playable game after 7 days, what I've created is barely a roguelike. It
has procedural levels, and a basic item ID system, permadeath, and
that's about it. The hunger mode gives you a real-time hunger clock, but
it's optional. One major flaw is the lack of resource management, aside
from health. Another is that there's no tactical advantages presented in
the layout of the map. The last I feel would be interesting, game
changing items. The potion effects were meant to change up the way one
approaches each battle, but that really didn't come across that well.
2. Not enough enemy types, enemy attack types, and
Encounters feel too bland. Each enemy has only one attack. With only two
enemy types that means there are only two types of attacks to learn how
to avoid or counter. Which leads to...
3. Enemies are too easily kited to death.
A major thing that I overlooked was simply kiting enemies and attacking.
I knew in early testing that the problem was there, just slash, back up
and wait for the enemy to approach, slash again. This is a 100% way to
beat every enemy. The AI will fall for it every time, and it totally
eliminates all the depth of countering and guard breaking that I worked
All in all, it was a fun week, and a great learning experience. I got a
ton of practice modeling and animating in Blender, and really pushed the
boundaries of my knowledge of Unity game development. I ended with a
playable game, that despite the game breaking bug (#3 above), I find
quite fun to play. also the sound effects I created for eating and
drinking make me giggle.