next »

[Alec S.]

[Alec S.]

Made a new enemy model so that they're not just a palette swap of the player (I still need to clean up the animations a bit...)

[Alec S.]

Created a Spearman enemy

[Alec S.]

Added a lock-on graphic

[Alec S.]

Added another enemy type.  These ones have a shield which they hide behind, occasionally popping out to shoot at the player.

[FROGANUS]

Alec- Looks great!

I see the resemblance to your previous project, but wasting no time in expanding beyond some of the basic 'constraints' of the predecessor: this looks more '360' open with the view and level design, which is very attractive. Less emphasis on aimed shooting also really helps in this regard. I'm eager to see the movement and melee gameplay that this will pave the way for.

Also, the whole art concept and story seems on point. (I get torqued for purpley pink color schemes.)

 

[Alec S.]

Thanks!

[Alec S.]

Working on an enemy which will be the boss of the first area, but which will become a normal enemy later in the game

[Alec S.]

Currently working towards making some sort of playable demo out of the first area.  I've got the three enemy types that will be in the first area, the level design is all blocked out, combat is most of the way to where I want it, and I've got doors/keys working.

Stuff still left to do:
-The boss
-A few bits of controls tweaking
-Sound effects
-Health pickups
-More environmental objects (like the pillars)

[Alec S.]

[Alec S.]

Colossus

[Alec S.]

At the Gates

[Alec S.]

I've been working on some visual effects

[Alec S.]

Created an opening cutscene

[Alec S.]

Time for a break from things that make nice gifs, and into technical stuff.  I've been working on my Saving/Loading code.

Previously, for Cold Vengeance, I basically had a class that stored data such as what level the player was on, what their position was last time they hit a checkpoint, what their score/time was at the checkpoint, which coins they had found, ect...  Essentially, I was hard-coding every piece of information that needed to be saved.

That was good enough for a run 'n' gun game, but for an Action Adventure, there's a lot more that has to remain persistent, both when you save and reload the game, and when you leave a zone and then come back to it.  The primary thing is that items that the player has picked up need to stay gone and if a player defeats a boss, they should stay defeated.  But beyond that, if the player opened a door, it should stay open, or if the player interacts with an object in some way, it should be able to keep track of that.  For the time being, I think normal enemies will respawn when you leave the zone or restart to a checkpoint, but since I'm adding this directly into my base code, I also want the option available to me for later games (or if I change my mind in this game) to have enemy deaths be persistent.

The solution to this has been slowly taking shape, and I don't know if I'm going about this the best way.  Basically, if I want to make an object persistant, I can add a behavior to it that gets a unique ID (from another object that exists in each scene specifically to generate the unique IDs).  I then have a Level Manager object that can store information about objects (currently whether they've been destroyed or not, what their position is, and an array of boolean flags for misc. purposes), along with a reference to their ID.

From that point, it's up to the objects themselves how they interface with the object data.  For example, a unique item will check the Level Manager for data that matches its ID.  If it finds one, and the data has the Destroyed flag set to true, the Item will destroy itself.  If you pick it up, it will set the data in the Level Manager class to say it's destroyed.

Then I can just serialize the Level Data for each level to save the overall state of persistent objects.

[Alec S.]

Made a start screen:

[Alec S.]

Added a dodge roll.

[Alec S.]

Drop into Boss Battle



Continuing to work to polish up the demo.  I've been doing another pass on the level design, doing things like breaking up some of the building interiors with broken walls, and adding some more textural variations.

I've also added more behaviors to the boss.  In addition to the attack you've seen already, there's a bull-rush attack where he charges at the player with his axe in front of him, and there's an attack where he rolls towards the player then slams his axe on the ground.  I'll probably post gifs of them once they're a bit more polished.

[Alec S.]

[Alec S.]

Added a button which activates when you shoot it.  In addition to being something I can use for puzzles later on, right now it's a simple way to make sure the player knows how to lock on and shoot before they reach the first combat encounter.  It also provides the area with a nice bit of book-ending, as it will begin with opening a small gate, and end with opening a large gate.