Files
Bubberstation/code/datums/components
lessthanthree 1496019dde Fixes tram plate electrocution [NO GBP] (#79717)
## About The Pull Request

When tram electrocution was turned into a component instead of on the
turf, the bad luck omen stopped having a chance of electrocuting the
mob. Fixes the toast proc to check for the cursed trait, now also
applied by the omen.

Splits the toast probability into one value for a normal plate, and one
for a broken plate or people with omen. Narrows the window of a
potential shock with adjusted probability, no chance of electrocution on
green.

Adds a missing early return for when the tram isn't moving.

## Changelog

🆑 LT3
fix: Bad luck omen again raises your chance of getting shocked by the
tram plate
fix: Tram plate checks and energizes when the tram is moving
code: Omen component now applies the cursed trait
/🆑
2023-11-14 14:32:12 -07:00
..
2023-10-16 16:14:31 +02:00
2023-09-19 19:07:51 +00:00
2023-10-11 16:58:29 -06:00
2023-11-12 09:25:59 +00:00
2023-10-21 23:36:48 +00:00
2023-10-08 03:04:35 +01:00
2023-08-16 13:04:41 -06:00
2023-10-05 13:20:16 -06:00
2023-11-12 09:25:59 +00:00
2023-11-03 22:39:33 +00:00
2023-10-16 16:14:31 +02:00
2023-08-14 12:39:30 -06:00
2023-09-07 20:25:52 +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.

HackMD page for an introduction to the system as a whole.

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