Files
VOREStation/code/datums/components
Cameron Lennox 61f2fc1009 Various bugfixes (#18944)
* Fixes robotic multitool going invisible

* fixes hybrid cutters

Fixes https://github.com/CHOMPStation2/CHOMPStation2/issues/12125

* Fixes radiation healing

Fixes https://github.com/CHOMPStation2/CHOMPStation2/issues/12072

* Fixes holocarp spam

Fixes https://github.com/CHOMPStation2/CHOMPStation2/issues/12042
2025-12-28 14:28:46 +01:00
..
2025-08-06 21:16:32 -04:00
2025-11-08 02:05:08 +01:00
2025-12-09 17:50:52 -05:00
2025-12-20 03:23:16 -05:00
2025-12-09 17:50:52 -05:00
2025-12-17 03:06:46 -08:00
2025-11-07 21:28:21 +01:00
2025-12-28 14:28:46 +01: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-12-20 03:23:16 -05:00
2025-12-20 03:23:16 -05:00
2025-12-09 17:50:52 -05:00
2025-12-10 03:41:33 +01: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