[jvriezen]

Originally Posted by Bob Steele

I would have to respectfully disagree with this line of reasoning. Other than the fact that it is redundant ("contiguously connected") a
contiguous assembly must mean that it is simply connected... the new answer does not say that it has to be contiguous OUTSIDE the frame perimeter. I quote directly from Q&A:

" To elaborate, an Appendage is a contiguous assembly that may extend beyond the Frame Perimeter per Rule [G21]."

I looked at the old wording "an appendage, when extended beyond the Frame Perimeter, is a contiguous assembly" and this simply doesn't make sense...you can't define a contiguous assembly as one that extends beyond the frame perimeter..you define it by the definition of contiguous (ie connected). They were simply cleaning up the answer.


If it looks like an appendage, quacks like an appendage and moves like an appendage...it is an appendage... contiguous means connected..connected could possibly mean moving all at once... but wouldn't have to ..


I think that Q and A is sufficiently clear on this topic. I also think it is unambiguous.

But how could you possibly EVER have two appendages exiting from the same edge then? If they can be connected inside the perimeter, then any thing you want to call two appendages on the same edge will be one by your definition --- unless one is totally disconnected from the bot, which of course violates a different rule. By your line of thinking, I can have any configuration whatsoever for appendage(s) as long as they all exit the perimeter along the same edge-- they are always connected to each other somehow via the bot parts.