Don't compute the initial value of dynamic properties in the editor#14650
Merged
uckelman merged 1 commit intoJun 3, 2026
Merged
Conversation
This prevents evaluation and replacement of beanshell expressions for the initial value of a dynamic property while in the editor. Expression evaluation is deferred to the player module.
riverwanderer
added a commit
that referenced
this pull request
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This prevents evaluation and replacement of expressions for the initial value of a dynamic property while in the editor. Expression evaluation is deferred to the player module.
I did some simple tests initializing from a global property with pieces in the Piece Palette and At-Start stacks. This change may make it harder to debug issues with expression evaluation being deferred to the player.
Closes #13609