Files
Bubberstation/code/datums/components
Jacquerel cfcf905a1c Separates COMSIG_LIVING_ADJUST_DAMAGE into 6 different signals (#78814)
## About The Pull Request

As potato requested after the merge of #78744 these should have separate
concerns even if they are very similar.
In addition I improved how mob chains react to glide size changes, and
swapped PAIs to using these signals instead of an override of
`onBruteLoss` just because I can.

I tested it but the unit tests will catch me if i did it wrong

## Changelog

🆑
fix: Flesh Worms will move smoothly more consistently.
/🆑
2023-10-07 11:44:15 -06:00
..
2023-08-22 01:26:34 +00:00
2023-08-16 13:04:41 -06:00
2023-09-19 19:07:51 +00:00
2023-09-26 15:28:26 -06:00
2023-08-16 13:04:41 -06:00
2023-07-12 18:52:02 -06:00
2023-10-05 13:20:16 -06:00
2023-08-14 12:39:30 -06:00
2023-09-07 20:25:52 +01: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