Files
Paradise/code/datums/components
DGamerL db1ed68a7d Tweaks some nuclear agent items (#22119)
* First changes

* Dont forget to do cooldown shit

* I HATE PEOPLE AAAAA

* Defib almost done

* Okay we ball

* Defib done

* I hate bullets

* Sniper done

* More stamina damage

* GDN review + Oops I forgor this

* Update code/datums/components/defibrillator.dm

Co-authored-by: Henri215 <77684085+Henri215@users.noreply.github.com>

* Disintegrate go brrrr

* Lewc review

* Ghhhhh

* Final oopsie fixed

* Almost made an oopsie daisy myself

---------

Co-authored-by: Henri215 <77684085+Henri215@users.noreply.github.com>
2023-09-07 10:52:48 +01:00
..
2023-08-21 19:48:45 +01: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

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