When items collide with other items

Long story, but I found need to make item objects collide with each other. The solution I decided on (which is probably incorrect after what I've gone through) was to add ItemObjectType to sClientCollisionMask. Upon a clean recompile, I loaded up Torque with trace on. Strangely, and much to my horror, Torque crashed within seconds. Looking over console.log, I noticed something incredibly odd: The items were calling collisions against themselves! Console.log was filled with "entering Healthpatch::onCollision(16, 1734, 1734)" Right, so add %obj.setCollisionTimeout(%obj) to Healthpatch::onAdd. Again, a crash, same story. I went back to item.cc, and I guess I was sleep deprived, because I removed the following lines:

if(mCollisionObject)
	     mCollisionObject->disableCollision();

and

if(mCollisionObject)
	     mCollisionObject->enableCollision();

from Item::updateWorkingCollisionSet(). For whatever reason, this stopped the collisions and the crashes.

Fast forward three days. I'm still working on the issue that required colliding items. I encounter a new problem (now using a custom Rock item). Whenver a Rock item's z position was between 254.25 and 256.25, it would repeatedly call collisions against itself. I went back to item.cc, noticed that some lines had been removed from updateWorkingCollisionSet() and put them back in. The original error did not return, but the new one remains.

As near as I can tell, this is an error somewhere in the source code. The item calling updateWorkingList has had collisions disabled so it shouldn't be able to call collisions against itself. But... it does.

I see four possible solutions:
1) There is a different way to make items collide against each other and I never should have added ItemObjectType to the collision mask in the first place
2) I'm missing some piece to the puzzle and only made some of the necessary changes.
3) There is a bug somewhere in the source code, presumably at a low level.
4) Occam's Razor: If the item only calls collisiosn against itself at those z values, lower the terrain so it can't reach those z values.

Still, this whole situation leaves me incredibly confused, and somewhat sleepless. Especially how the source code change fixed the first glitch where items would continuously call collisions against themselves, but putting it back in didn't also recreate that peculiar glitch. Also at one point where I had both rocks and health patches in the same map, the health patches would have issues but not the rocks. Another thing that came up is sometimes Torque would alternate between crashing and booting me from the server (single player game) because of a bad packet update.

On the plus side, I've learned that if you're gonna go in over your head, you may as well try to do it with style.