{"id":1264,"date":"2025-05-10T17:43:24","date_gmt":"2025-05-10T17:43:24","guid":{"rendered":"https:\/\/sites.wsagames.com\/et4g23\/?p=1264"},"modified":"2025-05-14T15:16:45","modified_gmt":"2025-05-14T15:16:45","slug":"wrought-pt-2","status":"publish","type":"post","link":"https:\/\/sites.wsagames.com\/et4g23\/2025\/05\/10\/wrought-pt-2\/","title":{"rendered":"Wrought – Pt 2"},"content":{"rendered":"\n

A large issue I had noticed with the Wrought enemies, was that in order to aim towards the player, the entire gameobject would rotate in the direction of the player. Therefore, its sprite would also rotate towards the player; which needed to be fixed immediately.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The process I chose to fix this issue, was to use a child object which would rotate independently of the parent object that would have the Sprite Renderer and Animator components. This child object would act as the sprite renderer and would rotate in the opposite direction of the parent object, effectively counteracting the rotation and causing the Wrought’s sprite to appear as if it weren’t rotating at all.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\n
\n

Furthermore there would also be a second child object that would act as a hitbox:
To allow the child object to deal damage to the player, I wrote a simple script that would check if any collisions were from the player.<\/p>\n\n\n\n

If the player was the other object in the collision, it would call the TakeDamage()<\/em><\/strong> method in the player’s PlayerHealth script<\/strong><\/em> and cause the player to take one HP of damage.<\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n