Using --SkipSetup doesn't "always" update the card asked in the new XML

[NickDuff]

After doing 6 use cases of how SkipSetup works, I see some disparity of how I think it would come out and what the feature does.

Here, i've tested to change the back according to a new XML.
UC3.3- Change Back for a Particular Back other than a Generic One AND change the first back card with the same AND one other with a Demonic Tutor.

(See screenshot)
Steps to reproduce:
1- Take the 4 cards Opt Project from previous UC
2- Add 220 cards with all the same new picture (No Mercy)
3- Change the Back for a new Generic One (Money)
4- Change the Back for a new Particular for the 4 new added (Demonic Tutor)
5- Change the first cards (old card) for a Demonic Tutor
6- Change the 4th card for OPT (a new picture)

I should had 224 cards with at the Front (4 opts and 220 No Mercy) and at the Back (Tutor, Opt, Opt, New Opt, 4x Tutor, all other back Money).

Result: (see screenshot)
All opt at the front (even if uploaded No Mercy) and at the back the first generic picture that has been chosen, no tutor.

Screenshot:

[ndepaola]

this is the behaviour of --skipsetup at the moment as documented here https://github.com/chilli-axe/mpc-autofill/blob/master/autofill/readme.md

but i appreciate this isn't how people expect it to work and you're not the only one who's been caught out by this. the desired behaviour here is for the resultant project to match the XML no matter what the initial state of the project is - will leave this issue open until i get around to doing this