Issue of "Create object" event

[ASD]

create_object_issue.zip
Created object from event of second line.
Is this a bug?

[Anders]

Your first event is called 'never' so the object that the others should be created relative to doesn't exist since it isn't created.

When you call the 'create object' action and MMF2 has no object to create it at, it just have to create it at 0,0

As a side-note, since you use "Compare two general values" to test if 'Active 2's angle < 0.5 then MMF2 normally picks the last created instance of 'active 2' and return it's angle, but since there are no instances of 'active 2' MMF2 is forced to return 0 and since 0 < 0.5 is true the object is created anyway.

Also *if* there were any instances of 'active 2' then 'active' would have been created relative to *each* 'active 2' object you have regardless of their individual angle as long as the last created instance of 'active 2' meets the angle < 0.5 criteria.
This can be a somewhat confusing behavior and not seem logical, but it is in fact the right thing to do.

If you had used one of 'active 2's own conditions to check some criterias, the 'create object' event would not even have been fired if there were no instances of 'active 2' that met the criteria. This is because of the object selection system in MMF2. Remember that each condition is meant to "pick out" the objects you want modified or do something with. Compare two general values does not to one bit of object selection but object's own conditions do.

It is important to learn the differences between 'compare two general values' and an object's own conditions.

[SEELE]

because there in no event so test & select the objects angle, i would use.

always+
-set alterable value (?) to angle
;this would make each objects value (?) there own angle

+if value(?)=???
-bla bla bla

[00J]

Did it work? Test it and see.