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

Enemy Commander pt2 #574

Closed
4 tasks done
Wyqer opened this issue Mar 7, 2019 · 0 comments
Closed
4 tasks done

Enemy Commander pt2 #574

Wyqer opened this issue Mar 7, 2019 · 0 comments
Assignees
Milestone

Comments

@Wyqer
Copy link
Member

Wyqer commented Mar 7, 2019

Short Summary

Next part of #529

Description

This part will provide the foundations for the "decision making" of the enemy commander. So the target is to implement routines (maybe think about a FSM for this) to trigger certain enemy actions concerning reinforcing/transfer garrisons, like it was mentioned in pt1:

This by moving vehicles/soldiers from one sector to another or by reinforcing them from his military bases (which could be considered as enemy forces spawn points)

Furthermore a first implementation of the mechanic, that the enemy won't directly know the positions of the players FOBs and may send out reconnaissance teams in the area where the players are progressing, to discover the FOB, so it would be a valid target for later counter attacks by the enemy commander. Until it's not discovered it shouldn't be a valid target. Maybe this could be some kind of "semi realistic" due to the fact that some maps are maybe not that big and FOBs might be built near to sectors. We need to test that after we've a basic mechanic for this idea.

2019-06-09 - Edit
Garrison reinforcement etc. will be moved to the next iteration.
This iteration is laying down the basic FSM, enemy patrols and likely the recon mission to get knowledge about player FOBs.

Sub-Tasks

  • Implement/Research possible routine/FSM for a reliable and plausible "enemy reactions/decisions" mechanic
  • Implement patrols in enemy territory as function and in routine/FSM
  • Implement "discover player FOBs" functionalities Will be moved to next sprint
  • Implement this mechanic in the routine/FSM Will be moved to next sprint
@Wyqer Wyqer added the backlog label Mar 7, 2019
@Wyqer Wyqer added this to the Sprint 11 milestone Mar 7, 2019
@Wyqer Wyqer self-assigned this Mar 7, 2019
@Wyqer Wyqer added in progress and removed backlog labels Mar 29, 2019
@Wyqer Wyqer modified the milestones: Sprint 11, Sprint 12 Apr 1, 2019
@Wyqer Wyqer added this to the Sprint 13 milestone May 4, 2019
@Wyqer Wyqer added in progress and removed backlog labels May 10, 2019
@Wyqer Wyqer added done and removed review/QA labels Jun 22, 2019
@Wyqer Wyqer closed this as completed Jun 22, 2019
@Wyqer Wyqer mentioned this issue Jun 30, 2019
@Wyqer Wyqer mentioned this issue Jul 30, 2019
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant