Files
Bubberstation/code/datums/components
SyncIt21 2f8acae66b Improves code for remote materials (#87870)
## About The Pull Request
- Moves remote materials attack chain to item interaction level. Another
step in moving away from `attackby()`
- Fixes #40070. Though the timer subsystem maybe affected by FPS, round
start trigger is always done after everything is set up which is now
used by remote materials

## Changelog
🆑
fix: silo connection on some machines won't time out when changing FPS
settings
code: improved attack chain code for silo connection
/🆑
2024-11-14 01:25:53 +01:00
..
2024-11-05 07:29:16 -05:00
2024-08-21 17:07:02 +12:00
2024-05-16 19:54:00 -07:00
2024-10-09 02:03:50 +02:00
2024-08-15 01:28:21 +01:00
2024-05-16 19:54:00 -07:00
2024-05-16 19:54:00 -07:00
2024-08-21 17:07:02 +12:00
2024-03-27 16:49:46 -06:00
2024-07-15 16:28:41 +01:00
2024-10-09 02:03:50 +02:00
2024-10-09 02:03:50 +02:00
2024-10-07 13:34:36 +02:00
2024-05-16 19:54:00 -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 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