Files
Bubberstation/code/datums/components
Jared-Fogle 7df16c595e Confusion will no longer continue to confuse after being cured (#52286)
* Confusion will no longer continue to confuse after being cured

* Grammar comment fix

* Move to status effect

* Remove test per request

* Make confusion a status effect, confusion curing now completely neuters the confusion

* set_confusion changes, get_confusion

* Fix confusion going down twice per tick

* Change strength = to proc

* Move procs to status_procs
2020-08-05 16:36:00 -03:00
..
2020-07-29 09:31:38 -03:00
2020-07-29 03:51:57 -03:00
2020-07-29 09:31:38 -03:00
2020-07-29 09:31:38 -03:00
2020-07-29 09:31:38 -03:00
2020-07-16 20:13:04 +02:00
2020-07-23 20:10:26 -04:00
2020-05-22 02:17:15 -07:00
2020-06-22 16:49:07 +02:00
2020-07-29 09:31:38 -03:00
2020-07-29 09:31:38 -03:00
2020-07-16 20:13:04 +02: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