Add message for glitched pet appearance
Seeing this right now with a lot of Invisibles, who have faces but we don't have the correct faceless ones in the db yet
This commit is contained in:
parent
a848533c7c
commit
0b16278703
2 changed files with 15 additions and 1 deletions
|
@ -3,6 +3,7 @@ import { Box, VStack } from "@chakra-ui/react";
|
|||
import { WarningTwoIcon } from "@chakra-ui/icons";
|
||||
import { FaBug } from "react-icons/fa";
|
||||
import { GlitchBadgeLayout, layerUsesHTML5 } from "../components/HTML5Badge";
|
||||
import { petAppearanceFragment } from "../components/useOutfitAppearance";
|
||||
|
||||
function OutfitKnownGlitchesBadge({ appearance }) {
|
||||
const glitchMessages = [];
|
||||
|
@ -105,6 +106,18 @@ function OutfitKnownGlitchesBadge({ appearance }) {
|
|||
}
|
||||
}
|
||||
|
||||
// Check whether the pet appearance is marked as Glitched.
|
||||
if (petAppearance?.isGlitched) {
|
||||
glitchMessages.push(
|
||||
<Box key={`pet-appearance-is-glitched`}>
|
||||
We know that the art for this pet is incorrect, but we still haven't
|
||||
seen a <em>correct</em> model for this pose yet. Once someone models the
|
||||
correct data, we'll use that instead. For now, you could also try
|
||||
switching to another pose, by clicking the emoji face to the right!
|
||||
</Box>
|
||||
);
|
||||
}
|
||||
|
||||
// Check whether the pet has OFFICIAL_SVG_IS_INCORRECT.
|
||||
const petLayers = petAppearance?.layers || [];
|
||||
for (const layer of petLayers) {
|
||||
|
|
|
@ -211,7 +211,7 @@ export const appearanceLayerFragment = gql`
|
|||
canvasMovieLibraryUrl
|
||||
imageUrl(size: SIZE_600)
|
||||
bodyId
|
||||
knownGlitches
|
||||
knownGlitches # For HTML5 & Known Glitches UI
|
||||
zone {
|
||||
id
|
||||
depth @client
|
||||
|
@ -268,6 +268,7 @@ export const petAppearanceFragment = gql`
|
|||
fragment PetAppearanceForOutfitPreview on PetAppearance {
|
||||
id
|
||||
bodyId
|
||||
isGlitched # For Known Glitches UI
|
||||
layers {
|
||||
id
|
||||
...AppearanceLayerForOutfitPreview
|
||||
|
|
Loading…
Reference in a new issue