Files
Paradise/code/datums/components
Luc d8ddda378b Deadchat Plays SS13: Ghost Control of Mobs (#20600)
* Add dchat control

* adds human support, cleans other things up

* Bit of cleanup

* actually use the item

* minor proc ref mistake, laugh at this user

* evil tg strings

* Renames defines, adds vv menu item for it

* Improve anarchy message formatting

* don't go to_chatting tesla energy balls

* aa review

* Minor cleanups, replace some emotes

* Addressing some reviews

* Incorporate some checks for deadchat mutes/prefs
2023-05-21 12:33:11 -05:00
..
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-12-19 23:44:07 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2023-02-28 14:38:27 -06:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +00:00
2022-11-08 23:08:40 +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 it's arguments with a SendSignal() call. Now every component that want's to can also know about this happening.

See this thread for an introduction to the system as a whole.

See/Define signals and their arguments in __DEFINES\dcs\signals.dm