Building Maintenance: Air Conditioning: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
'''Data leaks will be occuring next on Wednesday, 21:30-22:00 GMT! | '''Data leaks will be occuring next on Wednesday, 21:30-22:00 GMT! | ||
Learn how to crash the system and hit it hard at that time!''' | Learn how to crash the system and hit it hard at that time!''' | ||
Enter your findings on | Enter your findings on | ||
[[Ascendancy Point Residents]] | [[Ascendancy Point Residents]] |
Revision as of 14:39, 5 September 2005
Data leaks will be occuring next on Wednesday, 21:30-22:00 GMT! Learn how to crash the system and hit it hard at that time!
Enter your findings on Ascendancy Point Residents
This page is in reference to the A.C. systems at Ascendancy Point.
See also: Disaster Maintenance: Heat Sensors
Location
The Advisor installed a back door, as stated in Salklogs.doc, allowing access to "Ascendency Point Disaster Maintenance: Heat Sensors." Access was attained by Puzzled Pineapple, who posed as The Advisor. Many other people attempted to gain access as well. Most commonly people were directed to Alex Mitchell and Rajiv Warner and a mysterious T-980 form. Puzzled Pineapple was informed the Air Conditioning system should be available "within 48 hours."
URL: http://ascendancypoint.com/eclipsesecurity/building/ac/
Username: theadvisor
Password: thelimelife
Usage/Facts
- This is a randomly created simulator of internal climate control systems.
- It is not actual data from within Ascendancy Point; it is only a test environment.
- It does however link to data within the point like the usual systems and so can experience bugs
- If all temperature sensors get above or below 12 degrees, the system will crash.
- Usually Cooling fans have more efficient output than heaters.
- Between 21:30 and 22:00 GMT (10:30pm and 11:00pm BST), Sunday, Friday and Wednesday
Each time the system crashes, it becomes possible for us to see the Name, Floor No. and Room No. of one resident of Ascendancy Point. This is seen in the crash window.
The above is a print screen of a program crash when the server maintenance is not being carried out (ie. when the program crashes NOT at the specified time)
Maps
- Each system map, being a simulation, is generated randomly. So there are no maps.