Technical problems

From Halo
Revision as of 03:06, 17 August 2007 by Thebruce (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Technical problems

Listed below are various technical issues reported by users during the Iris campaign. This is a note for reference for players and improvement (for the puppetmaster team?).


(include other past issues here)

Server 04
  1. The server status page discovered a while back that's used to inform about the locked/unlocked status of the 5 server began reporting that Server 4 was pending, and 0/100 keys had been found.
  2. Hot on the new trail, players scoured for anything and everything that could be considered a clue to the new BPC location
  3. IP scanning revealed that 206.16.223.76 now contained available content called "Artifact Location"
  4. Inconsistently, the server status page returned ASP.net server errors, as well as the standard Windows Live login location that previous Servers had used.
  5. Players hacked the flash code on the Artifact Location page to find the required password. The result was the password for the "Artifact Location" but ultimately led to a dead end at the moment.
  6. THEN a new post on Jonas' book's Amazon page by Thomas Sanatos indicated the next step to finding the BPC page.
  7. Steps proceeded seemingly as expected to arrive at the BPC page. However, the ASP server errors had not ended.
  8. Many users who had arrived at the BPC page ended up at a dead end after receiving a key, since the Live ID login process occurs after that point. Repeated attempts to login failed due to the server error
  9. It was unknown that simply closing the browser and re-opening it would correct the problem. By that it was too late, for sufficient other users who did not receive the error were able to enter their keys first. This obviously upset a large number of players who felt they were 'shafted', because they would have been succesfully among the first 100 had there been no server error.
  • Also note that due to this issue as a whole, the 206.16.223.76 website was found prematurely - the password for the flash was intended to be found through the server 4 content, not via hacking the flash. The intended determination of the IP address is unknown at this point.
Server 05
  1. When the first coordinates appeared on the artifact location site at 12:13am EDT, they listed:
    New York - 40.75908 -73.98619 (46th and Broadway)
    Seattle - 47.61440 -122.32059 (Broadway and Pike)
    Los Angeles - 40.30609 -121.00434 (in Westwood, CA)
  2. The LA coordinate seemed odd, since it was in the town of Westwood, quite far from Los Angeles itself.
  3. After a hectic period of determining addresses and who were in the cities and able to travel to those locations at that time of night, there was a change...
  4. At 1:01am EDT (almost an hour late), the Los Angeles coordinates were updated to:
    Los Angeles - 34.05099 -118.43814
    A more reasonable location back in Los Angeles, on Westwood Blvd. (someone messed up the Westwood name)
  5. 2 minutes later the first key was claimed. Over the next 19 minutes, 4 more were claimed, before the link was posted, reported by a player in Seattle, after which time the remaining 95 keys were claimed in under 2 minutes - the server opened at 1:23am EDT
  6. At 1:30am EDT, the location for New York was also updated, to:
    New York - 40.75006 -73.99785
    About 16 block away from the original location, and too late to be of any help
  7. Seattle was the only location with accurate GPS coordinates from the start. It's no wonder the URL was reported from a player at that location.
Personal tools
misc game content
[Support Wikibruce]