Bulbapedia:Project Games/New game checklist
Please fill out this page. Generally: be specific. Include links to specific pages or templates.
Core games
There's generally a lot we can expect to appear in core series games, so we can predict a lot of things that need doing when a new game comes out.
Until a game officially releases, only so much can be reliably added to the wiki. (All of this applies only to officially revealed information! Do not add information from leaked data dumps.) New Pokémon or forms can be added; a page for the game, for the region, for named locations or characters. Types and Abilities of revealed Pokémon can be trusted. But some aspects of pre-release material should be taken with a little grain of salt. Big-picture reveals are generally safe, but smaller details like Pokémon seen in an area or moves seen used by a Pokémon are smaller details that could feasibly be different in the final release. (In short, be careful about what you "promise" will be in the game.)
Checklist
- Game
- A new page for the game(s) itself
- Add game to: Pokémon games, generation, the page for its generation (or create it if it's the first of its generation)
- (What else does this impact, like navboxes)
- Region
- A new page if it's a new region (otherwise update the existing page)
- New regional dex
- Create new page for regional dex (unless it's a remake, probably)
- Update Regional Pokédex
- (What else does this impact, like navboxes)
- New Pokémon
- ... (new pages, +NDex, lists of Pokémon...) (please feel free to flesh out details as individual bullet points)
- New forms...
- Player characters
- New items
- ...
- New Abilities
- ...
- New moves
- Create pages for new moves
- Example: tbd
- Update list pages:
- Move Tutor (new game's tutor moves/locations)
- Update TM/HM/TR?
- Stats
- Update any changed stats
- Species pages
- [list pages...]
- Learnsets
- Copy old learnsets to past-gen pages.
- Copy everything from the main page to a new past-gen page and add the
{{pokelinkback}}template. (It is not necessary to edit the section levels down, like changing====to==, primarily for the sake of keeping the task simple, but also because it's fairly trivial on a relatively small page.)- Example: when Generation VIII was coming out, Bulbasaur (Pokémon)#Learnset was copied to Bulbasaur (Pokémon)/Generation VII learnset, with
{{pokelinkback|001|Bulbasaur|7}}added at the top.
- Example: when Generation VIII was coming out, Bulbasaur (Pokémon)#Learnset was copied to Bulbasaur (Pokémon)/Generation VII learnset, with
- Copy everything from the main page to a new past-gen page and add the
- When new game's data is out:
- Replace old learnset with new learnset on species page
- Example: when Generation VIII came out (tbd)
- Replace learnsets of Pokémon not in the game with a null template (debatable)
- Example: tbd
- Add new learnset info into move pages
- Example: tbd
- Replace old learnset with new learnset on species page
- Locations
- ...
- Encounters
- Do not presume that Pokémon shown in trailers will be catchable in the final release.
- ...
- Trainers
- ...
- If there's a new Trainer class...
- Other characters
- ...
- Mechanics
- Create pages for new mechanics
- Predictable old mechanics:
- Templates
- (list templates that need to be updated and how (specific code))
- Walkthroughs
- Walkthroughs are most often created by regular users. See Bulbapedia:Project Walkthroughs for help.
- Check and update Bulbapedia:Project Walkthroughs/To-do list
Other games
Other games will be much more varied than core games, but we can probably think of a few things that will generally apply.
- TBD... (Game page, characters, ...?)
