Ehum, yes, me again, sorry! This is the last post (for today).
I'm pretty sure this is again something that no-one else has complaining, but it seems that in scene actionLists may generate a ridiculous amount clutter into the scene files.
For example one scene containing mainly 5-10 minutes of dialogue was about 12Mb in size (when asset serialization forced to text). After looking what made it so big, I noticed "(Clone)" being repeated 930 618 times, in that one scene! Every repetition was attached to a m_Name variable (about 3000 of which exist in the file).
I guess that under the hood that comes from moving and replacing the actions a lot, though "(Clone)(Clone)".. is not visible anywhere. I also tested removing all "(Clone)"-strings with a text editor and running the scene in Unity. Seemed to work without issues! This changed shrunk to scene file size from 12Mb to 4.5Mb.
All in all I'd estimate that the useless "(Clone)" in all our scenes has been wasting maybe 30 - 50Mb of bandwidth, which under iOS at least seems to become even bigger in the build. So, I'd say it can be significant, especially on mobile!
I could probably do the texteditor-removal trick for all scenes, but maybe moving the ActionLists from scenes into assets does the trick also? Haven't tried that yet.
I'm not expecting
@ChrisIceBox to fix this (serialization/cloning problem), but this is at least a heads up. It's probably also related to the issue of slowly loading scenes (with lots of in scene actionLists):
Comments
As for existing ones, it's better to have an Editor script that goes through all ActionLists in your project and makes the correction in one go - as opposed to auto-checking each Action when viewed in the ActionList Editor or something.
The issue is with the (internal) names of the Actions themselves, which are ScriptableObjects stored within a MonoBehaviour. This could be done regardless of your project's Asset Serialization setting, but I'm unsure how to make it available. Having a dedicated button somewhere may make things confusion, so I'm thinking either as a new page in the wiki, or having it done "behind the scenes" when gathering text in the Speech Manager.