/mob/living/simple_animal/hostile/hivebotbeacon/weakened hard deleted 1 times out of a total del count of 1 → @@@code/unit_tests/create_and_destroy.dm:279

SSGarbage HARDDEL: Completed search for references to a /mob/living/simple_animal/hostile/hivebotbeacon/weakened.

SSGarbage HARDDEL: Finished searching clients

SSGarbage HARDDEL: Finished searching datums

SSGarbage HARDDEL: Datums -> /datum/controller/subsystem/garbage [0x2100003a] -> queues (list) -> /list (list) -> /list (list) does not count as a ref for our count

SSGarbage HARDDEL: Found /mob/living/simple_animal/hostile/hivebotbeacon/weakened [0x3000ad4] in list Datums -> /datum/controller/subsystem/garbage [0x2100003a] -> queues (list) -> /list (list) -> /list (list).

SSGarbage HARDDEL: Finished searching atoms

SSGarbage HARDDEL: Finished searching native globals

SSGarbage HARDDEL: Finished searching globals

SSGarbage HARDDEL: Beginning search for references to a /mob/living/simple_animal/hostile/hivebotbeacon/weakened, looking for 1 refs.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, yogstation13/DreamAnnotate@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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: .

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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: .

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

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 '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 'plasteel' creates product with material 'plasteel', 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 '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 '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

--------------- Database not Configured - Skipping Preference Column UT → @@@code/unit_tests/sql_tests.dm:7

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: .

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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 105X 143Y 1Z

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

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: .

Ruins: No ruins available - Not generating ruins

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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

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

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: .

Ruins: No ruins available - Not generating ruins

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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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: .

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

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: .

Ruins: No ruins available - Not generating ruins

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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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: .

Ruins: No ruins available - Not generating ruins

Ruins: No ruins available - Not generating ruins

Ruins: No ruins available - Not generating ruins

Non-buildable or Non-magical SMES at 146X 180Y 4Z

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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 45X 99Y 4Z

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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: .

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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 96X 141Y 10Z

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

intercom_listener created with QDELETED intercom!

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: .

intercom_listener created with QDELETED intercom!

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: .

intercom_listener created with QDELETED intercom!

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: .

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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 135X 130Y 39Z

Non-buildable or Non-magical SMES at 153X 214Y 28Z

Non-buildable or Non-magical SMES at 87X 228Y 28Z

Non-buildable or Non-magical SMES at 139X 144Y 23Z

All shuttle transition and start location landmarks were found. → @@@code/unit_tests/shuttle_tests.dm:36

This map is not supposed to have any shuttles. → @@@code/unit_tests/zas_tests.dm:165

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

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

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 2

Sectors: Located sector "Away Sites Testing Facility" at 11,13, containing Z 1

Sectors: Building overmap...

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

Ruins: Ruin "Abandoned Hideout" (/datum/map_template/ruin/exoplanet/hideout) loaded with geometry: Lower X: 54 - Lower Y 78 -- Upper X: 86 - Upper Y: 110

Ruins: Ruin "Abandoned Listening Post" (/datum/map_template/ruin/exoplanet/abandoned_listening_post) loaded with geometry: Lower X: 64 - Lower Y 191 -- Upper X: 84 - Upper Y: 211

Sectors: Located sector "Thomas-Chi, a mineral asteroid" at 15,31, containing Z 5

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

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

Sectors: Located sector "NSS Runtime" at 14,31, containing Z 2 and 1

Sectors: Building overmap...

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

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

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

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

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

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

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

All shuttle areas are not station areas. → @@@code/unit_tests/area_configuration_tests.dm:53

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

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

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

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

Sectors: Located sector "SCCV Horizon" at 14,12, containing Z 3, 2 and 1

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

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

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 6

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

Sectors: Building overmap...

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

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

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

Sectors: Located sector "Thomas-Chi, a mineral asteroid" at 15,31, containing Z 5

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

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

Sectors: Located sector "NSS Runtime" at 14,31, containing Z 2 and 1

Sectors: Building overmap...

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

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

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

Sectors: Located sector "Thomas-Chi, a mineral asteroid" at 15,31, containing Z 5

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

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

Sectors: Located sector "NSS Runtime" at 14,31, containing Z 2 and 1

Sectors: Building overmap...

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

Ruins: Ruin "Crashed Shuttle" (/datum/map_template/ruin/exoplanet/crashsurvivors) loaded with geometry: Lower X: 66 - Lower Y 129 -- Upper X: 98 - Upper Y: 161

Ruins: Ruin "Crashed Skrellian Shuttle" (/datum/map_template/ruin/exoplanet/crashed_skrell_shuttle_01) loaded with geometry: Lower X: 105 - Lower Y 24 -- Upper X: 129 - Upper Y: 56

