Files
VOREStation/code/datums/components
Cameron Lennox 4924a73ba2 Start of TG Click Code Port (#18734)
* click code start

* snake_span

* Update click.dm

* Update click.dm

* Update click.dm

* Update click.dm

* Fixes borg ctrl_click

Also implements allowing  blocking of items being ctrl_clicked

* Makes the statpanel not annihilate peoples ratelimiter

Statpanel calls aren't really user controlled (and 180 of them get sent upon loading, as each verb counts as a topic calls when it calls Send-Tabs) so let's not count it towards the user when they log in.
2025-12-06 01:13:12 -05:00
..
2025-08-06 21:16:32 -04:00
2025-11-08 02:05:08 +01:00
2025-10-12 22:18:08 -04:00
2025-11-11 00:08:48 +01:00
2025-11-07 21:28:21 +01:00
2025-11-07 21:28:21 +01:00
2025-11-08 02:19:49 +01:00
2025-10-04 03:13:12 -04:00
2025-07-20 16:48:40 +02:00
2025-10-01 23:14:54 +02:00
2025-07-20 16:48:40 +02:00
2025-11-11 00:51:21 +01:00
2025-11-22 11:36:50 -05: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