Files
Bubberstation/code/datums/components
Qustinnus 4b2a8aebe5 [READY] Meat material & material datum turf support (#49402)
* temp

* meatwalls

* more

* adds sheetifier

* fix

* two

* mat texture + 4dplanner admin (#21)

* mat texture + 4dplanner admin

* keep together trait

* counter instead of trait

* finalizations

* woops

* fixes

* oopsie

* only set starting keep_together if necessary (#24)

* keep together as trait again

* remove false comment

* doc for TRAIT_KEEP_TOGETHER

* remove needless scoping

Co-authored-by: 4dplanner <3combined@gmail.com>
2020-03-04 23:18:08 +08:00
..
2020-02-17 23:09:09 -05:00
2020-02-17 23:09:09 -05:00
2019-09-22 03:03:45 -07:00
2020-02-17 15:03:16 +01:00
2020-02-17 23:09:09 -05:00
2019-10-09 01:50:16 -07:00
2020-02-17 15:03:16 +01:00
2020-02-17 23:09:09 -05:00
2019-06-19 22:07:57 +02:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2020-02-25 19:15:04 +01:00
2020-02-17 23:09:09 -05:00
2020-02-17 15:03:16 +01:00
2020-01-25 15:53:09 -08:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2019-08-21 11:50:38 +12:00
2019-10-05 13:40:40 -04:00
2019-10-13 16:46:25 +13:00
2019-10-13 14:36:43 +03:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2020-02-17 23:09:09 -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.

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

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