I used on Start of Layout, but that's interesting.

I used On Start of Layout > Check if OR > For Each

Maybe the best and worst thing about programming is how many different ways you can do the same thing.

> Almost. The condition is a string and it's an OR.

>

> Global string = Text

>

> YourVariable = "Five"

> OR YourVariable = "Eight"

>

> That said, if I drop the OR block and only compare for the "Five", it still doesn't work.

>

> If I change the YourVariable from a string to a number and check if it equals 5, it does work. But I need to check a string, and I don't understand why checking for a string would break it if checking for a number works fine.

I see — I don't think you can put OR blocks and Triggers in the same block, but I might be wrong.

I've always separated them like this. This approach also stops the code from checking "YourVariable" every loop, which can slow things down, and just check whenever a Sprite object is created.

But ROJOHound is right, it'd easier to see what your code looks like.

The issue isn't the OR block. I'll show.

Is this what you're trying to do? Both of these work for me:

Almost. The condition is a string and it's an OR.

Global string = Text

YourVariable = "Five"

OR YourVariable = "Eight"

That said, if I drop the OR block and only compare for the "Five", it still doesn't work.

If I change the YourVariable from a string to a number and check if it equals 5, it does work. But I need to check a string, and I don't understand why checking for a string would break it if checking for a number works fine.

1: We don't know what variable, global, or instance you are talking about.

2: Objects can't be selected until the next tick.

3: To deal with that you can manipulate them in the event they are created.

Not sure how this relates to my issue.

The runtime will also move objects to a different layer if the layout doesn't have the same number of layers. For example if an object is on layer 5 and you move to a layer with just three layers, all the objects on the higher layers will be moved down to the top layer.

Does that mean I need to be making every layout with the same number of layers, even if I don't need them on every layout?

I believe when you switch layouts, global objects are transferred to a layer with the same layer number, not with the same name.

I think in your case it may be better to make the layer "UI" global. And disable global attribute for UI objects.

This seems to be the behavior I'm looking for, Thanks! Is there a way to tell it not to override this layer on certain layouts?

Just use the condition compare variable as sub condition of On Created..

You might think so, but no, it doesn't matter which order I did these things.

But that's a good example of my problem. I *frequently* encounter situations where the most straightforward and logical option tends to be a time-consuming headache.

I really, really want to do something when an object gets created, that makes perfect sense to me.

In this case, I'm lucky that all the objects already exist when I start the level (manually placed where I want in the editor). So I can:

(C)Start of Layout > (C)Check Condition > (C)For Each > (A)Do Stuff

And maybe I can presume that for things created dynamically, the condition that allows them to be created might be the same one I would want to use with the (C)On Created, and that conflict doesn't come up.

It just feels like I spend a lot of time doing something that makes perfect sense, and then have to trial and error my way around it without ever really understanding why I wasn't allowed to do it.

Seems crazy to me there is no opacity to set the strength of this effect. Am I just missing it?