Files
GS13NG/code/datums/components
kiwedespars 7c653d0891 i actually kinda like the idea that you need a point for paths.
- whoops actually increases stamdamage of mansus grasp to 60.
- ascensions bumped up to 5 each.
- recipe for a codex made a bit harder.
2020-08-16 04:34:04 -07:00
..
2020-07-01 15:04:51 +02:00
2020-07-24 22:34:22 +01:00
2020-07-17 02:01:33 +01:00
2020-06-17 21:32:10 -07:00
2020-07-20 00:40:18 +01:00
2020-07-25 02:12:21 +01:00
2020-07-20 17:48:37 +01:00
2020-07-22 12:02:31 +08:00
smh
2020-07-28 12:31:35 -07:00
2020-08-08 00:08:43 -07:00
2020-07-25 00:22:24 +01:00
2020-08-07 16:23:15 -03:00
2020-07-28 10:47:07 -05:00
2020-06-24 23:18:03 +02:00
2020-08-07 01:06:23 -07:00
2020-07-17 02:01:33 +01:00
2020-08-07 01:31:29 -07: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\components.dm