Files
VOREStation/code/datums/components
Aura Dusklight 311c0117c1 Conversion of realname and nickname from bay (#19120)
* Automatic changelog compile [ci skip]

* replace all bay instances for realname and nickname with tg

* add comments where uncertain of sanitisation needed

* Fix issue from git conflict..

* Fix issue causing setup menu not opening

* Attempt to clean up how name datums are handled

* Remove redundant check

* Fix number issues with character names

---------

Co-authored-by: vorestation-ci[bot] <199609141+vorestation-ci[bot]@users.noreply.github.com>
2026-02-08 17:34:04 +01:00
..
2026-01-30 19:51:21 +01: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
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