Files
Bubberstation/code/datums/components
NightRed 97d969dfca Many issue fixes for stomachs and chem interactions (#53440)
This changes the has_reagent check to work with stomachs.
Several supporting procs have been added to fully support this behavior.
end_metabolization will work as expected again
expose is working with INGEST items again
on_mob_add working as intended
on_mob_life has been reviewed and worked over.

Health Analyzers now show stomach contents, same with the medical kiosk.

Included the unit test to validate reagent checks.
Unit tests for the new procs on mob
2020-09-05 21:57:30 -03:00
..
2020-09-05 16:18:55 -03:00
2020-08-29 23:33:47 -03:00
2020-09-05 16:18:55 -03:00
2020-09-05 16:18:55 -03:00
2020-09-05 16:18:55 -03:00
2020-09-05 16:18:55 -03:00
2020-09-05 16:18:55 -03:00
2020-08-28 14:26:37 -07:00
2020-09-05 16:18:55 -03:00
2020-08-19 13:24:20 +12:00
2020-08-28 14:26:37 -07:00
2020-08-23 02:05:35 +02:00
2020-09-05 16:18:55 -03:00
2020-08-24 13:56:07 -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