Files
Bubberstation/code/datums/components
nemvar 6ef421be42 Renames a few variables. Also reorders icon fallback order again. (#51060)
* Renames a few variables. Also reorders fallback order again.
Renames item_state to inhand_icon_state
Renames mob_overlay_icon to worn_icon
Renames mob_overlay_state to worn_icon_state
worn_icon_state/mob_overlay_state now never gets used for inhands.

* Fixes some comments

* Fixes map issue

* Restart lints

* Properly resolves conflicts
2020-05-25 06:47:19 +02:00
..
2020-04-01 14:38:55 +08:00
2020-02-17 15:03:16 +01:00
2020-02-17 23:09:09 -05:00
2020-05-24 14:04:35 -03:00
2020-02-17 15:03:16 +01:00
2020-04-19 19:36:35 +03:00
2020-03-14 01:58:18 +01:00
2020-04-05 21:06:45 -03:00
2020-02-17 15:03:16 +01:00
2020-05-22 02:17:15 -07:00
2020-03-11 15:30:17 +08:00
2020-02-17 23:09:09 -05:00
2020-04-18 10:26:47 -04:00
2020-01-25 15:53:09 -08:00
2020-02-17 15:03:16 +01:00
2020-02-18 00:06:12 -07:00
2020-02-17 15:03:16 +01:00
2020-02-17 15:03:16 +01:00
2020-04-25 00:59:23 -03:00
2020-03-06 09:49:50 -06:00
2020-04-24 23:45:35 -03: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