Files
Bubberstation/code/datums/components
SyncIt21 da4868cff9 Fixes random runtime for round start silo connections (#92897)
## About The Pull Request
Happens randomly only at round start. Between the time the silo
connection gets initialized (i.e. when the atom subsystem is
initialized) & the round start literarily anything can happen like the
atom getting destroyed by some random event resulting in the parent
becoming null.

So we check for that & abort accordingly

## Changelog
🆑
fix: Fixes random runtime for round start silo connections
/🆑

---------

Co-authored-by: LemonInTheDark <58055496+LemonInTheDark@users.noreply.github.com>
2025-09-11 03:40:08 -07:00
..
2025-09-03 04:39:43 -07:00
2025-09-07 09:24:34 +02:00
2025-05-12 20:37:17 -07:00
2025-09-07 09:24:34 +02:00
2025-04-05 22:27:05 +02:00
2025-02-22 13:24:53 +00:00
2025-01-22 20:50:07 -07:00
2025-01-28 03:12:59 +01:00
2025-07-11 07:21:02 +00:00
2025-05-08 07:26:01 +02:00

Datum Component System (DCS)

Concept

Loosely adapted from /vg/. This is an entity component system for adding behaviours to datums when inheritance doesn't quite cut it. By using signals and events instead of direct inheritance, you can inject behaviours without hacky overloads. It requires a different method of thinking, but is not hard to use correctly. If a behaviour can have application across more than one thing. Make it generic, make it a component. Atom/mob/obj event? Give it a signal, and forward its arguments with a SendSignal() call. Now every component that want's to can also know about this happening.

HackMD page for an introduction to the system as a whole.

See/Define signals and their arguments in __DEFINES\components.dm