Cannot package project for a plugin that build correctly

As the title says, I get an error for a plugin I made. But I keep getting errors. I can’t figure out how to make it all work.

Let’s start from the beginning.
First the plugin:
-It builds
-It works
-It does not package properly. I get an error for “Element” not being correct. I do not understand as the plugin build without issues.
Even worse, it still output the plugin. I get the plugin at the end. And it works as well.


UBA-UnrealEditor-Win64-Development.txt (106.8 KB)

So after trying that the plugin worked, I added it to my game. Works as expected. Everything runs fine. Until I try to package the game.
Then and only then do I get an error because somehow, it cannot make sense of FPermissionListOwners type on line 17. If it couldn’t figure it out, it shouldn’t build in the first place.

UBA-StealthGame-Win64-Shipping.txt (33.3 KB)

I don’t know why it doesn’t work.

1 Like

The error requires the use of the character “;” (semicolon) with relation to your sockets function.

You must have done this in C++, so make sure to place it.

1 Like

Hi, have you got "include “Misc/NamePermissionList.h” in your source file? The build system is more strict about include folders - that could be what’s happening.

1 Like


I believe the semicolon are corrects.

It says BEFORE sockets. So try doing that. You have only after.

My skills in C++ are rusty, however, it may need to be in this syntax:

FPermissionListOwnders; sockets;

1 Like

@RecourseDesign , always good to see you.

Yeah, I mean, I’m just reading the error. You create plugins professionally, so @Elgatee , you could also try what they suggest.

2 Likes

FPermissionListOwners is the type of the sockets variable. I can’t really put a “;” before. The line before the semi colon error says it cannot make sense of “FPermissionListOwners” thus why it thought sockets needed a semi colon before.

Unreal wants you to put a “;” somewhere before.

Again, my C++ is rusty, so I can’t remember a lot of things. But it won’t work until you do.

EDIT:

Oh, I see, I thought what was in red were the only two errors.

Then, at the moment, I do not understand why Unreal is not recognizing the identifier.
That’s why it requires the semicolon; because it ignored that line.

1 Like

I did not have it. The error no longer show up, but I still cannot package properly.
Error in plugin packaging is the same:
UBA-UnrealEditor-Win64-Development.txt (106.8 KB)

But error in game packaging has changed. Now I no longer see something obvious that I can at least point out.
UBA-StealthGame-Win64-Shipping.txt (30.8 KB)

1 Like

This time it’s looking for a definition for UOSCServer - you’ll need to add # include “OSCServer.h” to any of your files referencing that.

1 Like

I don’t think I use that one? My plugin is nothing more than a single class with a single function modified. Nothing related to servers. Not in my game, not in my plugin.

Edit: Alright I see the error. but the error happens in Core. Not in my plugin. Could it be an issue with my installation of inreal engine itself?

That is possible - it might explain the error with the null value in your first packaging logs.

If you’re using the binary version you could verify it to see:

The error comes up when compiling around your plugin (just after) from a file 'VrmVMCObject.cpp" which doesn’t exist in the engine code.

------ Building 7 action(s) started ------
[1/7] Compile [x64] APCharacter.cpp
[2/7] Compile [x64] APCharacter.gen.cpp
[3/7] Compile [x64] ImprovedPerception.cpp
[4/7] Compile [x64] ImprovedPerception.init.gen.cpp
[5/7] Compile [x64] VrmVMCObject.gen.cpp
E:\UE\UE_5.4\Engine\Source\Runtime\Core\Public\Templates\PointerIsConvertibleFromTo.h(19): error C2027: use of undefined type ‘UOSCServer’

2 Likes

Thanks. VrmVMCObject is from VRM4U. Another plugin that I added. I didn’t think it could be the cause of the issue since it’s apparently well maintained and nobody seems to have my issue. I’ll put the issue on their git and wait there. Thanks for all the help and I’ll keep you updated :wink:

3 Likes

As promised, I keep you updated. TL:DR: the plugin’s author has added the dependency. The plugin no longer causes issue for me.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.