When you use callThreadFunction, it turns out that the function called will, if it has any commands that use the affiliated scriptable object, use the scriptable of the thread doing the calling, and not that of the thread which was called. Consequently, I have to stick in a setThisThreadScriptable "Mother" for instance, but that is just a temporary hack, so this should be resolved: if we're calling a function in another thread, it should use the scriptable of the other thread. Modifications will be made to put this in effect.
When you use callThreadFunction, it turns out that the function called will, if it has any commands that use the affiliated scriptable object, use the scriptable of the thread doing the calling, and not that of the thread which was called. Consequently, I have to stick in a setThisThreadScriptable "Mother" for instance, but that is just a temporary hack, so this should be resolved: if we're calling a function in another thread, it should use the scriptable of the other thread. Modifications will be made to put this in effect.