Yeah I've been doing that, but since I'm still new-ish I wasn't aware of the importance of making sure that first instance gets created in what I'm calling the "Master" sheet. I'll dig through the JSON and see if I can correct the 'first id' somewhere.

Wonderful, so if I accidentally added it to a scene first, then to master, I'm kinda out of luck for that object type? Any way to fix this in the json files?

You shouldn't mix movement behaviors. Tile movement is for tile based games (typically top-down). Platform behavior is for platform games. There's a "Custom" movement behavior if you're trying to get fancy. We'd need more context if you want more help.

I have some objects that I instance. An example would be a Tileset, a Sprite (specifically a Trigger), and NPCs.

Now the tileset of course can be drawn on, sprites have instance properties that can be set, etc. I, by convention, drag at least the first instance into a "Master" sheet so there's always that first core instance. I can also drag multiple instances, and set each of them to have different instance variables. All of this works as expected.

But sometimes I get 'old' values when dragging new instances. For example, if I drag a new instance of Tileset into a layout, it will have one of the other layer's layouts by default, which I have to erase before I can draw new stuff on it. Similarly, I may drag a new trigger instance into a layout, and for whatever reason, its attributes default to a previous instance's attributes (even though I have one on the Master sheet).

SOMETIMES when I drag a tileset to a layout, it's blank as expected.

I'm really confused here. How does it decide what the 'default' state is?

Ok I got it working, thanks for the hint!

For anyone else having this issue.. it appears that you can 'filter' child references by adding them to the condition list for the code block. Everything works perfectly and now I know how to filter out objects. Wonderful!

Does your ship and tilemap have a solid behavior? Are you using an 8 direction movement behavior? Are you manually setting x/y coordinates?

Oh and this is what I mean by associating an instance before playing an animation.

Here's an example of what I'm talking about...

Notice it's referencing EmptyBox - 15. I cannot define a timeline unless it is specifically referencing an instance of an object type. If I were to delete this object typist he timeline would go blank and have no value (this is how I ran into the issue.. I deleted all instances of the empty box and my timeline change to showing nothing). I fixed it by having a dummy layout with the animation defined, but this seems weird and tacky.

For the instance variable thing, I tried it again and this time it worked, so I'm guessing it was a weird IDE bug.

Coming from engines such as Godot and unity, When I create an instance of an object, I'm expecting it to inherit properties of that object. But I'm noticing this is not the case in Construct 3 and I'd like to understand it better.

For example, if I create a timeline animation for an object, it's only valid for one specific object. I get 'around' this by creating a scratch scene, animate the object there, and then when I want to animate an actual instance I set the animation instance target first. This works, but seems like a tacky workaround.

Secondly, I wanted to create an instance level property for the contents of a chest, but it seems that if I create an instance variable, the value is shared by all object instances (not just the variable itself).

Thirdly, if I create a TileMap, the first instances values seem to be retained for all future versions on other scenes. I can change the contents and the data stays independent, but it's just... strange.

What am I missing here?