You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in or create an account, your edits will be attributed to your username, along with
other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision |
Your text |
Line 16: |
Line 16: |
|
| |
|
| I don't think this should be classified as an Easter Egg. It's not a silly thing the developers placed in the game for the players to find, it's intent is to provide extra information about the surrounding plot of the game.--{{User:Spartacus/Sig}} 11:38, 4 January 2014 (EST) | | I don't think this should be classified as an Easter Egg. It's not a silly thing the developers placed in the game for the players to find, it's intent is to provide extra information about the surrounding plot of the game.--{{User:Spartacus/Sig}} 11:38, 4 January 2014 (EST) |
|
| |
| == Speculation on the Composer audio logs ==
| |
| Is there any way to verify the timelines for some of the Composer audio logs that don't have a stated date? Based on the available information:
| |
| * Phosphorus test / Artifact test - Some people got digitzed when the Composer suddenly activated. I can't say for certain which audio log comes first. Also I don't if this happened in 2554 when the Composer was first excavated or in 2557 at Ivanoff Station.
| |
| * Ceased transmission - The Composer stopped transmitting something around 0900 on the 21st. Could this be the July 21, 2557 date when the Ur-Didact was released from the cryptum in the Halo 4 campaign? Also, the transmission could be the Composer's coordinates to help the Ur-Didact locate it after crashing the USS Infinity inside Requiem.
| |
| * Something big - Something big is happening outside Ivanoff Station. This could be the Halo 4 Composer mission during the July 24, 2557 date.
| |
| [[User:S.g.ali|S.g.ali]] ([[User talk:S.g.ali|talk]]) 02:01, May 30, 2022 (EDT)
| |