Files
Bubberstation/code/datums/components
William Wallace b9b3cffad7 removing some duplicated proc definitions (#50812)
* remove duplicate definition of '/datum/component/plumbing/reaction_chamber/can_give'

* remove duplicate proc definitions for '/datum/status_effect/pacify/'

* syndicate holster correctly sets storage component's silent var

* singularity_act no longer deletes fulton 'extraction holder'

* singularity_act no longer deletes rend tears

* remove duplicate singularity_pull method from /obj/effect/cult_turf/overlay

* remove no longer used 'dir_map_to_angle' proc from reflectors

* remove duplicate /mob/living/simple_animal/bot/hygienebot/Crossed
2020-05-06 02:36:14 +08:00
..
2020-04-01 14:38:55 +08:00
2020-02-17 15:03:16 +01:00
2020-02-17 23:09:09 -05:00
2020-02-17 15:03:16 +01:00
2020-04-19 19:36:35 +03:00
2020-03-14 01:58:18 +01:00
2020-04-05 21:06:45 -03:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2020-03-11 15:30:17 +08:00
2020-02-17 23:09:09 -05:00
2020-02-17 15:03:16 +01:00
2020-04-18 10:26:47 -04:00
2020-02-17 15:03:16 +01:00
2020-02-18 00:06:12 -07:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2020-04-25 00:59:23 -03:00
2020-03-06 09:49:50 -06:00
2020-04-24 23:45:35 -03:00
2020-02-17 23:09:09 -05: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