Using copied behaviors is dangerous

[oripessach]

I'm seeing this in build 9001.

I have a scene behavior that was copied from another behavior. Let's call them Behavior A and Behavior B. 

I have an actor that needs to call a custom block in Behavior A or in Behavior B, depending in which one is used in the scene.

It seems like only the block in Behavior A is accessible. Something gets seriously messed up when scene behaviors are duplicated.

The attached game has a scene behavior (Behavior A) that had a custom block when it was duplicated as Behavior B. Behavior B's custom block and Behavior B itself don't show up in the palette when editing an actor behavior, for example.

Trying to work around this by inserting code like:

sayToScene("Behavior B", "_customBlock_CustomBlockA");

Into the actor's behavior does seem to work, but you have to admit that this is not right.

[Justin]

So the scope of the issue is limited to how custom blocks are handled, right?

• Issue Assigned from (none) to Justin

[Justin]

Perhaps related: http://community.stencyl.com/index.php/topic,47022.0.html

[Justin]

Same as above: http://community.stencyl.com/index.php?issue=399.0

[rob1221]

I have a scene behavior for my game that holds all my global custom blocks.  I shared two of those on the forum by copying the first behavior and deleting the blocks I didn't need to share.  Today I just found out that the same blocks I deleted in the second behavior have also been deleted in the first.

[irock]

Last night I ran into the issue where when you duplicate a behavior and delete the custom blocks in the new duplicate behavior, they're deleted in both behaviors.

I think fixing this bug should be a priority.

• Tags added: resources

[Justin]

Fixed in b10443.

• Status changed from New to Resolved

• Tags added: 4.0.2

• 4.0.2
• resources

 Copied Behavior Test.stencyl (388.4 kB - downloaded 769 times.)