SlamBamActionman

This is a funny item. It's also really strong. It def shouldn't work for anchored objects, that just invites a whole new level of harassing every single department ever. Considering...

> this is in a good direction (i think we have an issue somewhere for turning this into a fully generic reusable thing) but seems inadequate, considering reagenteffects still carry...

New commit splits `EntityEffectArgs` into `EntityEffectReagentArgs`, which is derived from `EntityEffectBaseArgs`. _Most_ effects should now work with just `EntityEffectBaseArgs`, allowing systems to trigger them without using any of the reagent-specific...

Also I can't make heads or tails of the failed build error. If anyone has suggestions, I'd be happy to hear it.

Test failure is caused by serialization issues with EntityEffect. This is not caused by the PR itself, but rather an underlying problem which I do not know how to solve....

> Some of the comments refer to reaction effects / reagent effects still (e.g. EntityEffect itself). Should be fixed now, though it's not impossible I've missed some place.

~~We already have a Visitor icon in the Jobs folder which is utilized for assigning visitors with the station's ID console, I suggest you use that to avoid icon mismatch:...

Not that I don't find the idea of more shuttle roles and stuff very exciting, but considering the breadth of shuttles and variations in the ghost roles being added it...

> * What's to stop command just taking the console onto escape shuttle or just breaking it immediately. If this is "just make it unanchorable, invincible and always powered" I'm...

If there is a strong concern that Command will too often remove the CC CD to take the Cargo/Salvage shuttle to CentCom, thus making Escape Pods too often unusable, it'd...