Possible to scope objects while testing modulo?

[elvisish]

I often use mod to test against counters to perform certain things at intervals, but it has to be done through "compare two general values", but is it possible to test mod on individual objects alterable values so each object can be scoped? I don't think it's possible in any way at present, so might it be considered as a feature request for some way of being able to do this?

[marbenx]

Might not be the most ideal way to do it, but you could have an "Always" event that calculates the modulus and puts it in that object's alterable values.

i.e. instead of using "IF (A + B) mod n == C" as a compare statement, you can do "IF object's alterable value == C" instead, which will scope the object correctly. I do this sometimes if I want to check an test against object's scale when there's multiple instances of it

[Volnaiskra]

Not sure if this helps, but while "compare two general values" doesn't scope anything for subsequent conditions/actions, it does inherit scoping from preceding conditions. What this means is that you can combine it with a forEach loop to isolate a particular instance based on its modulo:

[casleziro]

Why not always set an alterable value of an object to (Value + 1) mod interval? Then below the event that increments the value check if value = 0 to tell it has reached the interval.

example added.

[elvisish]

Might not be the most ideal way to do it, but you could have an "Always" event that calculates the modulus and puts it in that object's alterable values.

i.e. instead of using "IF (A + B) mod n == C" as a compare statement, you can do "IF object's alterable value == C" instead, which will scope the object correctly. I do this sometimes if I want to check an test against object's scale when there's multiple instances of it

Which part would go in "Always"? If I'm trying to scope a specific object (say an overlapping object or one within a certain distance of another) would this be a loop for each object and put it in every objects alt value?

Not sure if this helps, but while "compare two general values" doesn't scope anything for subsequent conditions/actions, it does inherit scoping from preceding conditions. What this means is that you can combine it with a forEach loop to isolate a particular instance based on its modulo:

That's really helpful to know, I'm not sure what kind of performance loss it would have looping through each, but it's interesting that scope can be found using "compare two", so if I had an Always adding +1 "clock" value on each of the object, and I wanted the object within a certain distance of the player to do something if it's "clock" was "mod 60 = 0" or something, I could just loop through all objects and test like that?

Why not always set an alterable value of an object to (Value + 1) mod interval? Then below the event that increments the value check if value = 0 to tell it has reached the interval.

example added.

I hadn't actually thought of separating the mod value and the check for 0 on two separate events, that's a good idea!

[marbenx]

Which part would go in "Always"? If I'm trying to scope a specific object (say an overlapping object or one within a certain distance of another) would this be a loop for each object and put it in every objects alt value?

Like this:


"Always" can be replaced with whatever other condition you wanted, like the overlap or distance check you mentioned above, and line 3 will only scope objects where Value A mod 3==0