The Smuggler
From Halo
"The Smuggler"
|
(note: year calculations of timestamps made using 365.2422 earth 24hr-days per arbitrary 'year')
Phase 1
May 30, 2008
- a new set of text was posted in a Bungie.net weekly update:
T-0: Containment Failure
T~8min -
REPORT: CONTAINMENT FAILURE
LF.Xx.3273 research and containment facility; [delta site] has experienced catastrophic specimen containment failure. All apertures into facility will be locked until further notice. Atmosphere evacuation and [reduction of ambient temperature] protocols have already been enacted. Request maintenance and security detail [at earliest opportunity]. [8 minutes] elapsed since initial containment failure.
T~40min 9sec -
REPORT: CONTAINMENT FAILURE
Waiting for maintenance and security detail. [32 minutes, 9 seconds] elapsed since request.
T~24hrs 8mins -
REPORT: CONTAINMENT FAILURE
Still waiting for maintenance and security detail. [24 hours] elapsed since request.
T-286 yrs, 221 days, 5:46:27.12 -
REPORT: SECURITY BREACH
LF.Xx.3273 research and containment facility; [delta site] has experienced a security breach via emergency [slip stream space] transportation conduits. Emergency [slip stream space] transportation conduits have been placed in recursive mode to contain unauthorized hostile lifeforms. Request emergency security detail. Still waiting for primary maintenance and security detail. [2512332 hours, 14 minutes, 6 seconds] elapsed since initial request.
T-?? -
REPORT: DERELICTION OF DUTY
2401 [PENITENT TANGENT] has been lax in the areas of maintenance and security.
- LF.Xx.3273 is the code for the Flood cell type (the Gravemind ID)
- "REPORT" indicates these are messages being sent likely to Installation 00 (the Ark)
- This could the sequence of events taking place after the initial Delta Halo flood outbreak.
June 6, 2008
- In another Bungie weekly update:
T-99,713 yrs, 143 days, 18:21:10.96 - Since Forerunner firings? (+/- 7yrs, 00:12:39.44)
LOG: QUERIED ADJACENT FACILITIES
LF.Xx.3273 research and containment facility [alpha, beta, gamma, epsilon, zeta, and kappa sites] have all replied [systems normal] within expected constraints. This would tend to signify that the containment failure was purely mechanical in nature; perhaps a manufacturing flaw. As no [outside agent] has accessed [delta site] in the past [874068942 hours, 4 minutes, 46 seconds][allowing for a 61360 hour, 54, minute, 2 second margin of error]sabotage would seem unlikely.
T-?? -
LOG: REQUEST UNANSWERED
LF.Xx.3273 research and containment facility; [delta site] is currently being held at [.01 atm] / [184K]. Local maintenance and security hubs have failed to reply within expected constraints. [Bumping maintenance and security request up] to [quadrant oversight].
T-?? -
LOG: REQUEST UNANSWERED
LF.Xx.3273 research and containment facility; [delta site] is currently being held at [1 atm] / [278K] as atmospheric seals were showing signs of stress. [Quadrant oversight] has failed to reply within expected constraints. [Bumping maintenance and security request all the way up] to 2401 [PENITENT TANGENT].
T-?? -
LOG: UNAUTHORIZED ACCESS TO FACILITIES
LF.Xx.3273 research and containment facility; [delta site] emergency [slip stream space] transportation conduits have been accessed by unauthorized parties.
T-?? -
LOG: FILED COMPLAINT TO INSTALLATION 00
2401 [PENITENT TANGENT], monitor of Installation 05, has been lax in the areas of maintenance and security. Requests for aid in said areas have gone unanswered by both 2401 and [subservient] systems well beyond expected constraints.
- "LOG" indicates events described locally
- These LOG/REPORT segments may be ordered chronologically, even overlapping, describing the same containment failure event.
- Initial atmospheric adjustments: 1/100th atmospheric pressure, 184K = -89C = -128.2F
Priority bumped to "quadrant oversight" - Atmosphere re-adjusted: 1 atmospheric pressure, 278K = 5C = 41F
Priority bumpted to "2401 Penitent Tangent"
Chronology calculations
- The final REPORT is timestampted 286 yrs, 221 days, 5:46:27.12 after containment failure.
The first LOG occurred at 99,713 yrs, 143 days, 18:21:10.96 (+/- 7yrs, 00:12:39.44) after ring-firing.
IF the first LOG was made at T-0 (containment failure), then- 99713,143,18:21:10.96 + 286,221,5:46:27.12 = 99999yrs, 364days, 23:67:38.08
- or 5:41:08 short 100,000 years, +/- 7yrs, 00:12:39.44
- (1.2422 days short of 1 year. 1.2422 days = 107326.08s. 23:67:38.08 = 86858.08s. Difference = 20468s = 5h 41m 8s short of 100,000 years)
- 99713,143,18:21:10.96 + 286,221,5:46:27.12 = 99999yrs, 364days, 23:67:38.08
Conclusion:
- The final timestamped REPORT was made 5h, 41m, 8s before precisely 100,000 years since the ring firings (rather, since "[outside agent] has accessed [delta site]")
- Add the period of time (if any) between "Containment failure" (T-0) and initial LOG entry.
- With a margin of error of 7 years, 12m, 39.44s
- (all year calculations based on 365.2422 days per year - earth days and earth years)
Theories
- One theory is this is a viral-ish promo for the upcoming Halo map "Smuggler"
Official Revelation
lukems posted on bungie.net that indeed "The Smuggler" is referring to a new Halo 3 map "Cold Storage":
Posted by: CrypticGuardian ]Luke said "Smuggler" was the code name for Cold Storage. It will be included, along with Purple Reign and Moonbase Alpha, in the next map pack.
The first sentence is a fact. The second one is an incorrect assumption ;b
- More info on Cold Storage here
Phase 2
June 27
- At the end of another weekly update (link), even interrupting the last paragraph:
- Fourth of July – A collection of Flag, Rockets, and VIP. 5v5.
- [SPURIOUS INTERRUPT: PACKET LOST - ERROR CODE 5929]
- Fiesta – FFA featuring random weapon spawns. 8 Players.
- Grifball – Updated to use the Summer League map. 4v4.
- Team Snipers – No changes from June. 4v4.
- Team Melee – Sword and hammer-centric slayer and
*/PACKET INTERRUPTION ERROR CODE 5929 */
Attempting Recovery
Attempting Recovery
*/ 93% PACKET CORRUPTION RECOVERY UNSUCCESSFUL - DISPLAYING */
C!#4x---^&-$x%^^p3@
Head2@!#SWa#++-DL*SLAj3r
48hr0x0ABFFFFF [ERR 5929]
*/ END DISPLAY */
Notes:
- Error code: 5929
- Head2
- 48hr