295 break the protection for non-exist object's flag

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Fusion usually will return 0 or "" if the given alterable value doesn't exist, but 295 seems to break this protection for flags.
    I only tested the expression part, IDK if this also exists in other parts like conditions and actions. It may be dangerous as it may break existing projects.
    For normal cast that convert param1 and param2 directly seems to be Okay, but will crash if param more than 2, which means you need to use the macro to read them.

    How to reproduce:

    Please login to see this picture.

    Please login to see this picture.

    Please login to see this picture.

  • OK, I'll check.

    PS: the build 294 also crashes in this case, no difference in the build 295.

    Thanks for the reply.

    I was back to work on an old project back to 2021 by local fusion community member's demand, and got several crashes. So the change might be made in 293 or 292.

    Topic relative to this project:
    Please login to see this link.

    Now immediate event from non-action will cause crash, but in the post link above, an event in a disabled group also triggered crash.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!