Title says it all, I made a tone assignment in Editor on Fire, but every time I load it into the toolkit, it's been reset to read as either "Default" or as one of the other XML files' tones. Is there a specific reason for this, or is this a small bug that I'm encountering?

There are some requirements for using tones, such as having to have more than one tone change set, and defining one of them as the default tone.  Is EOF giving any warnings about tones when you perform a full (not quick) save?  What do the tone related tags (tonebase, tonea, toneb, tones) look like in the affected XML file?

I receive warnings when performing a full save, but I always ignore it since the bass only needs one tone, which is already set as the default. And the XML file has no tones, default or otherwise.

@@Hornet871 i'm not sure what your issue is regarding EOF here as EOF only manage tone change and naming when multiple tone are used but you seems to only want to use a single tone for the bass.

 

I think it's mostly the toolkit behaviour that aren't used to which would make way more sense.

If only one tone is used for an arrangement, EOF will not export it to XML and you'd instead just need to define the one tone in the toolkit.

It wasn't EoF directly, I just wasn't sure if I should've posted it to the EoF forum, or the toolkit one. Due to implementing custom tones into the couple of CDLC files I've worked on, I wasn't aware of how single-tone arrangements worked. So I just import the settings to a new tone in the toolkit, then assign it to the bass?