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

Files

Heroman3003 a15578d8fd Merge pull request #16597 from Kashargul/miscGripper

up ports misc gripper, gargoyle, petrification, some message fixes

2024-11-30 14:41:36 +10:00

crafting

usr to user up to player effects

2024-11-12 00:10:20 +01:00

_component.dm

Fix datum components (#15788 )

2024-02-27 19:37:15 +01: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

Update the autolathe UI, make it less laggy (#16521 )

2024-10-26 14:19:12 +02:00

overlay_lighting.dm

More 515 Compatibility

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

README.md

…

recursive_move.dm

Remove

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

resize_guard.dm

always resize... (#16038 )

2024-06-11 19:15:57 +02: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.

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\dcs\signals.dm