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 Sprint 2 - Scanner and Engineer Spawning #129

Merged
merged 10 commits into from
Sep 10, 2023

Conversation

The-AhmadAA
Copy link
Contributor

This merge will update main with the 'Gap Scanner' functionality that detects the conditions required to spawn engineers into the game area. These conditions are:

  • No towers in the lane
  • No engineers in the lane
  • Mobs detected within 10 tiles of the Scanner entity.

A scanner entity (invisible) is spawned at the far left end of each lane and scans for conditions appropriate for spawning engineers.
If the conditions are met, up to three engineers are spawned at the location.

Additional organisational changes - a 'wiki' directory has been added to the assets directory for storing documentation related diagrams, images, etc, and contains a directory for each team.

Copy link
Contributor

@Mohamad11Dab Mohamad11Dab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent Work!

@ryandmcneilly
Copy link
Contributor

Looks good, Engineers seem to be going to a lane where there are no enemies is the only problem that I've found. Apart from that good work!

@The-AhmadAA The-AhmadAA merged commit 0f09aab into main Sep 10, 2023
4 checks passed
@The-AhmadAA
Copy link
Contributor Author

Looks good, Engineers seem to be going to a lane where there are no enemies is the only problem that I've found. Apart from that good work!

Thanks for the feedback, I'll see if I can fix that before tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

4 participants