New EVA voice after deploying a building

[FS-21]

• You can now replace the current EVA voice when a specific building is placed/deployed.
• If any building is undeployed/sold/destroyed, the EVA voice will be evaluated again across all active player buildings defining NewEVAVoice.Tag.
• NewEVAVoice.Tag specifies the EVA voice name (defined under [EVATypes] in evamd.ini via Ares, or vanilla voices Allied, Russian, Yuri).
• In case of multiple buildings with different EVA voices, NewEVAVoice.Priority establishes a priority queue, where the building with the highest value is selected.
• NewEVAVoice.RecheckOnDeath controls whether to re-evaluate the active EVA voice upon building destruction or sale.
• NewEVAVoice.InitialMessage plays an EVA sound message to the player when a new EVA voice is activated.
• NewEVAVoice.EndingMessage plays an EVA sound message / sound effect with the outgoing EVA voice when it is deactivated/replaced before transitioning to the new voice.
• When no buildings with NewEVAVoice remain, the EVA voice automatically falls back hierarchically:
  1. [HouseType] -> EVA.Tag (Country-specific EVA voice)
  2. [Side] -> EVA.Tag (Side-specific EVA voice)
  3. Default vanilla voice according to side index (Allied, Russian, Yuri)

In rulesmd.ini:

[SOMESIDE]                        ; Side
EVA.Tag=                          ; EVA type name from [EVATypes] or Allied/Russian/Yuri

[SOMEBUILDING]                    ; BuildingType
NewEVAVoice.Tag=                  ; EVA type name from [EVATypes] or Allied/Russian/Yuri
NewEVAVoice.Priority=1            ; integer
NewEVAVoice.RecheckOnDeath=false  ; boolean
NewEVAVoice.InitialMessage=       ; EVA entry
NewEVAVoice.EndingMessage=        ; EVA entry

[FS-21]

2025-05-28.09-02-10.mp4

[github-actions]

Nightly build for this pull request:

• compiled-dll-a057e896a45a9f4e5870dbd978f6e683a8eb8120.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

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]

The EVA voice change logic should be generalized and put in a separate function from buildings, probably in SideExt or something. Firestorm has a map trigger for this purpose and I suppose someone might want to reimplement that here as well.

Some smaller things to take note of as well.

[FS-21]

The EVA voice change logic should be generalized and put in a separate function from buildings, probably in SideExt or something. Firestorm has a map trigger for this purpose and I suppose someone might want to reimplement that here as well.

Some smaller things to take note of as well.

Since Ares already has Map trigger actions for changing these voices like in Firestorm I only focused in learning how to change it and apply this logic for buildings like in the video, not reimplementing again the EVA voices.

Let me see the SideExt you mentioned because I remember one of the first attempts was storing data in that place but things happened that made me move the code and I ended here.

[FS-21]

Applied feedback and updated documentation and initial message here.

The missing bit I have to do now is that suggestion of moving the code into a separated function from buildings to SideExt for future changes/additions, etc.

[FS-21]

Moved the UpdateMainEvaVoice(...) function to SideExt.

[Flactine]

Limbo Delivery buildings can't change EVA

[FS-21]

Limbo Delivery buildings can't change EVA

Yes, I never tried that so I added support now.

I updated this code and added support when a building is captured by engineers.