I’m hoping to get clarity from Epic on this situation:
Tl;DR: @epic Has the “NO AI” tag rendered the MCP plugin pretty much useless?
-
Almost all the assets I have seen are marked “No” for usage with AI. (“The creator has specified that this digital content is not to be utilized in datasets utilized by generative AI programs, in the development of Generative AI programs or as inputs to Generative AI programs”)
-
The new MCP plugin permits an AI agent to act on the contents of a project in ways that would (I assume) technically treat those assets as “inputs”, given that the AI will likely need to read the assets and potentially alter those assets depending on the task (consider tasks like “Make the rock bigger/blue/low poly” or “find all the skeleton models and give them a random sword” or whatever)
A cautious reading of the “No AI” clause has me thinking the MCP plugin is utterly off limits for most practical use. I’d like to install it for evaluation as a debugging aid/project cleaner etc. I could see a great use for it in pointing it at a problematic widget or class to analyze wtf is wrong, or even to check for code quality/style etc. Id REALLY like to use it for cleaning up projects - remove unused assets, fix up redirectors that the editor just can’t seem to manage, etc. As a stretch goal, (would need fab integration) it would be good for building a manifest of all the third party stuff in a project and checking for licenses (CCO or standard?) grouping assets by author etc.
but..
I can’t comfortably do that with any ‘live’ projects. Even if this plugin works well, it is going to be relegated to building out level prototypes with grey boxes or building POC widgets in ‘clean’ projects. If I’ve misunderstood, please enlighten me. I think the current “No AI” tag has removed most projects from being able to use this plugin.
If you’ve read this far, please give it a reply or a heart to hopefully get @epic to notice and confirm or clarify. I can’t be the only one wondering.