Files
Bubberstation/code/datums/components
SkyratBot e5ba1e5e99 [MIRROR] [NO GBP] The deathmatch modifiers modal menu can actually be opened now. (#26942)
* [NO GBP] The deathmatch modifiers modal menu can actually be opened now. (#82041)

## About The Pull Request
I've fucked up the logic, so it requires the user to be both the host
and an admin to open it, which was the case when I tested it locally.
This PR fixes that and other issues (and **un**dumbs some of the code).
The spinning screen modifier has also been scrapped for being downright
awful and breaking my screen.

## Why It's Good For The Game
Fixing stuff I've thankfully noticed early.

## Changelog

🆑
fix: The deathmatch modifiers modal menu can actually be opened now.
Also fixed a bunch of issues it had.
/🆑

* [NO GBP] The deathmatch modifiers modal menu can actually be opened now.

---------

Co-authored-by: Ghom <42542238+Ghommie@users.noreply.github.com>
2024-03-20 06:28:45 -04:00
..
2024-02-20 01:00:11 +01:00
2024-03-01 19:05:23 +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