[Resolved] Extension properties missing conditions & actions

Hi there,

I’m trying to create a custom behavior in my project but the actions and conditions for the extension properties seem to be missing and I can’t find them anywhere.

I even went to another extension that already have events for it’s properties and double clicked on them but I also couldn’t find the event in the list.

Custom objects also seem to have the same issue. FYI I’m using the latest GD version.

Please let me know if I’m missing something or if there’s a previous working GD version that I can downgrade to in the meantime so that I can continue working on the behavior.

Thanks!

The property “Property” appears in the behaviour config, when you edit the object:


The action what is visible is the function “Function” or whatever name you gave it.

1 Like

Thanks for the reply! Sorry if my explanation wasn’t very clear or lacking some details.

I’m talking about the events inside the extension’s functions. In my example, i’m tryin to add a new action in the events of “Function”, to change the value of the property “Property”.

i have the same problem in all the other methods like onCreated or doStepPreEvents etc. The actions / conditions for the properties seem to be missing.

Example events from another extension:

img1
img2

Hope my explanation is clearer.

Unless I’m misunderstanding. You should be able to access the property with the same functions that you use for regular variables. The names should appear in the list and autocomplete.

You can so click the 3 dots at the end of the property name and GD will automatically add an expression and action to read and set the values. I believe that’s more useful outside of the behavior.

For my test Speed property it added

2 Likes

That’s it, thanks dude!

It’s been few months since I last worked on GD and I had to update several versions all at once. So I missed this point in the release notes

v 5.5.226 * Deprecate internal actions and conditions to set and compare property values in extension events: the unified variable action and condition should be used instead.

1 Like