Files
Bubberstation/code/datums/components
BluBerry016 c3570d7168 [Semi-Modular] Adds Shipstation, an entire station... on a shuttle. (#2680)
* Adds Shipstation

* Whoops, haven't ported the turnstile module in yet

* Update maps.txt

* SHIPSTATION OVERHAUL BABYYYY

Updates shipstation to (most) of Kath's suggestions, adds a dedicated shuttle pilot job and completely overhauls the map itself.

* Shuttle Pilot  Landmark

* Air Supply

* Scrubber Pipes

* Scrubber Pipes 2

* Digi Fix

* card.dmi fix

* Update tgstation.dme

* a

* Update tgstation.dme

* card.dmi

* HOP Office Beutification

Sec next

* sec overhaul compliance

* Update station_ship.dmm

* area / iron repath

Co-authored-by: Gandalf <jzo123@hotmail.com>
2021-02-12 14:34:26 +00:00
..
2021-01-08 18:52:35 +01: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