Packaging fails due to compile error in BlueprintTaskForge

[samaursa]

What happened?
Packaging fails with a compilation error. The error log is included below. Replacing the main file (BtfTaskForge.cpp) with the version I shared earlier fixes the issue. With the latest commit, standalone mode no longer crashes.

How do we trigger it?
Package a project that includes BlueprintTaskForge at commit bc50064f2cebc8f5c299f2648bdc73182cc38d5c.

What did you expect instead?
Project should package without compile errors.

Any logs or screenshots?
Error log: https://pastebin.com/xDMA0K1z

Your setup

• Unreal Engine version: 5.6.1

• BlueprintTaskForge commit: bc50064f2cebc8f5c299f2648bdc73182cc38d5c

Anything else?
This seems to be the same issue reported earlier in support. Replacing BtfTaskForge.cpp resolves the packaging error.

[Variann]

Blueprint extensions either were always editor-only, or were recently changed to be editor-only. I am very certain it wasn't, but I could be wrong. This means the entire "Allow Instance" feature does not work as most of the data is stripped when packaging the project.

I was afraid of this and did share those worries when we reviewed these changes. The backup-plan was to reparent Btf_TaskForge to UActorComponent and use the ComponentTemplates array, which is used for runtime code all over the place. It's how all the "Add Component" functions work.

I did quickly replace all the extension code references and the ClassGeneratedBy stuff, just to see if it would package and it did.
I then tested reparenting the tasks to UActorComponent, but wasn't able to go too far. At the moment I'm too busy to try and do much testing to solve this.

[Variann]

I'm going to leave a note here, in case someone else will take a crack at this problem before I will. I will need this feature for my game, so I will 100% someday take a look at it, but that might be months from now.

I had completely forgotten that Asset User Data exists and is heavily used by a lot of parts of the engine. I quickly went over it and it looks like it is 100% runtime accessible. The idea would be to create a AssetUserData and store a TMap of the Guid's and then an instance of the class the node is supposed to spawn.

There is 1 example in the engine of using an Instanced object and a Asset User Data, though it is editor-only.

It would be wise to quickly test with some dummy assets whether this data is serialized properly. I assume it is, because actor components have separate arrays for non-editor and editor-only

If this works, then the API changes required would be extremely minimal.