mirror of https://github.com/VOREStation/VOREStation.git synced 2026-01-29 02:13:12 +00:00

Files

Guti a081d48590 DCS Update + Footstep element (#17076 )

* DCS Update + Footstep element

* Steppy

* Revert "Steppy"

This reverts commit fab0590fb7.

* Reapply "Steppy"

This reverts commit 1f7ad8f8f7.

* Ough

* Oops! Wrong map.

* lil stuff

* Update

* Only loud

* Missed one

* NO MORE SILENT

* ...parenthesis.

2025-02-08 18:19:59 -05:00

crafting

fix crafting UI stuck

2025-01-14 18:56:23 +01:00

_component.dm

DCS Update + Footstep element (#17076 )

2025-02-08 18:19:59 -05:00

COMPONENT_TEMPLATE.md

DCS Update + Footstep element (#17076 )

2025-02-08 18:19:59 -05:00

connect_mob_behalf.dm

Port tg statpanel (#16463 )

2024-10-16 19:39:06 +02:00

gargoyle.dm

adds petrification

2024-11-12 19:43:48 +01:00

material_container.dm

DCS Update + Footstep element (#17076 )

2025-02-08 18:19:59 -05:00

overlay_lighting.dm

More 515 Compatibility

2023-06-05 19:29:40 +02:00

README.md

DCS Update + Footstep element (#17076 )

2025-02-08 18:19:59 -05:00

recursive_move.dm

Remove

2024-09-09 02:36:53 +02:00

resize_guard.dm

2024-12-04 22:45:00 +01:00

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.

README.md

Datum Component System (DCS)

Concept

HackMD page for an introduction to the system as a whole.

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