mirror of https://github.com/Aurorastation/Aurora.3.git synced 2026-01-10 17:32:36 +00:00

Files

Fluffy 457a091d9a Clicks refactor (#20321 )

Added various events to the dcs system in regards to click handling.
Refactored various mouse related procs.
Fixed MUI mask.
Fixed AI jump on double click.
Fixed some runtimes with the click handler system.
Updated the click handler system.
Fixed fireman carry.

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

armor

Runtime map now loads in ~11 seconds instead of ~40, sped up various other things (#19957 )

2024-10-06 21:31:01 +00:00

base_name

…

eye

Clicks refactor (#20321 )

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

multitool

Refactored all the backslash ref and ref() calls to use REF() instead (#19847 )

2024-09-13 10:17:32 +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

Fixes the exosuit mounted autolathe. (#18440 )

2024-02-20 11:58:39 +00:00

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