Issue when using a colon in the name of a deck to save

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Populate attack slots
2. Click save top deck
3. Enter a deck name and include a colon ":" in the name (i.e. Anti-Enclave 
Flagship: Strike 1)
4. Click OK
5. Load a different custom deck as attack
6. Try to load the deck you just saved with the colon

What is the expected output? What do you see instead?
The deck should load, but nothing happens.

What version of the product are you using? On what operating system?
v6r12 on Windows 7 64

Please provide any additional information below.
If you go to Update DB and click Reload custom decks, the deck will now appear 
in the drop down with the part of the name to the right of the colon missing.  
If you attempt to load it as attack, you will get an error message that 
includes that right part of the name, followed by a RecordIndex out of range 
error.

Most likely this is because a colon is used as a delimiter when storing custom 
decks, so using a colon in the name should either not be allowed by the program 
or perhaps disallow save with an error indicating colons cannot be used in the 
name...

Original issue reported on code.google.com by t...@macaleese.ca on 15 Sep 2011 at 10:03

[GoogleCodeExporter]

Forgot to sign the above -- Slivicon on Kongregate

Original comment by t...@macaleese.ca on 15 Sep 2011 at 10:04

[GoogleCodeExporter]

Well, and I forgot to check the issues page ;)
If you look into file 'custom.txt' where are all decks stored, you may notice 
some rules for implementing custom decks:
// Special symbols are ':', ',', '[',']','(' and ')', don't use them in deck 
names or card names
Symbol ':' is used to divide deck name from deck cards. Maybe you can use '-' 
instead? I think I will fix it in a way that last ':' in string will be used to 
determine end of deck name.

Original comment by mini...@gmail.com on 19 Sep 2011 at 5:40

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Also, input box with deck name should disallow using these special symbols in 
future.

Original comment by mini...@gmail.com on 19 Sep 2011 at 5:45

[GoogleCodeExporter]

Fixed

Original comment by mini...@gmail.com on 2 Oct 2011 at 12:17

• Changed state: Fixed