- fixed : @attach:folderA=force,attachover:folderB=force,attach:folderA=force...
- fixed : @attach:folderA=force,attachover:folderB=force,attach:folderA=force results in undefined/undesirable behaviour? -> previously implementation would replace any "conflicting" wearable type from folderB that also exists in folderA -> if an item in folderA is fully worn then trying to "rewear" then it (probably) makes more sense that this should have no effect - fixed : @attach:folderA=force followed by another @attach:folderA=force will (re)wear the wearables contained in folderA even if they're already worn --HG-- branch : RLVa
Please register or sign in to comment