I find that it is because LanguageSource.Assets is added by loading asset in Resources folder.
However, In LocalizationEditor.cs
GUITools.DrawObjectsArray( mProp_Assets, false, false, false, testAddObj, testReplaceObj, testReplaceIndx, testDeleteIndx);
Since allowResources is false, so it will auto destroy.
The administrator has disabled public write access.
LanguageSource Inspector Assets auto destroy
1 week 11 hours ago #3041
The problem is that LanguageSource.Assets shouldn't contain any asset from Resources.
The idea of that array is that it includes references to those assets that the plugin can't load at runtime because they are not in the Resources folder.
If you need to add assets (sprites, fonts, etc) from the resources folder, just add the path+name to the translation.
Term: "MY_FONT", English: "Arial", Spanish:"CustomFonts/Comic"
That will automatically load the Arial font from "Resources/Arial" when in English, and the "Resources/CustomFonts/Comic" when in spanish.
However, if "Arial" is not found in a Resources folder, then the plugin will look for it in the Assets array.