Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Team 2] Engineers Task Ticket #80

Closed
17 of 20 tasks
Tracked by #132
praneetdhoolia opened this issue Aug 31, 2023 · 3 comments · Fixed by #148 or #154
Closed
17 of 20 tasks
Tracked by #132

[Team 2] Engineers Task Ticket #80

praneetdhoolia opened this issue Aug 31, 2023 · 3 comments · Fixed by #148 or #154

Comments

@praneetdhoolia
Copy link
Contributor

praneetdhoolia commented Aug 31, 2023

Description

Task: [Team 2] Engineers Task
Feature: [Team 2] Towers and Engineers Feature Ticket

This task proposes the creation of an 'Engineer' entity, a new crucial component of the game mechanics which ties in to the win/lose state of the game. The number of engineers left is a direct representation of 'HP' of the player, and if reduced to zero, ends the game. Engineer entities will spawn as described in the Logic section below. The engineers will be able to move up and down along the lanes behind the towers and attack enemy mobs using a ranged weapon. They cannot be revived, causing the user to lose the game if all engineers are dead. This feature may be extended in future sprints to allow buffing or repairing of towers, and may become controllable by the player, adding a more interactive real-time component to the game.

Logic

One Engineer would be automatically assigned to defend a lane which satisfies the conditions below.

  • The lane doesn't have any active towers.
  • The defense has spare Engineer entities.
  • The lane has one or more incoming mobs.

If an engineer is killed in action and the lane still meets those conditions, another would be assigned.

Dependencies

Milestones

  • Implementation of Engineer entity factory mechanism. (Sep. 2)
  • Creation of Engineer entities. (Sep. 2)
  • Automated task logic, including mob detection and spawning. (Sep. 5)
  • Adding visual assets and animation controller. (Sep. 5)
  • Adding audio assets. (Sep. 5)
  • Creation of an animation controller class. (Sep. 5)
  • Integration of engineers into win/loss state. (Sep. 7)
  • Testing the Engineer entity and fixing bugs. (Sep. 7)
  • Integrating fully working Engineer in main. (Sep. 9)
  • Detailed Engineer documentation on wiki. (Sep. 11)

Optional - May be carried over into future sprints

  • Implementation of engineer attacking.
  • Implementation of engineer damage and death.
  • Integration of engineer Area Effects on Towers.
  • Clickable/controllable engineers.

Completion Deadline: Sep. 12

Documentation

Members

@praneetdhoolia
Copy link
Contributor Author

Added dependency links.

@The-AhmadAA
Copy link
Contributor

Updated task ticket with details of the feature's role in the game, and added further tasks.

@The-AhmadAA
Copy link
Contributor

Split tasks out for improved granularity

@praneetdhoolia praneetdhoolia linked a pull request Sep 12, 2023 that will close this issue
@The-AhmadAA The-AhmadAA linked a pull request Sep 12, 2023 that will close this issue
@The-AhmadAA The-AhmadAA mentioned this issue Sep 12, 2023
@Mohamad11Dab Mohamad11Dab moved this from In Progress to Done in 2023 Studio 3 Project Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment