mirror of
https://github.com/Aurorastation/Aurora.3.git
synced 2026-07-30 17:26:32 +01:00
FabianK3
328c56be11
# Summary This PR adds persistent supply packages and a specialized charge card for lore arcs. Both can only be created using admin permissions and are not intended for general availability. ## Changes - Added a new package type, persistent supplies. - Abstracted existing orion deliveries for shared code. - Added a new persistent charge card variant. - Added exceptions and specific logging for new card variant. ## Notes Depends on PR #22367. Specific merge order not relevant. Icons by @Fyniiy. Relevant information for the current arc can be found on the forum thread [Operation Deep Dive](https://forums.aurorastation.org/topic/22921-all-crew-thread-operation-deep-dive/). --------- Signed-off-by: FabianK3 <21039694+FabianK3@users.noreply.github.com> Co-authored-by: Copilot <copilot@github.com> Co-authored-by: SleepyGemmy <99297919+SleepyGemmy@users.noreply.github.com>
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.