(Suggestion) Allow Developers to specify Additional Plugin Search Path

Development Pipeline & Plugins Plugins
,
6

That confirms what am seeing with the documentation.
Also i might have found an undocumented fix for my problem of being able to choose Plugin path

By adding AdditionalPluginDirectories section to project.ini file

"Plugins": [
		{
			"Name": "Bridge",
			"Enabled": true,
			"SupportedTargetPlatforms": [
				"Win64",
				"Mac",
				"Linux"
			]
		}
	],
	"AdditionalPluginDirectories": [
		"../../DevPlugin/UserPlugins"
	]

Initially project edited with plugin path will pick up every plugin in said path and ticked in editor as selected. So you have to go untick which plugins you dont need. But thats not really necessary cause i think plugin not included in build.cs is not part of the build anyway.

One thing i noticed is i put in the full path initially from c root C:.…
And the project itself changed it to relative path as seen above.

Thanks to those that help to highlight the deplorable state of unreal documentation, which borders on information hiding, Cause it helps to know this ahead especially if you new to the engine like myself.
So that as been mentioned source code, forums, and answerhub far more useful than the documents.

At this point we have google to thank for being able to use this product

1 Like