Files
VOREStation/code/datums/components
Reo Lozzot f8fc337da3 Toilet Overhaul (#19370)
* April Fool !

there's 30 minutes till midnight in my timezone so it's still valid

* Powder that make the maintainer say yes

* Apply suggestions from code review

Co-authored-by: Cameron Lennox <killer65311@gmail.com>

* Edits

* Update watercloset.dm

* five nights at space station toilet

pls merge or else poopwater 2 pr will be next

---------

Co-authored-by: Cameron Lennox <killer65311@gmail.com>
2026-04-23 21:22:06 -04:00
..
2025-08-06 21:16:32 -04:00
2026-04-16 10:40:31 -04:00
2026-04-23 21:22:06 -04:00
2026-04-20 22:56:22 -04:00
2026-04-12 19:42:30 -04:00
2026-04-23 21:22:06 -04:00
2026-03-21 23:59:46 -04:00
2025-11-07 21:28:21 +01:00
2025-10-04 03:13:12 -04:00
2025-10-01 23:14:54 +02:00
2025-12-20 03:23:16 -05:00
2026-04-18 15:22:00 -04:00
2025-12-09 17:50:52 -05:00
2025-12-10 03:41:33 +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