- changed status to open
TIEs are not destroyed when disabled
Issue #60
resolved
Original X-wing behavior had TIEs blow up when disabled. I'm actually ok with this feature not being implemented since it was removed for XvT balancing, but its something to consider since it is easier to take out T/Is and T/Bs with ions than lasers.
Comments (15)
-
-
reporter
I do want to add that it does make it easier for the player if TIEs aren't destroyed when disabled. It prevents additional waves from spawning and would allow players to easily destroy Star Destroyers. Not that they weren't easy to destroy in the first place with the whole shield gen thing.
-
Actually this can be circumvented by the mission checking for active craft. If no active craft are present, send the next wave?
-
- changed status to resolved
Fixed: Issue
#60: TIEs are not destroyed when disabled Fixed: Issue#153: Engine at Zero on Mission Restart Fixed: Issue#172: [General] Briefing shows text from instructions box→ <<cset 9ec01ee3b39d>>
-
reporter
TIEs are still not destroyed when disabled.
The only exception is the T/A.
-
reporter
- changed status to open
-
reporter
changed priority since it can absolutely change balance in missions.
-
This issue was solved by applying Feipan's suggestion: - TIEs are disabled as any other craft. - If all TIEs left in a wave are disabled, then the next wave is sent.
This should keep balance (you cannot stall TIEs' reinforcements by disabling them) at the same time that it evens out X-wing behavior with later games in the series. Is this a wrong solution?
-
reporter
If we keep this mechanic, then we set a precedent to the player that disabling ships will not prevent waves. Which the developers developed around this mechanic throughout the series. Simply having them self-destruct is fine since it tells the player that another wave will becoming because they were destroyed, as opposed to confusing the player.
-
I'd be inclined to agree that self-destruct, for those specific craft types only, is probably the way to go. It preserves game balance and authenticity with the original. Where the balance comes in is when you have AI wingmen with disable orders that are attacking enemies - in which case they will be using ions.
You can also end up with a situation where if multiple waves of the same craft, you could potentially have a number of craft named exactly the same (e.g. three T/F Alpha 1's), which as Justagai mentioned could be confusing for players.
Would this only apply to the X-Wing ruleset, or does this exist in TIE Fighter and later too? (I don't recall seeing this behaviour in any of the other games)
-
reporter
-
Haha, I guess that answers that question, then. :-)
(Yes, TIEs still get destroyed when disabled in TIE Fighter)
-
If we keep this mechanic, then we set a precedent to the player that disabling ships will not prevent waves. Which the developers developed around this mechanic throughout the series. Simply having them self-destruct is fine since it tells the player that another wave will becoming because they were destroyed, as opposed to confusing the player.
I agree with this opinion. Being able to disable TIEs will make the game illogical, as to why waves are prevented or not prevented depending on the craft. The solution of the original game was ideal. If it ain't broke, don't fix it.
-
Perhabs an option for (non) self-destructing TIEs could become part of the Balance Settings Menu I proposed in issue #240
-
- changed status to resolved
Fixed: Issue
#60: TIEs are not destroyed when disabled→ <<cset 8ae3826a20a1>>
- Log in to comment
This is more like a feature than a bug. But the consequences of this need to be evaluated. If it breaks missions or make them too easy, we should revert to the original behavior or make this optional. Since Ions are way slower than lasers, it should be harder to disable TIE Interceptors with them, though.