Files
Paradise/code/datums/components
SteelSlayer e49b016df4 Updates the proximity monitor component (#15836)
* prox component update

* mochi review

* bug fix, makes proximity sensors always active

* GC fixes and removes an unused proc

* Disposal fixes from TM

* fixes runtimes when objects created in nullspace runtimes, fixes portable flasher

* a fresh perspective

* lewcc review

* adds comment about direct loc setting over forceMove
2022-04-30 15:50:36 +01:00
..
2021-02-01 14:10:08 +00:00
2020-09-16 11:34:18 -04:00
2020-06-26 01:15:59 -06:00
2021-03-02 10:01:57 +00:00
2020-06-15 18:18:07 -06:00
2021-08-28 21:04:50 +01:00
2020-06-26 21:53:38 -04:00
2020-07-20 06:59:40 +02:00
2021-02-27 11:59:33 +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