Deleting one conditions breaks others

When you're creating a move and delete a condition, all the conditions lower down the list get treated like they don't exist (they straight-up won't be there if you press "Create Move"). This was the bane of my existence, so I actually went into the inspector to figure it out, and I think I know what's happening.

The problem is that collectFormData() assumes that the fields in the conditions list are going to be numbered in order, with no gaps. It needs to find the field archetype_0, then archetype_1, and so on, and stops when one of them is missing.

But when you delete a condition, none of the fields change numbers. There's just a missing number, which stops collectFormData() early.