Bug: Custom set upload continuing to fail after initial name collision

[warshawd]

Webpage: www.dr4ft.info

Browser: Firefox Desktop 112.0.2

---

Detailed Description

I was uploading 3 custom sets today for an upcoming draft event. One of the sets had a conflicting set code with an existing magic set, TOR. The update failed with the error: the xml submitted is not valid: Set existing already. Not saving again with set go \"TOR\" to database

So I went back to my xml, gave it a new set code (using the same cockatrice_carddatabase/sets/set/name/ hierarchy in the xml that I always use), and tried again.

With a new set code, I still got the same error, but the set actually does show up in the list of all sets. The problem is, when I go to make a game, once it's time to draft the packs from that set, I just get pure white screen and nothing loads.

I went back again and changed not only the set code, but also the name of the set in the xml, and also the name of the actual file I'm uploading, but each time I still get the error, the still actually does show up in the list, and then I get pure white screen when it's time to draft it. Inspecting with browser console shows a pair of RangeError: invalid array length

I can upload any of the functioning or non-functioning xml if you would like to see it.

In the future I'll prefix all my set codes with our game's name, but I'm not sure how to get out of this particular state, since I feel changing the set code, set name, and filename should already be sufficient to make it look like a completely different set that doesn't collide.