#Some items are not in the right rarity areas in the skins menu

1 messages · Page 1 of 1 (latest)

tired vault
#

I have evidence of multiple being misplaced, I don't have all the skins so I can't confirm that all of them are where they should be, though, might be worth a look with an account that does. Making a few posts to organise it all

#

The Gumisshimar gun skin is up at the top of the menu even above the default, it should be in rares, the actual unit skin is fine.

The Gundam Miku skin is fine, can't confirm the rifle

I don't have the Zaku Miku skin, but I have enough locked Zaku skins to confirm the actual unit skin is fine (unless everything there is wrong, but I doubt it)

Don't have either the Teto skin or Teto weapon, can't confirm that

Rintank is down in the Normals as a rare

Kagamines Gun is up at the top above the default, should also be in rares. Unrelated to this update, but the Gatheroad GM skin is in the normal area when it should be in Rares. The locked skins are misordered, so at least one of either Cheap Imitation or Kagamine GM is probably in the wrong place, can't confirm which one, though

#

I don't have the Exatio Unit, so can't confirm that, but the EXATIO weapon is fine

The Yellow One unit is fine, so is the Leek

Megurine NUka unit is fine, the Megurine NUka weapon is lower than it should be

MEIKO-Arms Unit is fine, I don't have the weapon to confirm that the gun is fine, though

#

also, in the stamps, the GM flexing arm is in the middle of the Hatsuneverse stamps?

#

Ornaments wise, the Miku stuff is at th ebottom with the side 7 stuff, that feels more like a limitation on how you can add to that particular list, though

#

please, if anyone has any of the skins I couldn't confirm, can you check their positions and post those in here too?

viral eagle
#

i counted mine, i had 6 nu's and 4 assh's, everything else seemed fine

tired vault
#

It's the order in the menu which is the issue

wanton yacht
#

Thanks for confirming! We need to spend a bit of time re-organizing this on our end. Our backend tooling was broken on this for a bit which has slowed things down. We'll try to squeeze it in soon!