**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

There are dirty vars in the map! Read the logs above! → @@@code/unit_tests/map_tests.dm:355

Unit Test runtimed or returned an illicit result: MAP: No Dirty Vars → @@@code/unit_tests/ss_test.dm:188

**** [3] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

There are dirty vars in the map! Read the logs above! → @@@code/unit_tests/map_tests.dm:355

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

**** !!! Encountered a world exception during unit testing !!! - Exception name: Subsystem Odyssey(/datum/controller/subsystem/odyssey) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu. → @@@ code/controllers/master/subsystem.dm:134 **** → @@@code/unit_tests/ss_test.dm:270

**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: yogstation13/DreamAnnotate@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Recipe 'regular floor tile' on material 'holosteel' creates product with material 'steel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Recipe 'metal rod' on material 'holosteel' creates product with material 'steel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Recipe 'makeshift magazine (5.56mm)' on material 'holosteel' creates product with material 'steel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Recipe 'dark floor tile' on material 'plasteel' creates product with material 'plasteel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Recipe 'full dark floor tile' on material 'plasteel' creates product with material 'plasteel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Recipe 'dark floor tile' on material 'titanium' creates product with material 'plasteel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Recipe 'full dark floor tile' on material 'titanium' creates product with material 'plasteel', but that material is not required by the recipe. → @@@code/unit_tests/recipe_tests.dm:63

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

intercom_listener created with QDELETED intercom!

AME sector somehow created without a parent control unit! in code/modules/power/antimatter/shielding.dm at line 41 src: the antimatter reactor section usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

intercom_listener created with QDELETED intercom!

AME sector somehow created without a parent control unit! in code/modules/power/antimatter/shielding.dm at line 41 src: the antimatter reactor section usr: .

Non-buildable or Non-magical SMES at 105X 133Y 1Z

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Non-buildable or Non-magical SMES at 105X 133Y 1Z

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Non-buildable or Non-magical SMES at 105X 133Y 1Z

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Not spawning ruins for Fryer-India, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Not spawning ruins for Callirrhoe-Golf, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Not spawning ruins for Fryer-India, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Not spawning ruins for Fryer-India, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Not spawning ruins for Callirrhoe-Golf, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Non-buildable or Non-magical SMES at 122X 130Y 24Z

Not spawning ruins for Fryer-India, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Not spawning ruins for Fryer-India, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Not spawning ruins for Callirrhoe-Golf, a mineral asteroid because 'exoplanets_ruins' is FALSE in the UT config

]Timer: -1 ([0x2102b9bf]), TTR: 594.28, wait:5.28 Flags: TIMER_UNIQUE, TIMER_OVERRIDE, callBack: [0x21033cea], callBack.object: The threshbeast[0x3000ab5](/mob/living/simple_animal/threshbeast), callBack.delegate:stop_bleeding(), source: code/modules/mob/living/simple_animal/simple_animal.dm:723 usr: .

]Timer: -1 ([0x2102b995]), TTR: 594.28, wait:5.28 Flags: TIMER_UNIQUE, TIMER_OVERRIDE, callBack: [0x2102b9c0], callBack.object: The threshbeast[0x3000ab5](/mob/living/simple_animal/threshbeast), callBack.delegate:stop_bleeding(), source: code/modules/mob/living/simple_animal/simple_animal.dm:723 usr: .

]Timer: -1 ([0x21033cea]), TTR: 594.28, wait:5.28 Flags: TIMER_UNIQUE, TIMER_OVERRIDE, callBack: [0x2102b9bf], callBack.object: The threshbeast[0x3000ab4](/mob/living/simple_animal/threshbeast), callBack.delegate:stop_bleeding(), source: code/modules/mob/living/simple_animal/simple_animal.dm:723 usr: .

]Timer: -1 ([0x2102b994]), TTR: 594.28, wait:5.28 Flags: TIMER_UNIQUE, TIMER_OVERRIDE, callBack: [0x2102b9c6], callBack.object: The threshbeast[0x3000ab4](/mob/living/simple_animal/threshbeast), callBack.delegate:stop_bleeding(), source: code/modules/mob/living/simple_animal/simple_animal.dm:723 usr: .

