Files
VOREStation/code/datums/components
Will fd60bee1cb Relaymove Moved To Remote Views (#18714)
* Remote view setting datums

* remote view handles relayed move

* setting up checks

* many fixes

* small fixes

* default relay behavior

* use camera settings

* coordinated for overmap shuttle

* lock this down

* not needed

* not needed

* inaccurate doc

* small fixes

* various set machine calls no longer needed

* runtime

* health hud moved to signal controls

* overriding huds

* allow signal based huds entirely

* uav health icon

* fix

* oops that's important

* more return types

* mmis view fix

* not needed

* protect against instantly deleted ghosts

* all of these need remote on enter

* these too

* order
2025-11-05 17:47:58 -05:00
..
2025-08-06 21:16:32 -04:00
2025-10-04 03:13:12 -04:00
2025-09-07 23:05:08 -04:00
2025-10-12 22:18:08 -04:00
2025-11-03 20:38:11 -05:00
2025-11-03 20:38:11 -05:00
2025-10-04 03:13:12 -04:00
2025-07-20 16:48:40 +02:00
2025-10-01 23:14:54 +02:00
2025-05-17 06:44:56 -07:00
2025-07-20 16:48:40 +02:00
2025-10-12 22:18:08 -04:00
2025-10-14 15:35:38 -07: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 it's 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