Issue with Actor Instances and Expressions in Rules

SystemSystem Posts: 16
in Working with GS (Mac)
This discussion was created from comments split from: GameSalad Publishing Binaries (RC & Current).

Comments

  • blobblob Member Posts: 229
    edited April 2020

    @adent42

    This bug has been around for so long, I'm sure it's been mentioned before, time to re-up:

    In UNLOCKED actors, EXPRESSIONS within rule DISAPPEAR to value 0 when said rules are moved up and down

    @Armelline said:
    This is not reproducable for me so there's more going on than just unlocked actors and rules being moved. Anything else you can add that might help pin this down?

    @Armelline Thanks:
    i'm missing one bit: Only values entered prior to unlocking disappear when moved after the actor has been unlocked. values entered post unlocking are fine

  • ArmellineArmelline Member, PRO Posts: 5,354

    @blob said:
    @adent42

    This bug has been around for so long, I'm sure it's been mentioned before, time to re-up:

    In UNLOCKED actors, EXPRESSIONS within rule DISAPPEAR to value 0 when said rules are moved up and down

    This is not reproducable for me so there's more going on than just unlocked actors and rules being moved. Anything else you can add that might help pin this down?

    As a rule of thumb, though, unlocked actors are bad. There's very few times an unlocked actor is the best way to approach something. Pretty much just if you NEED access to the attributes like camera etc.

    Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support

  • blobblob Member Posts: 229

    @Armelline said:
    This is not reproducable for me so there's more going on than just unlocked actors and rules being moved. Anything else you can add that might help pin this down?

    @Armelline Thanks:
    i'm missing one bit: Only values entered prior to unlocking disappear when moved after the actor has been unlocked. values entered post unlocking are fine

    Yes unlock actors are bad. Using Self.IDs within a master actor is usually much cleaner and reliable agreed.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,159

    @blob is this for macOS or Windows?

  • blobblob Member Posts: 229

    @adent42 said:
    @blob is this for macOS or Windows?

    Mac 10.14.16 GS 1.25.97

  • bob loblawbob loblaw Member, PRO Posts: 793

    I've had this happen a few times. I've worked around by grouping/copying rules to the custom behaviours area, then dragging back in.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,159

    We got a repo case over here. This one might be tricky, but the team is looking into it.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024