Stacks of custom chips 'absorb' custom tokens into the stack#71

A custom token, if dropped onto a stack of custom chips, will be ‘absorbed’ by the stack. Dropping the stack onto the token can also lead to this bug.

By using tryObjectEnterContainer(), it seems like the Custom Token is somehow transformed into the Custom Chip, since printing out the Custom Token’s name will actually print the name of the Custom Chip - this indicates that the Token is transformed into the Chip, and then tryObjectEnterContainer() is fired.

I have a similar bug. 2 Tokens (A and B)with Stackable true and Thickness 0.50. I made a Deck with 2 A-Tokens. If i put a B-Token over my Deck, the B-Token land on the first A-Token in the Deck. So the second A-Token and the B-Token have exactly the same position.

I have attached an example save file which easily reproduces this bug.