Non-buildable or Non-magical SMES at 139X 132Y 22Z

Non-buildable or Non-magical SMES at 135X 130Y 33Z

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer: -1 ([0x2105aa94]), TTR: 594.21, wait:10.23 Flags: , callBack: [0x2105aa93], callBack.object: IHGV Sinta Pride[0x2105aafb](/datum/overmap_contact), callBack.delegate:unping(), source: code/modules/overmap/contacts/_contacts.dm:80 usr: .

Non-buildable or Non-magical SMES at 139X 132Y 22Z

Non-buildable or Non-magical SMES at 135X 130Y 33Z

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Non-buildable or Non-magical SMES at 70X 112Y 4Z

Ruins: No ruins available - Not generating ruins

Ruins: No ruins available - Not generating ruins

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Non-buildable or Non-magical SMES at 70X 112Y 4Z

Ruins: No ruins available - Not generating ruins

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Non-buildable or Non-magical SMES at 181X 188Y 4Z

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Non-buildable or Non-magical SMES at 109X 115Y 4Z

Ruins: No ruins available - Not generating ruins

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .

Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Away Sites Testing Facility" at 4,12, containing Z 1

Sectors: Putting overmap on 2

Sectors: Overmap build complete.

Initializing Unit Testing → @@@code/unit_tests/ss_test.dm:123

21 unit tests loaded. → @@@code/unit_tests/ss_test.dm:145

No active ZAS edges at round-start. → @@@code/unit_tests/zas_tests.dm:216

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "NSV While True" at ,, containing Z 3

Sectors: Putting overmap on 4

Sectors: Overmap build complete.

Sectors: Located sector "NSS Runtime" at 21,6, containing Z 1 and 2

Exoplanets: Building new exoplanet with type: /obj/effect/overmap/visitable/sector/exoplanet/barren/asteroid and size: 255 255

Sectors: Located sector "Fryer-India, a mineral asteroid" at 21,6, containing Z 5

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Initializing Unit Testing → @@@code/unit_tests/ss_test.dm:123

74 unit tests loaded. → @@@code/unit_tests/ss_test.dm:145

All exoplanet areas have an exoplanet base turf. → @@@code/unit_tests/area_configuration_tests.dm:29

Testing files for ruin /datum/map_template/ruin/away_site/abandoned_diner

Testing files for ruin /datum/map_template/ruin/away_site/abandoned_industrial_station

Testing files for ruin /datum/map_template/ruin/away_site/cursed

Testing files for ruin /datum/map_template/ruin/away_site/abandoned_propellant_depot

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Initializing Unit Testing → @@@code/unit_tests/ss_test.dm:123

1 unit tests loaded. → @@@code/unit_tests/ss_test.dm:145

All paths are created and destroyed successfully, without hard deletions or other unwanted behaviors → @@@code/unit_tests/create_and_destroy.dm:301

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Initializing Unit Testing → @@@code/unit_tests/ss_test.dm:123

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "SCCV Spark" at ,, containing Z 5

Sectors: Putting overmap on 6

Sectors: Overmap build complete.

Sectors: Located sector "SCCV Intrepid" at ,, containing Z 7

Sectors: Located sector "SCCV Quark" at ,, containing Z 8

Sectors: Located sector "SCCV Canary" at ,, containing Z 9

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "NSV While True" at ,, containing Z 3

Sectors: Putting overmap on 4

Sectors: Overmap build complete.

Sectors: Located sector "NSS Runtime" at 21,6, containing Z 1 and 2

Exoplanets: Building new exoplanet with type: /obj/effect/overmap/visitable/sector/exoplanet/barren/asteroid and size: 255 255

Sectors: Located sector "Fryer-India, a mineral asteroid" at 21,6, containing Z 5

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "NSV While True" at ,, containing Z 3

Sectors: Putting overmap on 4

