Files
VOREStation/code/datums/components
Will 53a1373611 fix some remote view component desyncs and crashes (#18627)
* fix some crashes

* lets clean this all up

* trymove

* the rest

* Revert "the rest"

This reverts commit a2076cbfb0.

* Revert "trymove"

This reverts commit f63e3c822f.

* Revert "lets clean this all up"

This reverts commit c590eef512.

* lets keep this in scope

* admin stuff

* this too

* fix

* this needs to be forceMoved

* Revert "this needs to be forceMoved"

This reverts commit d24f883699.

* stardog mouth fix and qdel
2025-10-14 06:35:57 -07: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-08-04 16:52:11 +02:00
2025-10-09 15:16:30 +02:00
2025-10-06 15:43:42 -04: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

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