Prepare a clear outfit screenshot for community review

A useful outfit screenshot lets another player judge the outfit without guessing which details belong to the character. Choose a view where the silhouette is easy to read and the important pieces are visible. A simple background and steady lighting usually communicate more than a dramatic scene that hides half the equipment.

Inspect the image before uploading it. Crop away unrelated desktop content, private messages, account information, or other details you do not want to publish. Use a screenshot you are entitled to share. If another player helped create the image or outfit, agree on attribution before sending the submission rather than trying to resolve it after publication.

The uploader accepts JPEG, PNG, and WebP images, with a maximum file size of 20 MiB per file. Choose a real image in one of those formats; changing a filename extension does not convert the underlying file. If an image is too large, export a smaller copy and check that the outfit remains readable. Keep your original separately.

Give the outfit a specific title and a helpful description. Explain the idea, identify deliberate substitutions, and mention any information you have not checked. Add the relevant game context and the character shown. Those fields describe your example; they should not be presented as a promise that every other character can use the same pieces.

Check the item list against your screenshot. Use exact item references where available, and avoid inserting a guessed item merely to make the list look complete. A concise, honest description is more useful than a confident acquisition claim that has not been verified. If a visual variant matters, say that it needs confirmation when you cannot identify it reliably.

Saving a draft and submitting for review are separate actions. Use a draft while you are still assembling the description and images. Upload processing must finish successfully before an image can be used in the submission. A successful upload does not publish an outfit, and a submitted outfit enters the review workflow rather than appearing in the public gallery immediately.

If a reviewer requests changes, read the feedback and correct the specific issue before submitting again. Keep a copy of your item list and description so you can review your own changes carefully. Avoid including personal contact details in a public description. The goal is a clear, attributable example that other players can understand, with uncertainties visible and the final public result checked before it goes live.