EVA.Event tags do not work on Type=HunterSeeker

Bug #1393086 reported by modder666
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Fix Released
Medium
AlexB

Bug Description

In my mod, I utilize the Type=HunterSeeker SWs to spawn vehicles that will deploy into expansion outposts. This new SuperWeapon has been added to the Construction Yard, but at the beginning of the game (when the AI would have deployed it's ConYard) I get an EVA report based on the side I am playing for the larger SW on the side (if playing against Allies, I get" Warning, Weather Control Device detected"). However, the SuperWeapon has EVA.Detected set to none. I will add my code below in case I have merely missed something.

[AlliedExpansionPower]
UIName=NOSTR:Request HQ
Name=Humper Seeker Trick
IsPowered=false
RechargeVoice=
ChargingVoice=
ImpatientVoice=
SuspendVoice=
RechargeTime=3.5
Type=HunterSeeker
Action=Custom
SidebarPCX=aexpandpower.pcx
FlashSidebarTabFrames=120
ShowTimer=no
DisableableFromShell=no
SW.AITargeting=none
Money.Amount=-1000
HunterSeeker.Buildings=GACNST
HunterSeeker.Type=AFHQ
HunterSeeker.RandomOnly=no
EVA.Detected=none
EVA.Ready=none
EVA.Activated=none
EVA.Impatient=none
EVA.InsufficientFunds=none
EVA.SelectTarget=none

Revision history for this message
AlexB (alexander-b) wrote :

What SWs does the Construction Yard have? Did this start recently, or was that also like this with 0.8?

Revision history for this message
modder666 (modder666) wrote :

Each Construction Yard is equipped with their own variant of the above SuperWeapon, using SuperWeapon= tags. This is the only SuperWeapon the Construction Yard is equipped with. This is a 0.8 bug, as I have not started using the new unstable release.

Revision history for this message
AlexB (alexander-b) wrote :

Please test with the latest unstable builds, because I changed large parts of this code. Is there by any chance an EVA event by the name of "none"?

Revision history for this message
modder666 (modder666) wrote :

I will try it with the latest unstable build. I set EVA.Detected to 'none' as the online documentation suggested, and there was no indication that it had changed in 0.9. I will test with the latest unstable and get back to you.

Revision history for this message
AlexB (alexander-b) wrote :

The documentation for 0.9 is not out yet, and there will be no change in this regard. The change is that in 0.8 and earlier a SW that does not suffice AuxBuilding was still announced as detected. This should not happen any more. EVA events do not consider "none" or "<none>" special, thus if you have an event called "none", this will be played. If it does not exist, nothing should be played, which is what "none" means.

Revision history for this message
modder666 (modder666) wrote :

After downloading the latest revision in the "Rough Seas" branch, I still got the same error. I tried switching EVA.Detected from "none" to "<none>" just to make sure WW hadn't entered any events into their EVAmd.ini. After entering the game and the Allied AI deploys their MCV, I get "Warning, Weather Control Device detected" message.

Revision history for this message
modder666 (modder666) wrote :

I took a step further to attempt to solve these issues, and created an EVA event with no sounds set. After adding EVA_NoWarningOrDisplay I was able to relieve this issue.

[EVA_NoWarningOrDisplay]
Text=No warning or display.
Russian=
Allied=
Yuri=

Revision history for this message
AlexB (alexander-b) wrote :

Did you, by any chance, put the Hunter Seeker SW as third on the SuperWeaponTypes list? In that case, an EVA event of <none> or none is not considered a valid value and Ares passes control back to the game, which goes through its own list. Nuke, IC, LS, ... If this is the case, this will be fixed in the next 0.9 build.

AlexB (alexander-b)
Changed in ares:
assignee: nobody → AlexB (alexander-b)
milestone: none → 0.9
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
mevitar (mevitar) wrote :

Confirming this issue as fixed.

AlexB (alexander-b)
Changed in ares:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.