#mechanictest

[adamtheamazing5]

A short minigame project exercise to kickstart for the new year, This time comes a Frogger clone. I usually prefer not to make game clones, but I decided to do a short exercise to warm up my skills for this year since I'm doing more complex projects later this year and then looking for work as a game tester or game designer. I did not make these assets, they were provided to me by AwesomeTuts. What I learned - to move the player character 1 unity without using delta time. - Getting The player to move to the starting position without using a vector 3 variable while executing it from another script rather than the player controller script. What I could've done better -Even though the background "roads" is not mine, It doesn't look pretty and is uneven with the player moving from unit to unit. So I could have made the roads and grass( safe area) follow unit by unit rather than be uneven which would cause the player to be hit by cars more easily. Overall -It was a nice warm-up for the beginning of this year.

[adamtheamazing5]

This time, I decided to do a programming exercise of a simple boss battle which will prepare me to make more complex boss battles for my future games. Normally I would prefer making it into an fps project battle boss, but I decided to do it similarly to a tank shooter-styled game to learn different ways of mechanics to use for my future games. WHAT I AM DEMONSTRATING: •   Player can move backward and forwards and rotate around. •   Player can shoot orbs from in front of him instead of using ray casts. •   The turret boss can aim and shoot cannonballs at the player wherever he is. •   The turret boss randomizes a minimum and maximum shoot force and fire rate. •   Both the player and the turret boss have health which determines the win-or-lose factor of the game. WHAT I LEARNED: •   Assigning game object variables with nulls is a good way to reduce errors when starting the project, except when they are called by in script by methods, awakes, or updates. •   Making game objects flash by mesh renderer when damaged then back to their original color which was stored in the awake function. •   Getting object references from projectiles by using their game object name instead of tags. •   Made simple particles for the cannonball and magic orbs. For the orbs, they combine lots of particles to make 1 orb. •   Adding relative force to Cannonball’s rigid body relative to its coordinative system. •   The difference between PlayOneshot audio parameters compared with play Audios. •   Getting the turret to randomize with Random.range with fire rate and force of cannonballs respectfully. •   Not getting the UI methods in the update function otherwise it wastes performance in the game manager. •   Static variables can be saved in the game Manager and be updated whenever called from other scripts. •   For orbs, I can use the audio length to play a certain sound before self-destroying the game object. Making sure the audio plays its full sound without cutting off. OVERALL: It was a nice and short exercise, I think usually boss battles are a bit more complex than this one, but I learned different ways of making mechanics that will be useful for my toolbelt in future development. #gamedevelopment