UEFN is Now Rejecting Auto-Created Localization Folders (e.g. "pt-BR", "es-419")

General Issues and Bug Reporting
, , , , ,
1

Summary

After the latest UEFN update, folders automatically created for localization using region codes (like pt-BR, es-419, zh-Hans, etc.) are being flagged as invalid because of the hyphen (“-”) in the folder name.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

In UEFN, right-click any asset (e.g. Material, Texture, Text, Sound).

Translation and choose a language like pt-BR, es-419, etc.

UEFN will automatically create a folder structure like:
/L10N/pt-BR/MATERIALS/My_Material

Try to launch the project.

Expected Result

The project should launch successfully, since UEFN is generating valid region code folders that follow standard localization formats.

Observed Result

UEFN now blocks launch, logging errors/warnings that folder names like pt-BR or es-419 are invalid due to the hyphen (“-”), even though these were created by UEFN itself.

Platform(s)

PC

Additional Notes

The use of hyphens in language-region codes like pt-BR and es-419 is standard according to BCP 47.

This affects all types of assets being localized: Materials, Audio, Textures, etc.

3

Hi,

This warning is related to additional Verse path validation for assets, as a hyphen is not valid to use in Verse paths. We do support using an underscore as an alternative for localized assets, however the in-editor tooling has not yet been updated to prefer using this form.

For now you would need to manually rename the folder to use an underscore, eg, rename pt-BR to pt_BR.
If you get an error starting with “The L10N folder is reserved…” then you may need to toggle “Localized Content” off and on again in your Content Browser view settings.

Thanks.

1 Like
4

FORT-949860 has been ‘Closed’ as a duplicate of an existing known issue.

5

I’ve submitted a fix to 37.10 to update the in-editor tooling to prefer the underscore form for new localized assets created in UEFN.

This won’t retroactively fix any existing content, so you’ll still need to manually rename any affected L10N folders as I described above.