Files
Bubberstation/code/datums/components
Cruix e129b731ed Bug fixes (#50334)
* Fixed pointing runtime

* Fixed runtime allowing abductors to speak out loud

* Fixed being able to get two monkeys from each monkey cube

* Fixed being able to use camera consoles with the mech teleporter to teleport further than intended

* Fixed ninja suit never copying data from tech disk

* Fixed being able to tackle things not on a turf

* Rearranged ifs
2020-04-04 12:34:08 -07: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-02-17 23:09:09 -05:00
2020-03-14 01:58:18 +01: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-01-25 15:53:09 -08:00
2020-02-17 15:03:16 +01:00
2020-02-18 00:06:12 -07:00
2020-03-09 22:13:48 -07:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2020-04-04 12:34:08 -07:00
2020-03-06 09:49:50 -06: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