tehuster

I've just finished a sweet project. It's an interactive gaming table. It's a digital version of Halli Galli ( a card game ). Some pictures are available on 

http://www.thomashuster.com/#!projecten/c1t44

The entire game in run on 4 arduino's and max msp. I got a small problem tho.

I've got 4 numbers that are variables for the lives of each player ( 4 players ). And when 3 of those players are "0" the patch knows, there is a winner !! And the apropriate actions are made!

I'm using [ match 0 0 0 ] to check when 3 players have "0", However this does not work very well!!

Sometimes when there are only 2 players left it already gives the a bang after [ match 0 0 0 ] Does anyone know a better object for this?

thanks in advance! much love, sorry for the bad english!

I've just finished a sweet project. It's an interactive gaming table. It's a digital version of Halli Galli ( a card game ). Some pictures are available on http://www.thomashuster.com/#!projecten/c1t44 ( sorry it's not in english yet! ).

The entire game in run on 4 arduino's and max msp. I got a small problem tho. 

I've got 4 numbers that are variables for the lives of each player ( 4 players ). And when 3 of those players are "0" the patch knows, there is a winner !! And the apropriate actions are made! 

I'm using [ match 0 0 0 ] to check when 3 players have "0", However this does not work very well!!
Sometimes when there are only 2 players left it already gives the a bang after [ match 0 0 0 ]  Does anyone know a better object for this?

better-match-object

That was exactly what i was looking for! I used [join 4] to put in a message and voila. It works like a charm!

you need to reset [match] with every new input or it might match 3 zeros as a combination of new/previous input.

yes, that seemed to be the problem. but the solution Nicolas gave me works great too.

I couldn't see the solution posted by Nicolas! Is there a way to stop these problems from occurring? I'm building a sort-of alarm clock i.e 'match 0 0 0', representing hours, minutes and seconds. However, it is unreliable for a 24 hour clock as it will trigger the same bang at '23 0 0' as it would at '0 23 0'. There is a confusion between hours/minutes/seconds ordering, perhaps? Any thoughts!?

Better match object