Expose an instance of the 4 layer modular architecture material as an inheritable material.
Use Case
Creators can efficiently create modular content which UEFN users are comfortable with. This is the modular architecture equivalent to the FN Base Material (which is a far simpler, single texture material).
This material can be instanced into the project tree and referenced by custom modular architecture
Value
More efficient runtime cost (compared to multiple material elements on a single simple mesh like a floor / ceiling combo).
Native TextureData support increases flexibility and visual consistency.
Native TextureData support also makes custom content more accessible by leveraging a workflow with which they are already comfortable
Ensures multi-platform scalability as the underlying Epic material is relied upon
Thank you! I understand FN probably doesn’t want to be too prescriptive in general. But I’d encourage exploring the thought that exposing more of FN’s own content creation workflows would go a long way in ensuring content is generally of higher quality. Additionally, other map creators wouldn’t have to learn many unique asset workflows when subscribing to marketplace content (at least for content that strives to visually and technically align with the core Fortnite experience).
Additionally, the validation and Epic review process could see potential efficiencies if underlying implementations are inherited. It’s a win win for everyone really