Terminal Overload: Difference between revisions

From Destinypedia, the Destiny wiki

(Created page with "{{Public Event infobox |name= Terminal Overload |image= |light= |place=Zephyr Concourse, Neomuna <br> Ahimsa Park, Neomuna <br> Límíng Harbor, Neomuna |enemies=Cabal <br> Vex |objective= Stop the Shadow Legion from hacking into the CloudArk and weakening its defenses }} '''Terminal Overload''' is a Guardian-initiated activity that can be triggered as a Public Event on Neomuna, similar to Escalation Protocol, Court of Oryx an...")
Tag: Mobile edit
 
Tag: Mobile edit
Line 34: Line 34:
*Despite being advertised as a 6-player activity, much like [[The Wellspring]] from [[The Witch Queen]], it appears as a public event instead. Why this change happened is unclear.
*Despite being advertised as a 6-player activity, much like [[The Wellspring]] from [[The Witch Queen]], it appears as a public event instead. Why this change happened is unclear.


==List of appearances==
==Appearance==
*''[[Destiny 2]]''
*''[[Destiny 2]]'': ''[[Lightfall]]'' {{1st}}
*''[[Lightfall]]'' {{1st}}


==References==
==References==

Revision as of 23:14, May 5, 2023

Terminal Overload

Location:

Zephyr Concourse, Neomuna
Ahimsa Park, Neomuna
Límíng Harbor, Neomuna

Enemies:

Cabal
Vex

Objective(s):

Stop the Shadow Legion from hacking into the CloudArk and weakening its defenses

Destinypedia doesn't currently have a walkthrough for this public event, could you write it?

 

Terminal Overload is a Guardian-initiated activity that can be triggered as a Public Event on Neomuna, similar to Escalation Protocol, Court of Oryx and the Blind Well, where a team of Guardians engage both Shadow Legion and Sol Collective forces in an attempt to protect the CloudArk from hacks.

Gameplay

This section needs expansion. You can help Destinypedia by expanding it.

Enemies

Cabal - Shadow Legion
Vex - Sol Collective

Bosses

Phase 1
Phase 2
Phase 3

Trivia

  • Despite being advertised as a 6-player activity, much like The Wellspring from The Witch Queen, it appears as a public event instead. Why this change happened is unclear.

Appearance

References