While powerful, these are ultimately barriers that are ready to be broken. I propose we add a sequential loop to the cloth and more commands. For example, the first tease would activate the first program and the second tease would activate the second program. So on and so forth before starting over at one. The number of programs accessible could be dictated by ProgCloth modules OR necessary skills.
In regards to adding to the command set, my proposal is a simple but bold one. Allow ProgCloth babble-on scripts to modify the @messages of a clothing object WITHOUT changing its @finalized status.
Inevitably, if implemented one of you will ruin this for everyone. Do we need a GM review process due to the inherent power of this proprosition?