Scripting Language extensions via plugins

[robert.manuszewski]

@;97698

I’ve started implementing a CLR binding and have run into an issue with FScriptContextBase::CreateContext(), it can only create a Lua context, and there’s no way to override that behavior. Perhaps some sort of registry of FScriptContext factories is in order, the various ScriptPlugin(s) could then register their factories, and FScriptContextBase::CreateContext() could pick the relevant factory at runtime based on some sort of identifier passed in by the caller.

The idea behind the plugin is that you only have one script integration active (otherwise supporting multiple integrations can get tricky). I’d suggest changing ScriptPlugin.build.cs and ScriptGeneratorPlugin.build.cs to support different script integration (essentially defining WITH_SOMEOTHERSCRIPTINGLANGUAGE in case Lua is missing and there’s another one present).