Adds the Odyssey gamemode. #28530
Annotations
9 errors, 10 warnings, and 10 notices
|
Configure pod, build and run
**** !!! 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
|
|
Configure pod, build and run
**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249
|
|
Configure pod, build and run
**** !!! 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
|
|
Configure pod, build and run
**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249
|
|
Configure pod, build and run
**** !!! 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
|
|
Configure pod, build and run
**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249
|
|
Configure pod, build and run
**** !!! 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
|
|
Configure pod, build and run
**** [1] Errors Encountered! Read the logs above! **** → @@@code/unit_tests/ss_test.dm:249
|
|
Configure pod, build and run
Process completed with exit code 1.
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Non-buildable or Non-magical SMES at 105X 133Y 1Z
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Non-buildable or Non-magical SMES at 105X 133Y 1Z
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Sound Loops usr: .
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Runechat usr: .
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Non-buildable or Non-magical SMES at 105X 133Y 1Z
|
|
Configure pod, build and run:
code/__HELPERS/logging/_logging.dm#L32
Timer buckets has been reset, this may cause timer to lag in code/controllers/subsystems/timer.dm at line 239 src: Timer usr: .
|
|
Configure pod, build and run
Unit Tests Enabled. This will destroy the world when testing is complete.
|
|
Configure pod, build and run:
code/__HELPERS/logging/subsystems/mapfinalization.dm#L3
SSMapfinalization: Finalized map in 0 seconds.
|
|
Configure pod, build and run:
code/__HELPERS/logging/subsystems/mapfinalization.dm#L3
SSMapfinalization: Not loading away mission, because no mission has been selected.
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Building overmap...
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Located sector "SCCV Spark" at ,, containing Z 5
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Putting overmap on 6
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Overmap build complete.
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Located sector "SCCV Intrepid" at ,, containing Z 7
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Located sector "SCCV Quark" at ,, containing Z 8
|
|
Configure pod, build and run:
code/__HELPERS/logging/modules/sectors.dm#L3
Sectors: Located sector "SCCV Canary" at ,, containing Z 9
|
Loading