WEEK2

Introduction

Goals

I have been assigned work on the enemy AI system.

The AI should be able to:

• Shooting: attacking the player, when player access into a specific enemy's attack range, shoot the bullets 1 each frame also stop shooting when exiting the attack range

Personnel

The following is the primary author and any secondary authors who assisted in completing the tasks this week. 

• Primary - Serena
• Secondary - 

Technologies, Tools, and Resources used

The following are the technologies, tools, and resources to assist in completing the set goals this week.

[How to make a Tower Defense Game (E05 SHOOTING) - Unity Tutorial]-

[How To Make An Enemy To Aim And Fire Bullet Towards Player Position? Simple 2D Tutorial.]-

Key Tasks Undertaken

The following are the key tasks that were taken to help a developer/reader understand how the tasks were completed.

1.  open the game project file, and created a file for my work, drag everything I edited in that file and create a new scene
2.  working on the old scripts and create d 2 new scripts to make the scripts work better and properly
3.  Comparing with the old scripts and move the main function codes to the new script. 
4.   think about the function, and what we need to turn up the trigger that tells the enemy to target
5.  the first new script named Enemy AI, also applying a status pattern to allow the enemy easier to switch their behaviors 
6. instead of using look radius, using collisions to adjust the areas
7. another new script will be EnemyViewVolume which will tell the enemy when enter this filed what they are going to behave 
8. attach a new collision to the enemy prefab 
9. attach the new script of EnemyViewVolume script to the collision and the EnemyAI script the enemy prefab
10. read through the contents of other people's scripts who did weapons.
11. applying other peoples' work find out a suitable way to make enemy shooting behavior
12. always check with references 
13. fix script errors to updated unity issues and classify the codes
14. commit the changes and merge to the server and push it to the bitbucket

What I Found Out

Include any particular lessons learned, especially if this Spike was designed to cover knowledge gaps. Use Graphs, ScreenShots, Outcome Lists, or other Notes.

1.  how to appropriately choose trigger is important

Solution Justification

1. have assumptions to see what dynamic is required and search tutorials to get relevant knowledge
2. check with unity references to confirm the rightness 

Open Issues/Risks

List the issues and risks that you have been unable to resolve at the end of the spike. You may have uncovered a whole range of new risks as well.

• shooting towards the target's position is different from stalking the target

Recommendations

• try to access exist work form others to make enemy attacking behavior next week