Files
Bubberstation/code/datums/components
ArcaneMusic e09a9032da Crates and bountes are now defined by crate's value and paygrades. Civilian bounty payout is higher and uncheesable. (#55413)
Does a value-wise refactor of crates and bounties in order to scale the value of these imports and exports to the value of crate exports (500 credits each). Then, I have adjusted the value of crate exports to 200 credits down from 500 to place the most standard unit of profit within cargo to a scale within that of roundstart paygrades currently on station. (350-1400 credits).

This effectively balances one of the biggest disparities left within the in-game economy, which is that cargo's price scales have really never been re-balanced with the considerations of on station prices, and have been still to the same scale as when they were based on cargo points 3 years ago. While admittedly some prices in vendors were scale to those original cargo values, so many of them weren't that it warranted a massive rebalance PR in order to places the scale of these items within an appropriate range of their intended user's cost values.
2020-12-10 23:43:46 +00:00
..
2020-10-01 20:37:57 -03:00
2020-11-30 12:48:40 -05:00
2020-11-30 12:48:40 -05:00
2020-12-07 13:04:51 -08:00
2020-11-30 12:48:40 -05:00
2020-11-30 12:48:40 -05:00
2020-11-30 12:48:40 -05:00
2020-11-30 12:48:40 -05:00
2020-10-28 20:31:13 -07:00
2020-11-25 13:12:12 +01:00
2020-08-19 13:24:20 +12:00
2020-12-08 10:58:03 +01:00
2020-08-28 14:26:37 -07:00
2020-11-30 12:48:40 -05:00
2020-09-05 16:18:55 -03:00
2020-08-24 13:56:07 -07:00

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.

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