I like the idea of a version of PlayMaker for the editor. You could build (and share) a lot of useful editor tools visually, which would be very cool. However, I think it would be a separate asset, focused on that task: with editor specific actions, play mode stripped out to simplify the UI, etc.

Scriptable brushes for Tilemaps is an interesting example. Would you want to create new rules, or procedurally paint tiles, controlled by an FSM? Is automation the main goal? Or building little widgets and controls that can interface with editor scripts?

It's hard to know if this could turn into a request for a feature or if it isn't just a way to launch a little discussion, but there is a simple fact that has been holding true thus far: Playmaker's FSMs only work in Run mode and in general it seems like Playmaker wants to live in its own bubble, rather jealous of its contents.

In Unity, the script components (but in fact almost any kind of component) offer the developers an ability to tweak values in the Inspector tab. Through scripts one can add menus, boxes to tick, fields to enter different types of values or to reference other GameObjects or assets.

In comparison, the FSMs that show up in the Inspector don't make access to FSMvars very easy, they are hidden away, cramped and organized in categories that sometimes may feel a bit arbitrary such as "in" and "out", making the Graph View super-mandatory for tweaking anything, instead of having FSM-components that would be explicitly constructed to show up in the Inspector.

Eventually if Playmaker could allow FSMs to be controlled in a straightforward way through the displayed corresponding component on any GameObject, acting as a practical shortcut, this could open up the way I suppose to making tools with Playmaker for the Editor interface, and perhaps going as far as making scriptable objects in Playmaker.

For example I was looking at scriptable brushes for Tilemaps. Why couldn't this be handled with a FSM? Say you need to bring a simple change to a brush function, something you could even toggle on and off to use either the default function or the modified one.
You look at the example given and while the script is a bit verbose it's not much complicated in its fundamental structure.

Does Playmaker really have to only exist within the Run mode or could it be extended to handle anything pertaining to the Editor environment, even if I know it's called Playmaker and not Editormaker?

Hi,

I'm having an issue with the json save/load actions from the ecosystem. I can save a file and load it once just fine, sometimes it will even let me do it 4 or 5 times, then I start getting this error every time I try to save:

IOException: Sharing violation on path C:\Users\name\AppData\LocalLow\My Company Name\My product name\MySaveFile.sav

I've read this error can occur when other programs are accessing the file, so I made sure all my file explorers are closed, didn't help.

I have a new empty project with only playmaker installed, in my test scene there is only one gameobject with one FSM, with an empty start state, a json save state and a json load state.

Using unity 2022.3.44f1

I've used json save/load on entire projects before and I've never had this issue...Any help would be greatly appreciated!

[UPDATE]
I set up a state to delete the file every time before the json save happens, and found that access was denied with the same error message upon trying to delete the existing file...So perhaps it is not an issue with json save and somehow my computer is the one blocking access to that file? I tried disabling virus protection, that didn't help...

The issue that you describe is most likely due to not leaving your save state. Don't put the loading in the same FSM where you're saving. Example playable Demo: https://colpolstudios.itch.io/enemy-saving-and-loading-with-playmaker-arraymaker

thanks there is still a lot to do before full release but we are working hard ^^
I´ll write an update in about half a year.

Ah nevermind, solved.

Theres a RayCast From Screen action (I think I got it in the ecosystem browser). While it doesn't return the hitpoint, there is a subsequent GetRaycast Hit Info action to get the details