usmap: same class name different namespace

[AndrewSav]

palworld has the likes of:

struct ABP_ChickenPal_Implemantation::FAnimBlueprintGeneratedConstantData final : public FAnimBlueprintConstantData
struct ABP_ChickenPal::FAnimBlueprintGeneratedConstantData             final : public ABP_MonsterBase::FAnimBlueprintGeneratedConstantData
struct ABP_CuteFox_Implementation::FAnimBlueprintGeneratedConstantData  final : public FAnimBlueprintConstantData
struct ABP_CuteFox::FAnimBlueprintGeneratedConstantData                final : public ABP_MonsterBase::FAnimBlueprintGeneratedConstantData

usmap does not hold namespaces just names so we end up with something like

    "AnimBlueprintGeneratedConstantData": {
      "super": "AnimBlueprintGeneratedConstantData",
      "propertyCount": 0,
      "properties": []
    },

in the usmap, we cannot tell the difference between:

• ABP_MonsterBase::FAnimBlueprintGeneratedConstantData
• ABP_ChickenPal::FAnimBlueprintGeneratedConstantData
• ABP_CuteFox_Implementation::FAnimBlueprintGeneratedConstantData
• etc

Was it considered to expand usmap format to include namespaces?

[alexbowe]

I'd really like a solution to this too, as I'm seeing naming collisions in Mistfall Hunter.

One possible solution is the PPTH extension, which stores package/object paths for each struct and enum. It is already emitted by UE4SS and consumed by UAssetAPI. There was also a PR into this repo to add it, but it was closed.

@FabianFG Is this something you would consider accepting a PR for? (Either the PPTH extension or another design)

[NotOfficer]

I will propose something later/tomorrow to fix this + another limitation.
Not a fan of what UE4SS made...