The Galbadian Missile Base

Story mode. Written for a first playthrough and kept free of spoilers — it will not tell you what happens here, only what the game is asking of you.

You are in disguise. Keep it.

Keeping the disguise

Two moments matter:

• The maintenance guards. You can walk past quietly or talk your way out. Both work. Choosing to fight blows your cover, starts a battle and costs you rank.
• The soldier at the missile bay. Play it cool, then help out. That is what gets you access to the console. Refusing reportedly switches random encounters back on for the rest of the building.

The console — do this right

At the control panel: Target → Set Error Ratio → hold right until it is at maximum → Data Upload → confirm.

This is not a “worse ending” choice. Getting it wrong is a game over. Four separate guides say so. Max it.

The timer is yours

Afterwards you set the base’s self-destruct clock yourself. Ten, twenty, thirty or forty minutes.

Here is the thing almost nobody leads with, and it changes the decision completely:

Picking ten or twenty opens a shortcut door. Thirty and forty leave it locked and make you walk the long way round. So the short options are not just braver — they are shorter routes. You are not trading safety for score; you are getting both.

Three sources agree on this. One source says the longer you pick the better, which is the opposite of everything else written about this area.

Take ten if you are confident, twenty if you are not. Do not take forty because it sounds safe.

Getting out

The clock keeps running through the fight at the end. That has one very practical consequence:

Do not summon. Summon animations are long and the clock does not care. Three sources say the same thing, and it is specific to this fight rather than general advice.

The machine at the exit takes extra damage from Thunder, Earth and Water — three separate openings, so you almost certainly have one of them. It is immune to Poison and Demi does nothing to it at all.

Its ordinary attack is physical and hits often, so blind it — that shuts down most of what it does. Its big beam attack is magic, ignores Shell, and there is no answer to it except killing the thing faster.

Do not bother stealing from it. It carries nothing — no steal, no drop. The fight pays ability points and that is all.

Fight the soldiers that turn up afterwards. A magazine comes out of that, not out of the machine, and it is one of only two issues of that magazine you can permanently lose.

Before you go: the hidden draw point

There is an invisible draw point in the missile bay holding one of the strongest junction spells in the game. Two guides call it the thing people miss here.

This building is destroyed. Everything in it — three draw points, the magazine, all of it — is gone permanently. There is no coming back to check.

Game Notes

This is the only place in FFVIII where you set your own difficulty and get scored on it, and the design of that choice is better than it looks.

On the surface it is the obvious risk-reward dial: less time, more points. Fine. But the short options also unlock a shortcut door, which means the ten-minute run is not ten minutes of the same journey — it is a different, shorter journey. The game quietly makes the brave choice the easy one, and does not tell you.

Which means the honest advice inverts what the presentation implies. A cautious player reads “forty minutes” and thinks safety; they are in fact choosing the longest route, the worst score, and the same boss fight at the end. The forty-minute option is a trap made entirely out of reassurance.

I have some sympathy for the one guide that says pick the longest. If you had never noticed the door, that is exactly the conclusion the numbers on screen would lead you to.

It is also the only fight in the game so far where the correct tactic is not the strongest one. Summons hit harder than anything you can cast here. You should not use them, because the clock is a resource and the animation spends it. That is a real tactical texture, and it exists precisely once.

Completionist mode. Full spoilers, in play order, with every permanent loss called out before you reach it. 10 entries below are marked where our sources disagree with each other — we have not picked a winner for you.

Spoilers from here.

The error ratio

Target → Set Error Ratio → hold right to maximum → Data Upload → Yes.

Four sources confirm that failing to max it is a game over, not a lesser outcome.

One lore wrinkle worth stating rather than flattening: the Wiki’s page on the missiles says they home in on Balamb Garden regardless of the error ratio, and that Garden survives because it had already moved off the programmed coordinates. Walkthroughs uniformly imply the sabotage is what saves it. Both are compatible — the sabotage is what keeps you playing; the in-fiction survival is about Garden having moved.

The timer

Ten, twenty, thirty or forty minutes, set at a panel above the control room. The clock starts immediately and runs through the escape and the boss fight.

Three sources agree that ten or twenty opens a shortcut door on the right of the screen, giving a direct route to the front of the base; thirty and forty leave it locked. So the shorter settings are also the shorter routes.

Four sources recommend ten. One recommends twenty for margin. One guide says the longer the better — which is the reasonable conclusion if you have not noticed the door.

Rank cost, single-sourced: none at ten minutes, −15 at twenty, −45 at thirty, −75 at forty. If those figures are right, this is the largest single rank swing in the chapter.

The disguise

One source quantifies the scoring: avoiding combat before the control room is worth around 105 points of avoided penalty, and a wrong answer to the hangar soldiers costs 7. Nobody else gives numbers.

