The field validation changes made a while ago broke things for tone names that contain an underscore (e.g. songname_tonetype).

 

Editing such a tone in the toolkit saves the tone key without the underscore, causing the tone to not work at all.

 

Caused me to spend a good part of the day puzzling over the fact that my tones suddenly stopped working.  :)

I feel your pain http://www.sherv.net/cm/emo/funny/1/bang.gif

 

It's been a long time i didn't update the toolkit, so i had the same problem with my tones.

But not with all the tones, some named with a underscore in it were stil working, i don't know why.

 

I understand now why some charters called their tones just clean, overdrive, acoustic, distortion...

If you load an old CDLC template (or import a package) that has tones with underscores in their names, they will still work as long as you don't edit them.

Ive got 44 that have tone errors when I tried to rebuild them.

I'm making a new custom and using the latest toolkit BUGFIX #5.

Just realised having an underscore in the tone name will break it.  :(

 

Is the the new norm? or a bug?

I've added this as a new issue at github.

Fixed