## About The Pull Request
This pull request removes the clipboard from the pool of heretic ritual
of knowledge items, specifically the "Easy" ones to obtain. The rest is
unchanged.
## Why It's Good For The Game
Clipboards are substantially harder to obtain than it's fellow objects
for the ritual.
- Shards are able to be made from glass from autolathes, maintenance
loot, protolathes, salvaged from structures
- Candles are printable from biomass, plenty of them in the chapel,
orderable, sometimes maintenance has them
- Paper is printable from biogen iirc and in huge quantities across the
entire station, you can also handcraft some or order it
- Everyone has a pen roundstart, obtainable from library, lathes, maints
- Flashlights are the same as above yet obtainable from most tool
closets and even emergency closets
- Crayons are able to be made with xenobiology, ordered, have a few map
spawns but are generally in good quantity and are maintenance loot.
The clipboard however is not printable, orders in sets of 2 for an
interesting sum in a suspiciously never ordered package, has lackluster
map spawns (One or two in cargo, one psychologist's), is sometimes
required in pairs if not more and it's severely more difficult to get. I
do not think anyone would miss this, as it's just tedious and too
low-supply to get. There are more batons on station then there are
clipboards, even organs are easier to access.
## Changelog
🆑
add: The heretic's ritual of knowledge no longer requires binoculars
add: Clipboards are craftable using a wood plank, an iron rod and
wirecutters
/🆑
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 its arguments with a SendSignal() call. Now every component that want's to can also know about this happening.