Files
Bubberstation/code/datums/components
MrMelbert 36e2c1c1c7 Refactors pricetag component: no getcomponent, no ugly signals, fixes cubes a bit (#63954)
Refactors the pricetag component
Removes a getcomponent for the pricetag component in cube export handling (replaced with inherit component behavior)
Removes some nasty signals which were effectively just send signal, get 1
Deletes the internal radio within bounty cubes from before exporting
Disallows bounty cubes from being barcoded with TRAIT_NO_BARCODES
Prevents bounty cube pricetag component from being deleted by unwrapping
Closes #63921 technically
2022-01-11 21:22:52 +00:00
..
2021-12-24 12:00:24 -08:00
2021-09-24 18:44:23 -07:00
2022-01-04 22:23:56 +00:00
2021-12-27 14:47:59 -08:00
2021-12-15 14:12:04 -08:00
2021-12-24 12:00:24 -08:00
2021-06-08 15:04:35 -07: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
2021-06-16 15:06:10 -07:00
2021-12-24 12:00:24 -08:00
2021-12-23 01:02:30 -08: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