If we would like to offer players/modding community option to extend the mutable parameters values in customizable object, how should we approach it correctly?
Is the Mutable tech ready for modding? Does it already support modding through data registry for example? We would like to combine mutable modding with GameFeature plugins.
Hey there,
Mutable is not mod-ready. The primary issue is that you would need to recompile the graph once you registered new assets and that is something that you do at cook time.
The closest we have to modding right now is the new dataless assets feature in 5.7. With these, you pass in the assets you want to use as data, and the output is the model. The feature is highly experimental right now, so we recommend trying it out, but not using it at the moment. That said, it removes the need to recompile the graph, which could serve your needs, but depending on the extent of the modding you want to do, there is most likely still more to do.
Dustin
I’m still experiencing the same issue. I also tried the dataless approach, but it did not resolve it.
My current implementation is as follows:
I have a main Character Customizable Object (CO) in the core project.
I have several character clothing mods, which are linked as External Objects to the Object Groups in the main Customizable Object.
In the editor, the mod clothing works correctly and attaches to the character through the assigned clothing object groups.
However, in the packaged build, the clothing assets are no longer linked to the character, and they do not appear in the Customizable Object Instance.
Could this be caused by an issue in my current setup, or is there a recommended fix for getting External Object-linked clothing mods to work correctly in packaged builds? Do the Epic plans to give a fix for this in future?