View Issue Details

IDProjectCategoryLast Update
0021277AI War 2Bug - OtherJun 6, 2019 9:32 am
Reporterwm46 Assigned ToChris_McElligottPark  
Severityminor 
Status resolvedResolutionfixed 
Product VersionBETA 0.866 Hotfix 
Fixed in VersionBETA 0.867 Smarter AI, Better Mark Spread, Player Economic Boom 
Summary0021277: Guard posts don't release stored units if they die instantly
DescriptionIf a guard post has stored guards and manages to be destroyed in one frame, stored units don't deploy at all.

The code that calls the function to deploy guards is in PlanetFaction, and it will deploy the units if:
1. There's enemy ships on the current planet
2. Any enemy ship is within a certain distance, or the guard post has taken damage

Ships that are completely destroyed in one step are extremely likely to do neither of these however. The current order for frames goes as follows:
1. Check if we need perSecond logic
      a. Do per second logic (*calls guard post unloading*)
2. Planet Combat Step
      a. Ship Step (Movement, Bubbleshield Size)
      b. Flag dead ships for removal
      c. Shot Step (Move Shot, Do Damage (sets ToBeRemoved if it kills)
3. Remove Flagged Entities

So there is a 1 frame window where a guard post can still release its units if its killed in 1 frame, but only if the next frame calls the perSecond logic.

Possible solutions:
Check for stored guard post contents during step 3 (Remove Flagged Entities)
Check for stored guard post contents when doing combat death (step 2c)
TagsNo tags attached.

Relationships

child of 0021274 resolvedChris_McElligottPark GameEntity_Squad.AIReinforcementPointContents Issues Parent 

Activities

Chris_McElligottPark

Jun 6, 2019 9:32 am

administrator   ~0051863

Thank you!

* Now when a unit dies, if it has reinforcements inside it for whatever reason, it should dump them all out immediately. Previously if you managed to kill a guard post full of reinforcements in under 1 second, then the guards would all die in the fire of their parent. Now they go free and attack you, as was always intended.

Issue History

Date Modified Username Field Change
Jun 6, 2019 2:29 am wm46 New Issue
Jun 6, 2019 2:30 am wm46 Relationship added child of 0021274
Jun 6, 2019 9:32 am Chris_McElligottPark Assigned To => Chris_McElligottPark
Jun 6, 2019 9:32 am Chris_McElligottPark Status new => resolved
Jun 6, 2019 9:32 am Chris_McElligottPark Resolution open => fixed
Jun 6, 2019 9:32 am Chris_McElligottPark Fixed in Version => BETA 0.867 Smarter AI, Better Mark Spread, Player Economic Boom
Jun 6, 2019 9:32 am Chris_McElligottPark Note Added: 0051863