Creating a Custom Playset adds an illegal PrimaryAssetTypesToScan override and blocks session launch

Development Programming & Scripting
, ,
1

Summary:

Creating a Custom Playset automatically modifies:

GameFeatureData.PrimaryAssetTypesToScan

UEFN adds the internal _INT/Playsets directory, but ValkyrieValidator considers this automatically generated value an illegal property override. This prevents the project from launching a session.

The issue does not appear to be related to a specific asset or content set. I reproduced it using different Fortnite assets inside the Playset.

UEFN Version:

41.30
Build: ++Fortnite+Release-41.30-CL-56430492
Platform: PC / Windows

Steps to Reproduce:

  1. Open the affected UEFN project.
  2. Create a separate Level.
  3. Place any supported Fortnite actors or props in the Level.
  4. Enable “Is Playset” in World Settings.
  5. Save the Level and allow UEFN to generate the Playset.
  6. Validate the project or launch a session.

Observed Result:

UEFN automatically modifies GameFeatureData and validation fails with:

/TheForceAwakens/GameFeatureData Illegal property override:
GameFeatureData.PrimaryAssetTypesToScan has an override of:

((PrimaryAssetType=“Playset”,
AssetBaseClass=“/Script/FortniteGame.FortPlaysetItemDefinition”,
Directories=((Path=“_INT/Playsets”))))

The default value is empty.

The Output Log also sometimes reports that the generated Playset asset is immediately deleted and reverted:

LogFortPlayset: Deleting unreferenced asset:
/TheForceAwakens/_INT/Playsets/PID_PS_SW_FirstOrderTower_A_Source

SourceControl: Reverted 1 file.

Expected Result:

UEFN should generate the Playset without creating an illegal GameFeatureData override.

The generated Playset asset should remain available, and the project should still be able to validate and launch a session.

Workarounds Attempted:

Resetting PrimaryAssetTypesToScan to its default value removes the validation error temporarily, but enabling “Is Playset” causes UEFN to add the same value again.

Asset Actions > Fix Validation Issues reports that 0 objects were updated.

Additional Information:

The problem appears to be caused by the Custom Playset generation process itself. It can be reproduced with different assets, so it does not appear to be specific to Star Wars content.