Behavior does not exist and exists at the same time

All right, this one's a real stumper. In the behavior, the first time I try to change something in the Walking class (part of the Run and Jump kit), I get a console warning saying the behavior doesn't exist. When I try to change it via a key later, it does exist. I don't have these problems with Running, Wall Sliding, or Air Jumping.

Even weirder is something I forgot to get a picture of: If I add in commands asking whether or not Jumper has the behavior Walking, it says "true"...and apparently, it's even enabled as well. So what's going on here?

EDIT: Whoops, something went wrong. Those twos should be in the other box and the variable name in its place. That's not the problem, however.

I guess it says it doesn't exist the first time because it isn't initialized yet. I can't say for sure, though. Perhaps Greg knows more.

Maybe we should initialize every class used in scene (both scene and actor behaviors) BEFORE scene will load? Sure it'll increase scene loading time a bit but that way we'll avoid such errors in future.

How would I go about doing that?

there is a problem with using messaging blocks in the when created section of a behavior. I experienced this with another user and it was a very similar problem to this. Basically the behavior is not yet initialized, therefore the functions don't "exist". The way to solve this problem is to wrap all of your messaging blocks in a do after .1 seconds block. it should solve the problem.

@ColorPrinter You can't. Stencyl team must change engine to allow this.