Skip to content

Add AI teams to sync logging#1828

Merged
Coronia merged 1 commit intoPhobos-developers:developfrom
Starkku:feature/team-sync-logging
Aug 30, 2025
Merged

Add AI teams to sync logging#1828
Coronia merged 1 commit intoPhobos-developers:developfrom
Starkku:feature/team-sync-logging

Conversation

@Starkku
Copy link
Copy Markdown
Contributor

@Starkku Starkku commented Aug 23, 2025

@Metadorius asked if this is doable and I am delivering. Basically exactly what it says in the title, all currently active TeamClass instances will have some info about them printed at the end of the sync log. Because the TeamClass array already effectively functions as a storage for this info there was no need to add any new sync events to record. Additionally I tried to make it bit more readable by adjusting the padding used dynamically but this does add little bit of extra runtime on writing the logs (which is only done once unless you have -MPDEBUG parameter on) I suppose.

If there is some other relevant info about teams that should be recorded, let it be known in this PR. I tried to include the most relevant parts.

An example of what such a log may look like:

AI Teams:
#00000: Type:  07C2D662-CTMBDFLab01-G | Script: 06DAB27C-SCCoalBDFLab-G | Line:  1 | Owner: 2 (Computer) | OwnerHouse: Coalition
#00001: Type:  065D29C6-DTMBDFPow01-G | Script: 06C0F679-SCDomiBDFPow-G | Line:  3 | Owner: 3 (Computer) | OwnerHouse:  Dominion
#00002: Type:  04F1F694-CTMBDFPow01-G | Script: 05728DCA-SCCoalBDFPow-G | Line:  1 | Owner: 2 (Computer) | OwnerHouse: Coalition
#00003: Type:  0448FEAF-DTMBDFLab01-G | Script: 0511D07E-SCDomiBDFLab-G | Line:  1 | Owner: 3 (Computer) | OwnerHouse:  Dominion
#00004: Type:  05DB3227-CTMBDFRef01-G | Script: 06930A62-SCCoalBDFRef-G | Line:  1 | Owner: 2 (Computer) | OwnerHouse: Coalition
#00005: Type: 05E743F3-DTMRavager01-G | Script:   079C95F4-SCDomiRavg-G | Line:  4 | Owner: 3 (Computer) | OwnerHouse:  Dominion | TargetRTTI: 11 (Cell) | TargetID: 01078752 | MissionTargetRTTI: 11 (Cell) | MissionTargetID: 01078752
#00006: Type: 05DAB9F5-CTMBaseGen01-G | Script: 07FA9250-SCCoalBDFGen-G | Line:  7 | Owner: 2 (Computer) | OwnerHouse: Coalition
#00007: Type: 04ABA9BD-DTMBaseGen01-G | Script: 06A89E7D-SCDomiBDFGen-G | Line:  5 | Owner: 3 (Computer) | OwnerHouse:  Dominion
#00008: Type:  0720B95E-DTMBDFRef01-G | Script: 07DB1BDD-SCDomiBDFRef-G | Line:  3 | Owner: 3 (Computer) | OwnerHouse:  Dominion
#00009: Type: 07F11555-DTMFVSHarv01-G | Script:  06DF9E54-SCGenFVSHrv-G | Line:  2 | Owner: 3 (Computer) | OwnerHouse:  Dominion

@Starkku Starkku added the Minor Minor feature and/or fix, not a lot of changes or they are not significant label Aug 23, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 23, 2025

Nightly build for this pull request:

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

@Starkku Starkku force-pushed the feature/team-sync-logging branch from 517507e to 7dd8dfd Compare August 24, 2025 11:06
Copy link
Copy Markdown
Contributor

@Coronia Coronia left a comment

Choose a reason for hiding this comment

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

worked in testing

@Coronia Coronia added Tested ⚙️T1 T1 maintainer review is sufficient labels Aug 30, 2025
@Coronia Coronia merged commit ed82230 into Phobos-developers:develop Aug 30, 2025
12 checks passed
@Starkku Starkku deleted the feature/team-sync-logging branch September 11, 2025 10:47
Metadorius pushed a commit that referenced this pull request Sep 30, 2025
@Metadorius asked if this is doable and I am delivering. Basically
exactly what it says in the title, all currently active TeamClass
instances will have some info about them printed at the end of the sync
log. Because the TeamClass array already effectively functions as a
storage for this info there was no need to add any new sync events to
record. Additionally I tried to make it bit more readable by adjusting
the padding used dynamically but this does add little bit of extra
runtime on writing the logs (which is only done once unless you have
-MPDEBUG parameter on) I suppose.

If there is some other relevant info about teams that should be
recorded, let it be known in this PR. I tried to include the most
relevant parts.

An example of what such a log may look like:
```
AI Teams:
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Minor Minor feature and/or fix, not a lot of changes or they are not significant ⚙️T1 T1 maintainer review is sufficient Tested

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants