Help:Checklist/Update

When a promotion, event, and/or general new content is released, editors need to do many of the following:

What to Do

General

1. Locate any official posts on the wiki and/or forums. If neither are available, look around SEGA or Steam news feeds. Sometimes new things just don't have announcements. Links to these posts are used quite a lot around the wiki.
2. Update the appropriate News or News subpage with content. (Example)
3. Add data to Template:DoRSource if appropriate.

Prize Box

• These are specific items that should not be confused with Lockbox etc.

1. Update the Prize Box page - either the box is new, so it needs a new entry, or the box is re-released, so only the "Most Recent Year" needs changing.
2. If the box is new, create a page for the box. "New" is any box that has a unique name, and this includes even small things such as a specified year. If appropriate, make a disambig page. (Example)
3. If the box is re-released, update the calendar section of that box's page. Make sure to adjust the page's contents if odds have been changed and so on.
4. If the box has a weird name, add it to the switch in Template:PrizeBox/unusualnames.
5. Make sure all links on the Prize Box page are working. Editors might need to make redirects and/or new pages depending on what's in the box.

Model

1. If the model is new, make a page for the new model. (Example for singular) (Example for variants)
2. Redirect variants to the model page if there are variants, and make sure each redirect page registers for all relevant categories. (Example)
3. Certain items will require many associated page and subpage updates, such as alchemy tree creation/updating, acquisition, Reskin list if relevant, and so on.
4. New Battle Sprite reskins are the exception to many of these rules because their upper-level variations are unique to their entity type. Make a new page for the sprite, and make sure the original sprite page has its reskin list updated (Example), along with the list of sprites on the main Battle Sprite page, the Sprite Pod page, and the Reskin page.
5. If the item is a recolor, update either Template:CostumeTable/Recolors or Template:AccessoryTable/Recolors.

Color Pattern

1. Determine its color codes and add them to Template:ColorPattern/Box.
2. Add content to Color Pattern.
3. Create a category for the Color Pattern. (Example)
4. Redirect the short-hand name of the Color Pattern to the category page. (Example)

Event

1. Check the event's page, such as Winterfest, and update the calendar section.
2. Update content if needed to best reflect farming and gameplay strategies.
3. Check any involved pages, such as mission or material pages, to see if they need updating regarding any event changes.

Uploading Files

• For more details about file formats, see the Style Guide. Some are animations, others are specific crops of a screenshot and so on.
• Quick tip to remember: News, Icons, Tooltips, Inspect, Overworld (not every new thing uses all of these)

1. Check the Upload Log in case the wiki is having cache issues before going crazy with work - someone might have already done the uploads. Alternatively, edit and save a page the file is supposed to show up in without making any edit changes. If it's been uploaded and the page calls the file appropriately, then the task is done.
2. Make sure there are no typos in file names. Excruciatingly painful fixes will need to happen if typos propagate through file uploads.
3. Upload icons with appropriate category organizing tags.
4. Upload tooltip visuals of the items captured in-game. Accessory images register categories, costume images do not (for category organization, this is abnormal wiki behavior but our users like the system). Make sure the object is at a consistent angle with other similar objects. Make sure files are captured with high graphics and without interference from lag and so on.
5. Battle Sprite images usually take quite a long time to get, because editors can only upload visuals from in-game and players have to level the sprite before ultimate variations can be visualized.
6. For any file, try to source it. While it is not appropriate to mention individual players in the mainspace, crediting the file to a person - after making sure they are okay with it - helps bring the community together and encourages players to help editors with the wiki, even if it only takes a moment of their time. (Example)
7. Upload a file that goes with the news post if available. (Example)
8. Upload a "big" version of the file if available. Redirect to the oldest "big" image if the image is a duplicate of a previous news post. (Example)

Notes

Be sure to follow page format. There are a few important differences between different kinds of items and this is reflected by page content regarding wording, linking, and templates.

Copy+pasting reduces errors, but make sure the right page is copy+pasted from.