Files
Bubberstation/code/datums/components
Fikou 7847efd270 [READY] the unfuckening of clothing rendering (#79784)
## About The Pull Request
refactors clothing visors to use the same system, including masks being
toggled and stuff like riot helmets toggling using the same system and
welding helmets and such
adds a handler that updates all visuals in slots that an item has
obscured, each visual proc calls that so you no longer have weird shit
happening like having to hardcode a proc for heads where you need to
also update hair, mask, glasses everytime you put on an item

one thing here i could also do is make check_obscured_slots return the
HIDEX flags instead of item slots, because in 99% of cases its hardcoded
to be ran against specific slots (like eye code running it against the
glasses slot), but maintainers didnt seem to like that :/

## Why It's Good For The Game
fuck this 2003 bullshit

## Changelog
theres like several bugs here i fixed but i forgot them all and they are
small
2024-04-21 17:08:03 -07:00
..
2024-04-19 11:33:41 -05:00
2023-10-16 16:14:31 +02:00
2024-04-18 17:05:06 +02:00
2024-04-16 17:48:03 -06:00
2024-04-09 03:21:51 -05:00
2023-10-11 16:58:29 -06:00
2024-02-11 03:17:55 +01:00
2024-02-29 04:24:10 +00:00
2023-12-04 14:42:43 -08:00
2023-11-12 09:25:59 +00:00
2024-03-16 12:06:02 +00:00
2024-04-20 01:39:50 -06:00
2024-04-16 17:48:03 -06:00
2023-10-21 23:36:48 +00:00
2023-10-08 03:04:35 +01:00
2023-12-04 14:42:43 -08:00
2024-03-29 22:26:35 -06:00
2023-10-05 13:20:16 -06:00
2024-04-16 17:48:03 -06:00
2024-03-27 16:49:46 -06:00
2023-10-16 16:14:31 +02:00
2024-03-21 20:30:56 -06:00
2024-03-16 12:06:02 +00:00
2024-04-16 17:48:03 -06:00
2023-12-09 13:31:50 +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