Strangely, if I delete Playmaker from the working shared project and reimport Playmaker from the Asset Store, the references once again break.

This would mean it doesn't have anything to do with the package export process, but perhaps a change in Playmaker?

No files are changed according to my version control, however there is one major difference. Playmaker from the Unity Asset Store does not contain the Assets\Plugins\PlayMaker\WP8 directory.

Upon restoring the WP8 directory all of the script references are restored!

A few of the FSM components are referencing the WebGL\Playmaker.dll as well, which explains why there were a few FSM components left working.

Is there a reason Playmaker no longer includes this DLL?

Why does this particular template rely on it? It's not like I ever had the option to choose from which DLL I created the FSMs with did I? IMO all FSM components should be using the default DLL that is always included with Playmaker.

Seeing as I can't redistribute the WP8\Playmaker.dll with my template, any idea on how I can remedy this?

TLDR: Breakout Pro cannot be exported to a unity package without losing all Playmaker FSM component references.

I updated all of my Playmaker templates on the Asset Store to Unity 2022.3.22 and Playmaker 1.9.8 using the most recent Asset Store Publishing Tools v11.4.0. All of them worked except for Breakout Pro.

Before submission everything was working perfectly, however once the updates went live I started getting support emails about missing scripts on all game objects.

Upon importing my updated Breakout Pro template from the store myself, they are indeed missing practically every single FSM component reference on almost every game object in the project.

It appears as though the Asset Store Tools are stripping Playmaker component script references, but ultimately I don't know if the issue is with Playmaker or Unity seeing as it only affected one of my templates.

I then tried using the Asset Store Uploader to "Export" rather than export and upload as I did before, and the exported Unity package also has this problem right out of the gate. I also tried the standard right click / Export Package and still the same issue. I even tried a custom project export script and the results are the same.

This is a pretty serious issue and I'm hoping to get it figured out as soon as possible.

I emailed you a link to the project so you can see for yourself.

Thanks!

yes but it should appear. I'm talking about my hand cursor and not the arrow

I made some actions to work with an Airplane Controller asset from Unity Asset store. The airplane asset is not mine. I just made actions to work with it.

https://assetstore.unity.com/packages/tools/physics/simple-airplane-physics-toolkit-lift-drag-thrust-146915

That links is for the asset.

Actions are attached as package to this post.

What version of Playmaker are you using? This should be fixed in 1.9.8.

Unity had a typo in some of their styles: ToolbarSeach instead of ToolbarSearch.
It was that way for 15 years and then they decided to "fix" it, breaking any tools that used the name with the typo. I was hoping they would "fix" it again by adding a duplicate style to restore the typo version, but I'm not sure if they will do this. Either way you shouldn't get the error in 1.9.8. If you still get it let me know!