GameFeatures plugin broken ?

Development Programming & Scripting
,
1

Hi everyone,

I’m trying to get my hands into the GameFeatures plugin. But it looks like that plugin doesn’t work at all.

Even the most basic setup is not working.

Just trying to follow the official presentation of the plugin is not even possible.

You can enable the plugin for sure but creating your own standalone feature ?.. nope

So to explaining everything after I enabled the plugin and put the GameFeatureData as a Primary Asset Type. I create my own plugin/feature (Content Only or With C++, both don’t work the only difference is when you select With C++ you have a compile error and the plugin is not even created… great) So the GameFeatureData open aaaaaaand, first error it says a big “ErrorRegistering” because it can find the asset GameFeatureData asset already open… Just save and it’s good.

Just restart the editor and it’s NOT good. The folder is gone and you can’t register it anymore.

Except you just enable it from the Plugin window which make the GameFeature plugin completely useless as it’s creating an entry in the main .uproject file.

It works perfectly with ValleyOfTheAncient example but I think they produced side code to side load the plugins and register them.

Dosent anyone successfully made that plugin worked or found workarounds waiting Epic’s team to fix it ?

Best regards everyone,

Alex

2

Ok so for the future users of the plugin.

By default when you add a GameFeature via the Plugin window. In the *.uplugin file it sets

“EnableByDefault”:false,

Just put it to true and voilà the folder appears magicly in the Source Panel.

Allé now let’s try to add some code :wink:

3

Same, on the *.uplugin of your feature.

Write :
“ExplicitlyLoaded”=false,
(To keep a trace of it, otherwise you can delete the line. It’s considered false by default)

To avoid the failure when you set your GameFeatureData to “Installed” state.

My guess is that if your GameFeature depends on other ones. The engine should not take care of loading/unloading but you have.

And accordingly to PluginDescriptor.h, it’s basically what it says. The loading/unloading phase will be handled by another entity during the program lifecycle.