Same here

Well, still a Construct noob myself, but are you sure that this isn't the typical tile problem which is the reason tiles are often set up with "smeared pixels" around the actually used pixels so the GPU doesn't render blank space if resizing the tiles?

In GameMaker this is a common problem even documented on the official YoYo page:

(Sorry for a link to the "competition".. but the article seems to be fitting here..)

https://docs.yoyogames.com/source/dadio ... tiles.html

I think I've read somewhere that construct takes care for this problem itself.. but who nows.....

Wow, thank you.. I've seen these "Pick" methods, but couldn't wrap my head around their implementation... Your example is perfect! Thanks!

Only problem which remains is the order of actions which are to take.. As I said, I've some actions which are only fitting for some of the family members, I can pick them by UID in a subevent now (thanks to you), but the actions for the family itself are already done at this point.. which is unfortunate in my case. Let's say the last action of the family "EnemyFamily1" is "Destroy", then in the subevent the picked "Enemy1" will never see an action.

There is no way to "get back" to the family after drilling it down to the family member in the subevent via the Pick method, or is it? There's "Pick all" method but I think that means something different.

And starting another event.. well, as I said, I want the whole collision handling with the bullet in one event, seems the best solution to me...

EDIT: Okay, MAYBE I've found the solution myself.. I first write all the actions for the family which can be done at the start in die beginning, THEN create a subevent and pick the right family member, perform the actions regardings the family member, THEN create another subevent and Pick the Family via UID again and perform the rest of the actions regarding the family...

At least that's a solution which worked for me.

Hello,

I have a problem with a - seemingly - simple problem.

Let's say a bullet hits an enemy. All enemies are in a family because there are always the usual actions (like destroying the bullet and the enemy etc.)

But some enemies are different, they have a different behaviour or an effect which has to be disabled while "dying" and so on..

Let's say there is EnemyFamily1, and Enemy1 has a "Sine" behaviour (and the family has not), Enemy2 another behaviour..

The condition (on collision with EnemyFamily1) won't allow me to set specific behaviour for Enemy1 (every action regarding Enemy1 will change ALL instances of Enemy1.. and not only

the instance which was part of the collision...

What is the solution for this problem without checking for the same collision for every different enemy type? I mean, families are meant to avoid redundant code right? But how to

achieve this if I cannot "break down" the object types in the collision handling with the family?