Solved it.

Silly me. That final state of damage, I didn't have it going to another state after it was done. So it would sit on that state, adding -1 to the health variable every frame, which confused the health FSM and got it stuck.

I just told it to go to finished and then to a final state when done and it seems to work great now.

Hi guys, I made a mobile game for children "Jungle Town - Birthday quest". I used Playmaker at 95%. Thanks to the Playmaker team, you created an amazing product.

https://apps.apple.com/app/id1454087759


More information see: http://funtyx.com

Hi all,

This is a weird one.

I have a Damage FSM set on objects, and I have a Health FSM set on my Player. The Damage FSM on objects affects player health by adding -1 to the global health variable I have set up, which in turn affects the player health FSM by using int switches.

Everything works great until I apply the damage-causing FSM to an object in motion (using the Move Towards action).

When the object is in motion and the player hits it, it's fine until it gets to the last heart. Once it gets to the last heart and they collide, the global variable for health goes crazy and rapidly decreases from 1 to negative hundreds, thousands, etc. And then the FSM for Health on my Player remains stuck on 1 health. I don't understand what the hell is going on here. I will supply the screenshots. I am highlighting where in the Health FSM it gets stuck.

Remember, this all works perfectly when the object the player collides with is not moving.

I tested with test sheet. it is creating cells and etc. Sheet should be public and should be edited by anyone 
And there is no playmaker actions

https://novack.itch.io/google-sheets-for-unity

Hey ppl! Just jumping in to clarify that using Google Sheets For Unity, the spreadsheet doesnt need to be public. The page explains that in detail, but to quickly summarize: those are constraints for the public online demo (otherwise the demo would be very limited), not really for the actual asset.

Heya,

So I think I stumbled onto a bug but can't seem to track it exactly down. 

Basically I have a GO that holds an array of all the resources it needs (Construction Site) and also adds itself to the job list array on another GO(Empty Job Manager).  A third GO (Builder Unit) then checks the Job list and finds a work site.  Once found, it checks the resources needed and collects what he needs.  This all works fine until the Construction Site is destroyed.  Once a new site appears for the unit to check the resources again, this null error appears.

At first I figured it was my logic somewhere but a break point right before the Get Next action for the Missing Resource Array shows everything to be correct.  The Builder unit has the correct GO Variable, Array Reference, Reset Flag, Ect. What really makes me think its a bug is by simple deactivating the Construction site rather then destroying it fixes this issue. It's like destroying the GO causes a Ghost reference for that Get Next array to try to find

Now I've tried to Isolate this by re-creating this in a new scene but couldn't.  Has anyone else notice this happening or knows the cause that it could be?

Thanks