Proposal: Junkers
Passed 11-0. TDS
Adminned at 17 Jul 2022 06:38:57 UTC
Under the rule “Bot Loadout” add a subrule titled “Spare Parts Bin” that reads the following:
Each Operator has a Spare Parts Bin, which is a publicly tracked list of Chassises, Engines, and Systems as well as their conditions.
Change the bulleted list at the end of the subrule “Engines” to read the following:
*Either increase their money by the effective one-off cost of their engine or add their engine and its condition to their Spare Parts Bin.
*Replace the Engine of their Bot with another of any Condition by paying the Effective One-off Cost of the new Engine. If the new Engine is present in their Spare Parts Bin, they may instead remove it from their Spare Parts Bin.
Change the bulleted list at the end of the subrule “Chassises” to read the following:
*Either increase their money by the effective one-off cost of their Chassis or add their Chassis and its condition to their Spare Parts Bin.
*Replace the Chassis of their Bot with another of any Condition by paying the Effective One-off Cost of the new Chassis. If the new Chassis is present in their Spare Parts Bin, they may instead choose to remove it from their Spare Parts Bin rather than paying the Effective One-off Cost.
In the subrule “Systems”, change the paragraph beginning with “At any time…” to:
At any time, an Operator whose Readiness is Workshop may add a System of a desired Condition to their Bot by spending its Effective Cost or removing that system from their Spare Parts Bin as long as that system is present in their Spare Parts Bin at that condition. An Operator whose Readiness is not Set may remove a System from their Bot at any time by either increasing their money by 50% of the Effective Cost of the system being removed or adding that system at the appropriate condition to their Spare Parts Bin.
I feel like there’s not much room to try new strategies because you need to sell the parts you want to remove at a loss. Instead, I think having the option to hang onto them and put them back on later would be nice.
SingularByte: he/him