Files
Bubberstation/code/datums/components
SkyratBot 7b326654b3 [MIRROR] Cargo bounty cube incentives (#3263)
* Cargo bounty cube incentives (#56375)

Bounty cube announces its creation over Supply with its creator and
area, starting the speedy delivery bonus countdown
20% bonus for cargo if you send the cube within 5 minutes of its
creation.

Using an export scanner on it in the supply shuttle awards a 10%
personal handling tip when it reaches Centcom.

Cube nags at five minutes over Supply if it's not sent and cargo bonus
is lost.

All nags tell you the cube's area

Co-authored-by: coiax <yellowbounder@ gmail.com>

* Cargo bounty cube incentives

Co-authored-by: cacogen <25089914+cacogen@users.noreply.github.com>
Co-authored-by: coiax <yellowbounder@ gmail.com>
2021-02-10 11:55:27 +00:00
..
2021-01-08 18:52:35 +01:00
2020-08-19 04:48:14 +02:00
2020-09-07 03:52:59 +02: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