Files
Bubberstation/code/datums/components
SmArtKar 92d224d48f Fourth! Time's the Charm: Actually fixes jetpack race conditions this time around (#88492)
## About The Pull Request

A) Queue time can be null and it'll be valid for hotstarting loops
B) Pushoffs working even when you're moving feels much better
C) Jetpacks were having race issues with drift handlers because those
were also using comsigs which is a remnant of old code back when they
were components. Handlers should fire last, post-comsigs.
D) We should not be hard-blocking jetpack movement when doing final
slowdown step. Like really.

## Why It's Good For The Game

Jetpacks ACTUALLY don't suck this time around.

## Changelog
🆑
qol: Jetpacks should ACTUALLY feel better now
/🆑
2024-12-15 04:49:30 +01:00
..
2024-05-16 19:54:00 -07:00
2024-10-09 02:03:50 +02:00
2024-08-15 01:28:21 +01:00
2024-05-16 19:54:00 -07:00
2024-05-16 19:54:00 -07:00
2024-12-14 00:13:12 +01:00
2024-08-21 17:07:02 +12:00
2024-07-15 16:28:41 +01:00
2024-10-09 02:03:50 +02:00
2024-10-07 13:34:36 +02:00
2024-05-16 19:54:00 -07: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 its 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