Files
Bubberstation/code/datums/components
SkyratBot 0186f4d8b0 [MIRROR] Removes stupid listlike var access code (#28658)
* Removes stupid listlike var access code (#84648)

## About The Pull Request

[Removes all other listlike var
accesses](4c5996b5c8)

Also fucking dumpsters an unused proc that allowed for arbitrary
variable modifcation. Bad juju

This is undefined behavior and errors in later 515 versions. also it's
stupid as hell

* Removes stupid listlike var access code

---------

Co-authored-by: LemonInTheDark <58055496+LemonInTheDark@users.noreply.github.com>
2024-07-06 09:42:28 +05:30
..
2024-05-23 02:37:43 +02:00
2024-04-26 01:22:24 +02:00
2024-05-18 11:40:59 -04:00
2024-02-20 01:00:11 +01:00
2024-04-26 01:22:24 +02:00
2024-04-26 01:22:24 +02:00
2024-04-29 21:15:33 +02:00
2024-04-29 21:15:33 +02:00
2024-04-28 22:24:01 +02:00
2024-04-23 20:43:45 +02:00
2024-04-29 21:15:33 +02:00
2024-04-26 01:22:24 +02:00
2024-05-18 11:40:59 -04: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