We would like to keep our generated navdata in a specific place (outliner folder, datalayer) and thus have thought of overriding the builder WorldPartitionNavigationDataBuilder.
Unfortunately, UWorldPartitionNavigationDataBuilder doesn’t export its functions (even the virtual ones).
One way we found was to make this patch:
`class UNREALED_API UWorldPartitionNavigationDataBuilder : public UWorldPartitionBuilder`
We have noticed that some Builders export some virtual functions but not all.
The developer that built that commandlet probably didn’t think that licensees would want to extend it. Adding the API macro at that level will result in exporting all methods and should unblock you.
Depending on the changes, this might be a case where making a copy of the code and renaming the class might be more appropriate.
Our changes are not complicated and we would like to keep the base behavior (and benefit from the updates you would make ).
However, do you plan to add yourself the missing “export keyword” like you did for “UWorldPartitionMiniMapBuilder” for instance? Because obviously, the fewer patches we have to maintain, the easier the integration of a new UE version is