Pikipedia:Pikmin Bloom update procedure

From Pikipedia, the Pikmin wiki
Revision as of 19:12, June 30, 2022 by Soprano (talk | contribs) (A few minor changes to reflect recent changes in the way things are done.)
Jump to navigation Jump to search

Documenting Pikmin Bloom on Pikipedia requires active maintenance, because its features often change due to updates, events, and other occurrences. This procedure explains what to do whenever there's an event, update, or some other change or announcement, in order to keep the wiki accurate.

When there's an update

Whenever there's a software update to the game:

  • Check the App Store page, Google Play page, and official update forum, and see what they say about the update.
  • Create a new row in the table in the update article, and copy the official update logs into that table, changing them in order to fit with the wiki's style (i.e. adding links, rewording to avoid using "you", etc.).
  • Install the update when you're sure that there isn't anything that needs testing before and after the update.
  • See if there are any changes which haven't been documented, and see if people on the internet have found any other undocumented changes. Document those when it's practical to.
  • Go to the articles about topics affected by the update. If the change was substantial enough to affect the content of the page, edit the page to reflect the current state of things, and add a row to the History section to explain what changed in the update. If documenting the changes requires further testing, place the {{update}} template in the relevant section so someone can do it later.

When there's a new weekly challenge

When a weekly challenge finishes and another one begins:

  • Go to the weekly challenge article and document the goal of the new challenge.
  • If the rewards given by the previous challenge are known, document them also.

When a Community Day is announced

When the next Community Day event is announced in the in-app news feed or elsewhere:

  • Read the details of the event.
  • Go to the event article. Use the {{community day}} template and fill out the parameters to ensure consistency in wording.
  • Upload a promotional image for the event and add it to the article, making sure that images alternate between left and right.

When another type of event is announced

When an event is announced that's not a Community Day:

  • Read the details of the event.
  • Document it on the event article in a way that's similar in style to the other events.
  • Upload a promotional image for the event and add it to the article, making sure that images alternate between left and right.

When an event starts

When an event has started in most timezones:

  • Reword the event's description in the event article to be in present tense.
  • If it's notable enough, add a news item about it in Template:News.
  • Go to the articles of any topic affected by the event, and edit them to reflect the temporary changes, adding a row in the History section.

When an event finishes

When an event is over in most timezones:

  • Reword the event's description in the event article to be in past tense.
  • If there were any unannounced features of the event, document those.
  • Go to the articles of any topic affected by the event, and edit them to reflect things returning to normal, adding a row in the History section.

When there's a new type of flower

When a new type of flower is added to the game:

  • Go to the Pikmin Bloom article and document the new flower type in the Flowers section.
  • Go to the nectar, petal, flower planting, and Big Flower articles and add the new flower type to the table, even if images of them haven't been uploaded yet.
  • When images of the new flower type are available, upload those using the file names that will cause them to appear in the other articles.
  • If the new type is one that was formerly in the files and unused, remove it from the Unused content in Pikmin Bloom article.

When flower availabilities change

Whenever the flowers available from Big Flowers or mushroom challenges change:

  • Go to the Big Flower article and describe what's changed in the table, making the wording similar to what's already there.
  • Go to the mushroom challenge article and document the new nectar rewards in table format, and move the old rewards to the History section in text format.

When a new type of Decor Pikmin is added

When new types or costumes of Decor Pikmin are made available:

  • Add them to the lists in the Decor Pikmin article, leaving broken image and icon links in the same style as the existing image and icon links. Add a row in the History section to show when they were added. If they're a special type requiring some explanation, add a section for them. Make sure to update the total number of types at the top of the article.
  • When images become available, upload them. The Decor type icons are from the game files, but cropped to 64x64 pixels and inverted.
  • If the new type is one that was formerly in the files and unused, remove it from the Unused content in Pikmin Bloom article.

When there's a change of items in the shop

Whenever the items in the shop change:

  • Go to the shop article and document the changes. Move any items that are no longer available to the formerly available items section, and document any new items. If it requires adding a note outside a table, that's fine.

When any other announcement happens

When there's any other official announcement about the game:

  • Go to the articles relevant to the announcement and change them as necessary, making sure to document changes in the History section if necessary.