The problem; people want to be able to put more than one attachment on the same place! The proposal therefore is simple; instead of 1 attachment per attachment point, we have a hard limit of 31 attachments in total, which you can distribute any way you like. Be it 2 each across 15 attachment points with 1 to spare, or all 31 attachments on your left ear. It's up to you, perfect if you have prim-hands/gloves and want to carry a shield, staff or sword for example! This overall allows more flexibility, and allows for things such as furry avatars that can have both prim-hands/paws AND can hold objects, or to wear armour and have a separate tail (integrating one into armour is not nice as you lose the ability to rotate independently). There are probably benefits to humans too =) Thoughts on implementation: Unless things have changed since I last read about it, attachments are currently implemented as an array of object-keys, whereby each key points to an attachment, and the position in the array represents an attachment point (so the key in slot 1 may point to an attachment for your left ear, NULL_KEY in slot 7 may mean there is nothing on your right shoulder etc.). Easiest way to implement multiple attachments per-point would be with a variable length list of attachments which can go no larger than 31. Each entry in this list contains a key pointing to the attachment itself, and an integer value, which indicates the location on the avatar that this attachment should go. This is no more complex than an array of slots, and simply requires the client to iterate through the list attaching objects to the corresponding attachment point as they arrive. It also allows additional attachment points to be added more easily since it just requires a new constant and programming on the client-side, no changes to the data-structure. UI representation: For UI solutions to the problem of how to represent and manipulate multiple attachments per attachment point, please see the sub-tasks to this issue.