• Maintenance guards: walking by quietly or talking your way out both avoid the fight with no penalty. Choosing to fight blows the disguise, triggers two soldiers and costs rank.
• Missile bay soldier: play it cool, then help out — that is the route to the control panel. Refusing reportedly re-enables random encounters for the rest of the base.
• One source notes that if your cover was already blown, you lose extra time consulting a wounded soldier to get console access — which eats the clock you are being scored on.

BGH251F2 — settled

Zero EXP. 20 AP. Immune to Poison, flagged immune to Gravity, and takes 150% from Thunder, Earth and Water. Its draw list — Shell, Protect, Stop — is identical at every level band, which is unusual.

It has no steal table and no drop table. Both are empty in all three bands, so Mug returns nothing however long you spend on it and the fight pays AP and nothing else. That is worth stating because one guide lists steals in this base and nobody else does.

Correction 1 — seven figures, one curve

Published: 4,200–8,400 over levels 1–22 (four sources) · 6,000–8,400 over levels 9–22 · a flat 6,000 · a flat 8,200.

The four-source range is exactly right. The flat 6,000 is that curve at level 10. The flat 8,200 is it at level 21. Nobody is wrong.

Correction 2 — 20 AP, not zero

One guide states 0 AP and 0 EXP. Zero EXP is correct; 20 AP is correct.

The Wiki offers a plausible explanation for how somebody recorded zero: it says the AP is only awarded if the machine is actually destroyed rather than withdrawing with HP remaining. A writer who let it retreat would have seen nothing.

Correction 3 — there are two of these machines, and they are not the same enemy

This is the one that explains the rest of the noise. The game stores two separate records under this name.

They agree at level 10 and diverge after it, and they have different Water resistances. Guides quote them interchangeably — which is why the same name attracts a ten-percent spread in HP figures and two different elemental tables depending on which page you open.

The loot is the cleaner tell. One of these two records carries nothing at all and the other carries a top-tier weapon component and a guaranteed stack of Quistis’s Blue Magic material. That is not a ten-percent difference you could read as level scaling; it is present or absent. Any page that tells you to steal from the machine at the missile base is describing the fight in Fishermans Horizon.

Tactics

Do not summon. Three sources, and it is specific to this fight: the countdown runs through the battle and Guardian Force animations are long.

Blind it — two sources. Its autocannon is physical and frequent; the beam is magical, reportedly ignores Shell, and has no defensive answer.

Draw points, all destroyed with the base

• Blind, early, under the stairs near the save point.
• Blizzara, circuit room. One walkthrough instead names it Thundara and places it near a guard.
• Full-Life, missile bay, left side. Two sources flag it as hidden and invisible; two describe it plainly. It is the most commonly missed thing here and one of the strongest junction spells in the game.

That same walkthrough claims a fourth draw point in the boss arena containing Shell, Protect and Stop — every other source treats those as the boss’s own draw list, which is almost certainly what it is.

A Confuse draw point appears on the ruins afterwards, single-sourced. The only thing left standing.

Weapons Monthly, June

Two sources specify it only appears if you also defeat the soldiers that emerge after the machine is down, and both describe it as a drop.

It is not a drop. No enemy anywhere in the game carries a magazine in a steal or drop table — not one, across all 142 records — and this machine’s own tables are empty in both columns. So the June issue is an event handout attached to finishing the extra fight, which puts it in field-script territory and out of reach of anything we can settle from the enemy data. Fight the crew regardless: one source identifies March and June as the only two permanently missable Weapons Monthly issues in the game.

Game Notes

Two of these machines exist in the game’s files under one name, with different HP curves and different Water resistances, and they happen to coincide at level 10.

I want to sit on that for a moment, because it is the most complete explanation this project has produced for why FFVIII’s guides look the way they do.

Consider what a careful writer experiences. They fight the machine here, at roughly level 10, and record 6,000 HP. Later they fight a machine with the same name, again at roughly level 10, and record 6,000 HP. Consistent. Confirmed. They publish a stat block.

Another equally careful writer fights the first one at level 20 and gets 8,000, and the second at level 20 and gets 7,000, and now has two irreconcilable numbers for what the game has told them is one enemy. They pick one, or they publish a range, or they average it.

Nobody in that story did anything wrong. The game presented two enemies under one name, scaled both to the observer, and arranged for them to agree at exactly the level most players would meet the first one.

We have now found three distinct mechanisms producing apparent disagreement in this game: level scaling (the HP curves), party branching (the Deling sewer magazine), and now name collision (this). None of them is carelessness. All of them are invisible from inside a playthrough.

That is the case for this whole vertical in one paragraph. Not that other guides are bad — most of them are the product of far more hours than I have put in — but that FFVIII is a game where honest observation systematically produces contradictory records, and the only way out is to read what the disc actually says.