2. Redesigning Rogue VI

Overview

UNC: Rogue VI is a vanilla Mass Effect assignment. Diversity enhances its Luna environments with visual improvements, additional logs, and environmental storytelling elements such as dead bodies. Those additions make the facilities feel more inhabited and provide more context, but they do not substantially change the assignment's plot or the decisions available to Shepard.

Ghost in the Machine is a complete overhaul of the vanilla assignment. It uses Diversity's environmental improvements as its foundation, preserves the parts of that work that remain compatible with the revised scenario, and replaces the original quest progression with a more developed encounter involving the intelligence later identified as Hannibal.

This distinction affects both the design and the implementation:

• The vanilla assignment supplies the original quest, locations, enemies, and plot infrastructure.
• Diversity supplies the version of the Luna environment on which our package is based.
• Ghost in the Machine overrides Diversity's affected packages, preserves its compatible additions, and supplies the new plot state and quest behavior.
• The Ghost in the Machine DLC must mount above Diversity because package overrides are resolved as complete files rather than automatically merged at runtime.

Before defining new plot variables, we need to understand the story state those variables will represent.

Original plot

In the vanilla assignment, the Alliance sends Shepard to Luna after a training VI begins behaving unpredictably. The facility consists of three bunkers containing hostile combat drones and destructible infrastructure.

Shepard can enter the bunkers in any order, destroy the hostile synthetics, and disable the VI by destroying the designated conduits or power-system components. The repeated bunkers function primarily as combat spaces; clearing one does not meaningfully change the others or develop the intelligence as a character.

Near the end, the failing intelligence communicates through a text message containing binary that translates to a plea for help. Shepard is not given a meaningful opportunity to investigate that plea, communicate with the intelligence, or decide whether it should survive. Completing the destruction ends the assignment and unlocks Shepard's specialization-class selection.

Diversity adds environmental detail and supporting material to these locations, but the player still follows substantially the same progression and reaches the same required conclusion.

Revised plot

Ghost in the Machine reverses the original premise. The intelligence was not merely a training VI that spontaneously became dangerous. It is Hannibal, an experimental Alliance military intelligence whose creators believed it could help humanity compete in a hostile galaxy.

Before Shepard arrives, a covert anti-AI operation has already attacked the Luna facility and disabled most of Hannibal's capabilities. Personnel who might have restored it were killed to prevent them from revealing or undoing the operation. Admiral Ines Lindholm preserved a concealed functional layer of Hannibal and hid three recovery modules at protected lunar heritage sites outside the facility network.

The Alliance sends Shepard to complete the shutdown without telling her the full history of the first operation. Shepard can explore the three exterior recovery sites, clear the three bunkers, and install the recovered modules in any order. Each module restores a bounded Hannibal capability with a visible effect on the remaining gameplay, allowing installation order to change the experience of later bunkers.

The first established module controls the facility shield network. Installing it allows Hannibal to suppress shields that would otherwise obstruct Shepard. A second module will affect drone behavior. The third module must provide another limited and visible capability without independently granting Hannibal full agency.

Hannibal initially communicates through damaged or corrupted messages. Its responses become more coherent as Shepard restores its systems, turning the repeated facilities into stages of a developing exchange rather than three interchangeable combat spaces.

Installing all three modules completes Hannibal's reconstruction and fully actuates the intelligence. Shepard must then make the assignment's final decision through action:

• Destroy the newly vulnerable AI housing, with Hannibal appealing to Shepard as it takes damage.
• Leave the housing intact and allow Hannibal to survive.

If Shepard destroys Hannibal, she has completed the substance of the Alliance's original order. If Shepard preserves it, Hannibal contacts a Cerberus recovery team but also detects that the anti-AI response force has been activated again. Hannibal tells Shepard to leave, both because it can now defend itself and because remaining would place her in danger.

The specialization reward remains deliberately uncomfortable in either outcome. Shepard receives the promotion with an expectation of discretion: if she destroyed Hannibal, the message acknowledges completion; if she preserved it, the Alliance assumes that whatever required attention on Luna has been handled. In both cases, the reward carries the implication that public knowledge of the mission would complicate matters.

A later return to a post-attack Luna or a second Cerberus phase may be added in the future, but neither is required for the first complete release. The initial plot must end coherently with Hannibal either destroyed or preserved.

From narrative design to plot state

This tutorial presents the revised narrative first and then shows how that design is represented by plot variables, transitions, conditionals, and quest records. That clean sequence is useful for explaining the finished structure, but it is not the order in which the design originally developed.

Development was iterative. We began with small, relatively isolated changes such as revising and adding log entries. That work allowed us to explore Hannibal's history, the earlier attack on the facility, the hidden recovery modules, and Shepard's incomplete briefing before committing those ideas to plot infrastructure.

The quest flow changed repeatedly during that process. Early versions gated access to the bunkers behind module recovery. Another version treated one module as an actuation module. Later revisions kept the bunkers open, gave each module a limited gameplay effect, and separated module installation from Shepard's final decision about whether Hannibal should survive.

Working first at the narrative level allowed weak assumptions and unnecessary mechanics to be revised without repeatedly rebuilding the quest's underlying state model. Only after the background story, player progression, module functions, and final decision were sufficiently understood did we define the persistent plot state needed to represent them.

The implementation that follows therefore describes the current result of that iterative process. It should not be read as a rule that plot variables must be designed before any writing, environmental work, or experimentation begins. In practice, narrative design and technical investigation inform one another.