How to know what pin triggered an interrupt?

[sheepdog]

Interesting, it would be fine if I was scanning from MSB to LSB, it is not the case.
Pin0 is the head
...
Pin4 is the right arm
Default porta is %xx111111
If Pin0 is activated we will have %xx111110
Reversed it will be %xx000001

It will tell me it is pin0, okay. What if there are two activated pins, example, reversed it would be %xx001001, it will tell me the activated pin is pin 3, which is true but as I have to scan starting from pin0, I will think the left arm was hit and use that info while the head was hit too, which is much worst (lethal) and the player will get some damage while a hit in the head would tag him out. See?

Yes I see, be fine if head pin3, glad you have it all sorted out anyway

[xnihilo]

Uh, seems that things are not so easy...

This time I guess it is a hardware concern.

I put a pin (c2) high somewhere before the routine that reads the incoming signal and put it low after, just to have a visual estimation of the time it takes to complete the routine.
The pin is just a test pin that lights a 5V led.
If I don't connect the led to the pin, then the signal is invalid but if I connect the led, all incoming signals are good...
C2 is an output pin, default low (no external WPU or WPD resistor).
If I connect the pin to GND through a 10K resistor, it is better but sometimes the signal is missed. Connecting the led ensures the signal is collected fine...

It makes no sense.

1 hour later:

I noticed I left from previous test C0 as input, default high but not using an external WPU.
I changed it back to output, default low.
Still I would miss some signals.
Then adding a 10K WPD instead of a led on the OUTPUT pin C2 seems to fix the problem.
I wonder how a WPD on an OUTPUT pin acts on my code ???