gamedev Iiro

The second playtest included all playable content of the game: the level as a whole, character progression, enemies, treasures, functioning shortcuts, and two bosses.  The test itself went much smoother than the first. It was conducted on the same PC as the first so I could see if the performance had improved. The game's default graphic scalability is now set to epic instead of cinematic and I assume that my custom-made materials are more lightweight than the prototyping materials I used earlier. The graphics card's VRAM ran short once again, but only by around 100 megabytes. The frame rate doubled compared to the first test's and the input lag was gone.  The playthrough of the level went smoothly without any issues or difficulties. Both of the bosses took several attempts, which was within my expectations. I was initially worried that one of the first boss' abilities was unclear. The boss jumps and slams the ground causing an earthquake that damages the player if they...

Enemy respawn when resting at a save point To make enemies respawn when the player rests at a save point, I went back to the enemy spawner and created an event that spawns new enemies in place of defeated ones. It simply goes through an array of killed enemies checking if they should be respawned and then removes the enemy from the array. The event that respawns enemies. To prevent duplicate enemies from spawning when resting after loading the level, I created a second event that clears the respawning enemies from the array when the level is loaded. Clearing respawning enemies from the killed enemies array. I noticed that removing an item from an array that is being looped through caused the next item's index to drop by one and it would not be included in the loop, always "skipping" the next index after an item is removed. So any changes are made in a temporary copy of the array and after the whole loop is finished the original array is updated with the information from t...