Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0.1s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0s

Process completed with exit code 1.

Found 2 datum list arguments with similar contents for /datum/element/hat_wearer. Contents: ["addtrait mob_tipped"].

Ensure that each list is static or cached. string_lists() (as well as similar procs) is your friend here. Check the documentation from dcs_check_list_arguments.dm for more information!

FAIL /datum/unit_test/dcs_check_list_arguments 0.1s

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@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/checkout@v3, actions/cache@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/checkout@v3, actions/cache@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/checkout@v3, actions/cache@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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/checkout@v3, actions/cache@v3, actions/upload-artifact@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 artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "test_artifacts_birdshot", "test_artifacts_deltastation", "test_artifacts_gateway_test", "test_artifacts_icebox", "test_artifacts_kilostation", "test_artifacts_limastation", "test_artifacts_metastation", "test_artifacts_multiz_debug", "test_artifacts_northstar", "test_artifacts_pubbystation", "test_artifacts_runtimestation", "test_artifacts_tramstation". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.

Lua Scripting (/datum/controller/subsystem/lua) is a subsystem meant to initialize but doesn't get set as initialized. This subsystem is marked as SS_OK_TO_FAIL_INIT. This is still a bug, but it is non-blocking.