mirror of https://github.com/Aurorastation/Aurora.3.git synced 2025-12-31 20:42:27 +00:00

Files

Fluffy c5dabb9cda Armor defines (#20563 )

Added armor defines
Converted raw strings use to defines
Added UT test to ensure people set the armor var correctly (to a list)

No player facing changes

2025-03-09 21:37:46 +00:00

armor

Armor defines (#20563 )

2025-03-09 21:37:46 +00:00

base_name

…

eye

Clicks refactor (#20321 )

2025-01-09 23:04:48 +00:00

multitool

516 internal links (#20428 )

2025-02-20 22:54:10 +00:00

overhead_emote

Refactored the abstract meta propriety (#19797 )

2024-08-23 10:49:28 +00:00

turf_click

…

_component.dm

Clicks refactor (#20321 )

2025-01-09 23:04:48 +00:00

connect_mob_behalf.dm

…

drift.dm

SSthrowing (#19421 )

2024-06-18 19:32:06 +00:00

local_network.dm

…

orbiter.dm

Adds the Odyssey gamemode. (#18972 )

2024-11-26 20:18:43 +00:00

README.md

…

README.md

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.

README.md

Datum Component System (DCS)

Concept

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