View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0018895 | AI War 1 / Classic | Gameplay Issue | Aug 24, 2016 1:28 pm | Aug 24, 2016 1:28 pm | |
| Reporter | tadrinth | Assigned To | |||
| Status | new | Resolution | open | ||
| Product Version | 8.023 | ||||
| Summary | 0018895: Warp Jammers should jam Raid Engines for increased Nomad usefulness | ||||
| Description | In my current game, a Spire Archive spawned on a Nomad. That was exciting, because it meant I could capture the Archive unusually early once it wandered into my territory. I put a warp jammer on it to avoid having to soak waves there as it wandered around. Then after I captured it, it wandered next to an AI homeworld... where to my surprise, it promptly triggered a raid engine. I thought Warp Jammers blocked Raid Engines, but it turns out they don't. Even if I'd scrapped everything on the planet, even an empty non-AI-controlled planet will set off a raid engine. Even with every turret I had unlocked parked on the nomad, I would lose the planet... which still wouldn't stop the waves. I guess this is the sort of exciting emergent interaction that Nomads are supposed to offer... but in practice, I'm just not going to capture Nomads if there's a risk of them wandering into Raid Engine range. I don't know how unbalanced it would be for Warp Jammers to block Raid Engines, but that would be my preferred solution. Seems more intuitive. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Aug 24, 2016 1:28 pm | tadrinth | New Issue |
