Files
Bubberstation/code/datums/components
Ghom a004694460 quickfix for a CI failure that went through because enabling auto-merge seems to ignore CI (#86740)
## About The Pull Request
Unused var removed.

## Why It's Good For The Game
I was told to do it.

## Changelog
N/A
2024-09-17 19:36:06 -04:00
..
2024-08-21 17:07:02 +12:00
2024-05-16 19:54:00 -07:00
2024-06-05 10:17:34 -04:00
2024-08-15 01:28:21 +01:00
2024-05-16 19:54:00 -07:00
2024-06-13 13:29:45 -07:00
2024-04-16 17:48:03 -06:00
2024-05-16 19:54:00 -07:00
2024-08-23 21:49:46 +02:00
2024-08-21 17:07:02 +12:00
2024-03-29 22:26:35 -06:00
2024-03-27 16:49:46 -06:00
2024-07-15 16:28:41 +01:00
2024-08-21 17:07:02 +12:00
2024-05-16 19:54:00 -07:00
2024-08-02 23:12:35 +00: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 its 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