Files
Paradise/code/datums/components
Luc 8b91d8b48e Refactors defib code into a component (#19987)
* Start to datumize the defib.

* Wire everything else up

* connect some loose wires from testing

* More changes from testing

* More cleanups and documentation

* Revert CMO defib to have a 10% heart-attack chance

* Review, clean up giant if statement

* other review things

* sirryan review

Co-authored-by: Ryan <80364400+Sirryan2002@users.noreply.github.com>

* change signals to direct proc calls

* rename variable

* Fix bad argument

Co-authored-by: Ryan <80364400+Sirryan2002@users.noreply.github.com>
2023-01-16 20:19:03 -06:00
..
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-12-19 23:44:07 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00: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\dcs\signals.dm