Files
Bubberstation/code/datums/components
4dplanner 27413bcf40 Shade fixes (#47031)
About The Pull Request

fixes #46572 (I think)
Why It's Good For The Game
Changelog

cl
fix: shades now heal properly upon re-entering a soulstone (previously they would temporarily heal, then take back all the damage next time they were hit)
fix: shades summoned from a soulstone are no longer invincible
/cl
2019-10-13 16:46:25 +13:00
..
2019-06-19 22:07:57 +02:00
2019-09-22 03:03:45 -07:00
2019-06-19 22:07:57 +02:00
2019-09-24 17:17:33 +02:00
2019-06-19 22:07:57 +02:00
2019-10-09 01:50:16 -07:00
2019-08-21 11:25:41 +12:00
2019-06-19 22:07:57 +02:00
2019-07-26 09:47:22 +12:00
2019-08-21 11:50:38 +12:00
2019-10-05 13:40:40 -04:00
2019-10-13 16:46:25 +13:00
2019-08-03 22:19:03 -07: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