Files
Bubberstation/code/datums/components
MrMelbert 61e45109cc Auto-docs + code improvements + splits up status_effect.dm (#66362)
* Code improvements for status effects in general

* Does this for now

* Throws in a qdeleted check

* A return

* comment tweak

* Missed some ref()s

* Wrong var

* Comment clarifications

* Some more comment clarifications
2022-04-21 15:59:46 -07:00
..
2022-04-21 15:35:23 -07:00
2022-03-31 14:05:55 +13:00
2021-09-24 18:44:23 -07:00
2022-03-31 14:05:55 +13:00
2022-04-01 21:07:46 -04:00
2022-04-01 21:07:46 -04:00
2022-04-01 21:07:46 -04:00
2022-01-13 23:44:45 -06:00
2021-12-24 12:00:24 -08:00
2021-10-15 07:01:02 +01:00
2021-12-24 12:00:24 -08:00
2021-12-24 12:00:24 -08:00
2022-04-01 21:07:46 -04:00
2022-04-01 21:07:46 -04: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