Are Name-variable values "Internalized" ignoring case in packaged builds?

[FortunaCournot (Screenflow)]

I have an issue when calling CPP code from blueprints. The values of Name-type variables have different case (e.g. capitialized) then the values i provided in the call (lowercase).

The only explanation i have for this, if they use internalization (forcing equal values have equal address) on literal strings to reduce the size of packaged builds. But in case of Unreal they also do the internalization check ignoring the case.

Any ideas?

[S-Dot]

Isn’t the name variable meant for file names? So they would ignore upper/lower case?

[JaredTherriault]

Why do certain FNames get capitalized in packaged builds?

The case of an FName depends on the first instance that is created with that unique (case-insensitive) string. If you create the FName for “x” and other packages (or code) uses the FName “X”, whether the x is uppercase or lowercase will depend upon which of those is encountered first by the engine. You can not change this behavior so make sure that all uses of the string treat the FName as case-insensitive.