What I made: This week my big focus was on making traps and obstacles for the player to dodge.
The spider: The spider trap is a trap that will be somewhat hidden for the player and once the player is within striking range. Once the player is within striking range the spider will lunge downwards towards the player, the spider will charge downwards really quickly and once the spider has completed its charging cycle it will slowly reel back in to its original position and resetting its attack.
The spiders speed and and trigger distance is directly related to the players speed. This is so that the trap will not become obsolete if the player is traveling really quickly or really slowly.
How I made the spider: I made the spider in Visual studio in c++. It has several functions that are dependent on the players properties, I did by linking the players values to the spider so that the spider can read the players values.
The spider measures the players speed and distance and triggers once the values are optimal. Once it triggers an internal timer inside of the spider starts that decides how long the spider will charge. The timer starts at 0 and counts up to 9 seconds, the spider charges for 3 seconds and the reels back up for 6 seconds, once the 9 seconds has passed the spiders internal clock will reset and it will go back to 0 so that the cycle repeats.
Why I chose to implement the spider: I chose to implement the spider into the prototype because it is a trap that would be more interesting than just normal falling traps. Before I started to work on the spider I had made a falling stalactite and the choice was between the stalactite and another enemy and I made the decision to make the spider.
Why we wanted to have a spider inspired enemy inside the game: The team wanted a spider themed enemy because it would match the aesthetic style in the game. A lot of power ups are based on fireflies and a fireflies natural enemy is a spider. From a coding perspective I chose it because it would be an interesting challenge to have make an enemy that would have a charging attack and timer implemented into its trigger mechanics.
The end result with the spider was an enemy that was somewhat scary looking with and unpredictable behavior
.
kimgrip 
The blog post is well written. You wrote about how and why you did things.
The only minor things that bothered me was that the information given about how you coded the things were a bit shallow. Maybe you could have gone into how it works a bit more. For example:
if you used vectors or two integers to define the positions. And how the spider charging mechanic works in syntax.
Which player values did you link to the spider? When are the values optimal?
Which power ups are based on fireflies? And how are the firefly related power ups related to a bat?
If the spiders movement pattern is fixed, does it not mean that it is predictable?
I see that the post has more value to those whom are not coders, since the information given is a a bit shallow. If the blog post was intended for coders to read, i think that it should have been more specific, with references to syntax and why you made things the way you did. And why you created the syntax the way you did: If you used an vector2f an array or sprite->getPosition() to define the location of the bat and spider.
GillaGillad av 1 person