Files
Bubberstation/code/datums/components
Tastyfish 3f3d337d7b Massive plumbing layer/placement improvements (#66602)
* Massive duct improvements

* last minute fixes/additions to plumbing layer fixes

* letter, loop, and early return fixes

* early continues

* color comments

* reaction chamber colors

* rcd tweaks

* Update code/datums/components/plumbing/reaction_chamber.dm

* Update code/datums/components/plumbing/reaction_chamber.dm

* Update code/datums/components/plumbing/_plumbing.dm

* Update code/datums/components/plumbing/_plumbing.dm

* remove unused var, better duct restacking

Co-authored-by: ShizCalev <ShizCalev@users.noreply.github.com>
2022-06-07 19:30:18 -04: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-05-26 12:56:00 -04:00
2022-06-01 19:41: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

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