I'm writing this, but I've already fixed it and pushed this to the Android branch.
When a ring gets magnetized, on contact with a character it is destroyed and the character's ring count increments. So far, so good, right?
The object objRingMagnetized is programmed to create an instance of objRingDropped on delete. This is used to handle the cases when the player character loses the lightning shield, and the magnetized rings drop. However, this instantiation is also triggered when a ring is destroyed because a player picks it up, resulting in the player getting two rings instead of one.
I'm writing this, but I've already fixed it and pushed this to the Android branch.
When a ring gets magnetized, on contact with a character it is destroyed and the character's ring count increments. So far, so good, right?
The object objRingMagnetized is programmed to create an instance of objRingDropped on delete. This is used to handle the cases when the player character loses the lightning shield, and the magnetized rings drop. However, this instantiation is also triggered when a ring is destroyed because a player picks it up, resulting in the player getting two rings instead of one.
So, yeah, fixed :) .