Sectors: Located sector "Onyekachi-Lambda, a grove exoplanet" at 7,4, containing Z 4

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

Sectors: Located sector "Cheng-Theta, a crystalline exoplanet" at 16,8, containing Z 3

Sectors: Overmap build complete.

Sectors: Putting overmap on 2

Sectors: Located sector "Away Sites Testing Facility" at 11,13, containing Z 1

Sectors: Building overmap...

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

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

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

Sectors: Located sector "Thomas-Chi, a mineral asteroid" at 15,31, containing Z 5

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

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

Sectors: Located sector "NSS Runtime" at 14,31, containing Z 2 and 1

Sectors: Building overmap...

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

Ruins: Ruin "Abandoned Mining Site" (/datum/map_template/ruin/exoplanet/abandoned_mining) loaded with geometry: Lower X: 194 - Lower Y 183 -- Upper X: 226 - Upper Y: 215

Ruins: Ruin "Crashed Escape Pod" (/datum/map_template/ruin/exoplanet/crashed_escape_pod_1) loaded with geometry: Lower X: 47 - Lower Y 62 -- Upper X: 57 - Upper Y: 76

Ruins: Ruin "Crashed Satellite" (/datum/map_template/ruin/exoplanet/crashed_satellite) loaded with geometry: Lower X: 104 - Lower Y 99 -- Upper X: 118 - Upper Y: 111

Ruins: Ruin "Abandoned Listening Post" (/datum/map_template/ruin/exoplanet/abandoned_listening_post) loaded with geometry: Lower X: 111 - Lower Y 59 -- Upper X: 131 - Upper Y: 79

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

Sectors: Overmap build complete.

Sectors: Putting overmap on 2

Sectors: Located sector "Away Sites Testing Facility" at 11,13, containing Z 1

Sectors: Building overmap...

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

Ruins: Ruin "Crashed Pod" (/datum/map_template/ruin/exoplanet/crashed_pod_1) loaded with geometry: Lower X: 187 - Lower Y 92 -- Upper X: 197 - Upper Y: 102

Ruins: Ruin "drill site" (/datum/map_template/ruin/exoplanet/drill_site) loaded with geometry: Lower X: 180 - Lower Y 51 -- Upper X: 186 - Upper Y: 57

Ruins: Ruin "Digsite" (/datum/map_template/ruin/exoplanet/digsite) loaded with geometry: Lower X: 25 - Lower Y 70 -- Upper X: 43 - Upper Y: 86

Ruins: Ruin "Abandoned Hideout" (/datum/map_template/ruin/exoplanet/hideout) loaded with geometry: Lower X: 162 - Lower Y 136 -- Upper X: 194 - Upper Y: 168

Sectors: Located sector "Cheng-Theta, a barren exoplanet" at 16,8, containing Z 3

Sectors: Overmap build complete.

Sectors: Putting overmap on 2

Sectors: Located sector "Away Sites Testing Facility" at 11,13, containing Z 1

Sectors: Building overmap...

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

Sectors: Located sector "Grand Romanovich Casino" at 13,11, containing Z 11

Sectors: Located sector "ICV Rustbucket" at ,, containing Z 10

Sectors: Located sector "asteroid lair" at 10,8, containing Z 9

Sectors: Located sector "Konyang - Point Verdant Spaceport" at 16,16, containing Z 8, 7 and 6

Sectors: Located sector "Assunzione - Port Volturno" at 16,16, containing Z 5 and 4

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

Sectors: Located sector "Casino Station" at 8,8, containing Z 2

Sectors: Building overmap...

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

Sectors: Located sector "Tret" at 5,8, containing Z 7

Sectors: Located sector "IHCV Xahth" at ,, containing Z 8

Sectors: Located sector "phoron deposit" at 9,12, containing Z 6

Sectors: Located sector "Orion Express Automated Station #103" at 5,8, containing Z 5

Sectors: Located sector "ICV Battle Against Evil" at ,, containing Z 4

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

Sectors: Located sector "Asteroid Station" at 6,14, containing Z 2

Sectors: Building overmap...

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

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

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

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

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

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

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

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

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

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

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

Sectors: Located sector "Auman-Phi, an arctic planetoid" at 14,8, containing Z 9 and 8

Sectors: Located sector "large derelict" at 4,13, containing Z 7

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

Sectors: Located sector "lone asteroid" at 15,9, containing Z 5

Sectors: Located sector "Abandoned Industrial Station" at 15,5, containing Z 4

Sectors: Overmap build complete.

Sectors: Putting overmap on 3

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

Sectors: Building overmap...