View Issue Details

IDProjectCategoryLast Update
0023054AI War 2[All Projects] Bug - GameplayMar 24, 2020 12:06 am
ReporterRoseAssigned ToBadgerBadger 
Status closedResolutionno change required 
Product Version2.009 Plenty Of Tuning 
Fixed in Version 
Summary0023054: Dyson Sphere Activates Distant Raid Engine
DescriptionApologies if this is a duplicate I couldn't see my prior report anywhere.

Playing on Tale of Two Stars, I freed a Dyson sphere near my homeworld to no unexpected effect. Later I captured another planet, which explored planets on the far edge of the galaxy from me. One of these explored planets is adjacent to the second Dyson sphere and immediately began launching raids against me.

I'm not entirely sure this is a bug but it seems like undesirable behavior. The raid engine is out of deep-strike range so I can't do anything to stop it. And it seems odd that it only started raiding when it became explored.
TagsNo tags attached.


Strategic Sage

Mar 23, 2020 12:46 pm

reporter   ~0056598

I can't say for sure on the unexplored part, but it isn't a bug that other factions can activate raid engines. They react the same to other factions as they do to the player; I've seen them trigger on other AIs in Civil War, Marauders, etc.


Mar 23, 2020 2:45 pm

reporter   ~0056599

Ah yes. Raid engines. I have had some experience with them while playing (more like watching) a Friendly AI Civil War game. When you say "it launches raids", is the countdown appearing and then nothing happens, or does something spawn on one of your planets when the countdown ends?

During my Friendly AI Civil War game, I saw (let's call the AI factions AI 1 and AI 2) an AI 1 raid engine target an AI 2 planet from across the galaxy, since there were no adjacent warpgates next to the raid engine. It's since been changed so Civil War AI's shoot raid engines, but it's possible that's what is happening to you,

My belief is that the Raid engines don't target a planet by itself, it targets a planet using friendly Warpgates. If there's no Warpgates next the raid engine planet, I believe (and again this is just a theory) it searches for enemy planets next to a warpgate and sends the wave there.

My guess on what happened: I've heard that the Dyson destroys warpgates. It's possible this happened in your game. The Dyson then triggers the raid engine. It can't fire on the Dyson since 1. I'm pretty sure nothing happens if it triggers it normally (The Dyson doesn't "control" planets) and 2. It couldn't send it at them anyway because there was no adjacent warpgates that could target the Dyson. So the Raid Engine looks at the rest of the galaxy and sees that there is a warpgate that can target one of your planets, and so it sends the wave at you via that warpgate. One thing I'm unsure of is if the raid engine targets the closest possible planet. So if you keep getting hit by the Raid Engine waves on the same planet every time, and its the one closest to the Raid engine, that might confirm the "Target closest planet" part.

Again, This is just a theory. It's entirely possible I'm wrong about the circumstances of your game and the rules in general.


Mar 23, 2020 11:31 pm

reporter   ~0056600

It makes sense that the raid engine can trigger on other factions. The behavior that seems undesirable is the fact that this raid engine is many jumps distant i.e. I can't interact with it at all except let it raid me indefinitely.

Loading the save, it appears to be sending waves against the Dyson sphere instead of my planets but what prompted me to save and make the report was the impression it was actually raiding my planets in response to the distant Dyson sphere. Either I'm confused about what happened or I interpreted the UI wrong? Either way, I can't replicate it.


Mar 24, 2020 12:04 am

manager   ~0056601

Last edited: Mar 24, 2020 12:06 am

View 3 revisions

The tooltip for the raid engine notification should say "This wave is against <faction name>".

So what's happening is that you only get the Notification once you explored the planet. The Raid Engine has probably been active for some time, but you just didn't know about it.

I don't see an actual bug here.

Issue History

Date Modified Username Field Change
Mar 23, 2020 1:08 am Rose New Issue
Mar 23, 2020 12:46 pm Strategic Sage Note Added: 0056598
Mar 23, 2020 2:45 pm Ovalcircle Note Added: 0056599
Mar 23, 2020 11:31 pm Rose Note Added: 0056600
Mar 24, 2020 12:04 am BadgerBadger Note Added: 0056601
Mar 24, 2020 12:05 am BadgerBadger Note Edited: 0056601 View Revisions
Mar 24, 2020 12:06 am BadgerBadger Note Edited: 0056601 View Revisions
Mar 24, 2020 12:06 am BadgerBadger Assigned To => BadgerBadger
Mar 24, 2020 12:06 am BadgerBadger Status new => closed
Mar 24, 2020 12:06 am BadgerBadger Resolution open => no change required