Sectors: Overmap build complete.

Sectors: Located sector "NSS Runtime" at 21,6, containing Z 1 and 2

Exoplanets: Building new exoplanet with type: /obj/effect/overmap/visitable/sector/exoplanet/barren/asteroid and size: 255 255

Sectors: Located sector "Fryer-India, a mineral asteroid" at 21,6, containing Z 5

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "NSV While True" at ,, containing Z 3

Sectors: Putting overmap on 4

Sectors: Overmap build complete.

Sectors: Located sector "NSS Runtime" at 21,6, containing Z 1 and 2

Exoplanets: Building new exoplanet with type: /obj/effect/overmap/visitable/sector/exoplanet/barren/asteroid and size: 255 255

Sectors: Located sector "Fryer-India, a mineral asteroid" at 21,6, containing Z 5

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Abandoned Space Diner" at 8,9, containing Z 2

Sectors: Putting overmap on 3

Sectors: Overmap build complete.

Sectors: Located sector "Abandoned Industrial Station" at 11,3, containing Z 4

Sectors: Located sector "lone asteroid" at 7,13, containing Z 5

Sectors: Located sector "Abandoned Propellant Depot" at 10,10, containing Z 6

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Away Sites Testing Facility" at 4,12, containing Z 1

Sectors: Putting overmap on 2

Sectors: Overmap build complete.

Sectors: Located sector "Thapa-Eta, a crystalline exoplanet" at 10,17, containing Z 3

Ruins: Finished selecting planet ruins (Delivery Site) for 0 cost of 6 budget.

Sectors: Located sector "Mugo-Juliett, a grove exoplanet" at 6,2, containing Z 4

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Away Sites Testing Facility" at 4,12, containing Z 1

Sectors: Putting overmap on 2

Sectors: Overmap build complete.

Sectors: Located sector "Thapa-Eta, a mineral asteroid" at 7,6, containing Z 3

Ruins: Ruin "drill site" (/datum/map_template/ruin/exoplanet/drill_site) loaded with geometry: Lower X: 95 - Lower Y 83 -- Upper X: 101 - Upper Y: 89

Ruins: Ruin "Abandoned Mining Site" (/datum/map_template/ruin/exoplanet/abandoned_mining) loaded with geometry: Lower X: 150 - Lower Y 38 -- Upper X: 182 - Upper Y: 70

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Asteroid Station" at 18,17, containing Z 2

Sectors: Putting overmap on 3

Sectors: Overmap build complete.

Sectors: Located sector "ICV Winds Over Aoyama" at ,, containing Z 4

Sectors: Located sector "Orion Express Automated Station #922" at 3,9, containing Z 5

Sectors: Located sector "IHCV Xk'tiik" at ,, containing Z 7

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Away Sites Testing Facility" at 4,12, containing Z 1

Sectors: Putting overmap on 2

Sectors: Overmap build complete.

Sectors: Located sector "Thapa-Eta, a barren exoplanet" at 10,17, containing Z 3

Ruins: Ruin "drill site" (/datum/map_template/ruin/exoplanet/drill_site) loaded with geometry: Lower X: 69 - Lower Y 196 -- Upper X: 75 - Upper Y: 202

Ruins: Ruin "Crashed Pod" (/datum/map_template/ruin/exoplanet/crashed_pod_1) loaded with geometry: Lower X: 149 - Lower Y 68 -- Upper X: 159 - Upper Y: 78

Unit Tests Enabled. This will destroy the world when testing is complete.

SSMapfinalization: Finalized map in 0 seconds.

SSMapfinalization: Not loading away mission, because no mission has been selected.

Sectors: Building overmap...

Sectors: Located sector "Konyang - Point Verdant Spaceport" at 18,18, containing Z 4, 3 and 2

Sectors: Putting overmap on 5

Sectors: Overmap build complete.

Sectors: Located sector "asteroid lair" at 8,16, containing Z 6

Sectors: Located sector "ICV Flintlock" at ,, containing Z 7