All items submitted by Developers will be reviewed by our submissions staff to ensure compliance with content standards. A submission will not be approved if it fits into one of the following categories:
Inappropriate: The custom content is deemed inappropriate or offensive.
Copyrighted: The custom content contains copyrighted material.
Technical: Your material does not conform to technical requirements.
Specific content guidelines include:
- The female and male avatar bodies must wear clothing that conforms to Minimum Coverage Requirements.
- Female and male forms depicted on artwork must also comply with the Minimum Coverage Requirements.
- No sexually offensive or overly suggestive material.
- No material generally considered to be disgusting or offensive.
- No personal attacks.
- No inappropriate language.
- No depictions of blood and gore, particularly on clothing items and vehicles.
- No references to illegal narcotics, particularly marijuana.
- No objects that can be used to "grief" (harass) other members.
- Submitted material should not contain a brand name, a logo (including the There, Inc. logo), a celebrity name, a slogan or other copyrighted material.
To aid compliance with the Minimum Coverage Requirements, developers can download and install an application called Fig Leaf. This allows you to preview textures quickly with minimum coverage templates applied and verify whether or not they are compliant.
The technical reasons for rejecting an item are covered in the Painter and Builder Kit documentation. In general, submissions will be rejected if:
- Any of the submitted textures are smaller or larger than what is required by the product type.
- Any of the submitted textures are in the wrong file format (i.e. textures must be in the JPEG or PNG file format).
- Incomplete submission data (i.e. one or more missing textures).
- Any of the submitted textures are not correctly bound to the model they are submitted with.
- The submitted model's root node (a.k.a. dummy object) is not within the bounding box.
- The submitted model exceeds budget requirements (i.e. too many polygons) or is incomplete.
- The submitted model causes a predefined in-world behavior (i.e. animation) to stop working.
- The submitted model contains elements not permitted within the properties of the product type it was submitted as.
