mirror of https://github.com/Aurorastation/Aurora.3.git synced 2026-01-15 20:02:16 +00:00

Files

Matt Atlas 23c0fd7b4f Autolathe and wires panel TGUI, autolathe queueing. (#17978 )

* autolathe 1

* FUCK MY LIFE

* more fixes

* autolathe queueing

* cl

* garbage collection

* wire fixes

* some final tweaks

* on second thought this might be annoying

* fix that

* whoopsies

* that didn't work for shit

---------

Co-authored-by: Matt Atlas <liermattia@gmail.com>

2023-12-21 11:40:49 +00:00

armor

Fix indentations (#17481 )

2023-10-05 10:15:58 +00:00

base_name

Major UT Overhaul (#16544 )

2023-06-27 16:44:16 +02:00

multitool

Rock the UI Away - Removes VueUI and adds TGUI (#16509 )

2023-06-25 19:03:33 +02:00

turf_click

Fix indentations (#17481 )

2023-10-05 10:15:58 +00:00

_component.dm

Async as define (#17542 )

2023-10-12 21:19:42 +00:00

connect_mob_behalf.dm

Autolathe and wires panel TGUI, autolathe queueing. (#17978 )

2023-12-21 11:40:49 +00:00

local_network.dm

Ports the fusion reactor from Baystation12, replacing the Tesla. (#17415 )

2023-10-07 19:57:22 +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