Files
GS13NG/code/datums/components
DeltaFire 27a099c6bf Revert "Merge branch 'master' into robotic-limbs-PT2"
This reverts commit 73b5267425, reversing
changes made to 2e780bfff2.
2020-10-11 00:51:39 +02:00
..
2020-08-25 18:55:57 +10:00
2020-09-06 20:41:35 +02:00
e
2020-08-18 19:09:01 +10:00
2020-07-01 15:04:51 +02:00
2020-06-10 23:14:25 +01:00
2020-07-24 22:34:22 +01:00
2020-10-06 17:34:13 +02:00
2020-09-02 19:16:16 +02:00
2020-05-30 22:29:41 -07:00
2020-07-20 00:40:18 +01:00
2020-07-20 17:48:37 +01:00
2020-07-22 12:02:31 +08:00
2020-06-10 23:14:25 +01:00
2020-06-08 06:12:51 +02:00
2020-05-31 02:20:20 +02:00
2020-07-25 00:22:24 +01:00
2020-08-07 16:23:15 -03:00
2020-07-28 10:47:07 -05:00
2020-06-24 23:18:03 +02:00
2020-07-17 02:01:33 +01:00
2020-08-07 01:31:29 -07:00
fix
2020-08-15 09:46:50 +08:00
2020-05-11 15:44:26 -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.

See this thread for an introduction to the system as a whole.

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