OK, folks, hang on and back off, please.
Mike: I realize you probably don't intend it, but your tone is coming off pretty bad here, and I'm unsurprised Brandon is feeling defensive. I appreciate what you're trying to do, but please drop it now.
Brandon: Mike is correct. However, the mistake being made is not your fault. Go back to
this post. When I said, "There's two really core ways to do a customization", I meant it: there are only two ways to do a customization. You can either do everything in one go, or you can separate out the "removal" and the "installation" steps into two customizations. That's as far as a customization can be broken down, specifically
because of the issue regarding Tech XP and deliberately "farming" tiny easy customizations to gain the XP**. However, I'm aware that it's not as clear as it should be in the rules, and I can see how you got from point A ("the customization can be broken down into 2 different jobs") to point B ("the customization can be broken down into each job being a separate customization process) in the absence of a completely clear rule. In my own defense, StratOps is hardly clear on it either, and to a large degree I basically copy-pasted the StratOps customization section over to our rules. Therefore, the customizations you have already made have already been made; the results and XP gained will not be changed. From this point forward however, please keep this post in mind.
**There is no good way to regulate this, short of a human GM stepping in and saying "no". I'm attempting to let people know my intent here so they can play according to it without the necessity of my having to review
literally every Tech roll made in the campaign. Other ways to handle it are things like "customizations under XXX minutes don't give XP", or "A tech can only make a single customization per month." I dislike both of those, but those are possibilities if I feel people are abusing customizations to farm Tech XP. I'm aware that was not your intent.