Thread:WKPQ/@comment-34918040-20190509011925/@comment-34918040-20190509023830


 * "The comments can still be found."

Glad to hear that.


 * "If we move the pages back, would the comments posted after the renaming be merged or made hidden? Would the currently hidden ones be made visible again or remain hidden?"

Good question.
 * First: I think you didn't check the box Rename subpages of talk page (up to 100) when renaming the pages. This would have moved all comments together with the page. I made this mistake once, but was able to revert it before people commented under the new page. Renaming it back let the previous comments reappear under the old page.
 * Now that we have two comment sections for some pages: Comments aren't part of the page. The page is in the main namespace, the comments are in the Talk: namespace. That's why we can tag comments separately with new data, see Category:Data contributions for an example. All entries have the Talk: prefix, followed by the page name.
 * The comments of the two update page versions now are at two different places:
 * Talk:2019 Spring Update/[...] and
 * Talk:Asphalt 8: Airborne/2019 Spring Update/[...]
 * We could try to rename Asphalt 8: Airborne/2019 Spring Update back to 2019 Spring Update, but this time check Rename subpages of talk page (up to 100). As the old talk page is linked to the old page, the old comments should reappear. I'm not sure if the new comments are simply merged with the old ones, but technically, they are simply renamed from Talk:NewPath/@comment to Talk:OldPath/@comment. As they all have different timestamps, the new comments shouldn't collide with the old comments, but simply be sorted with them. This would be the easiest solution, but I don't now if it works 100 %.
 * If the new comments don't appear under the old page with this method, we would have to rename the new comments manually. (That's rubbish when I think about it, because that's what the ''Rename subpages" checkbox already does.)


 * "I'm open to reverting the naming but would we need a format if said overlap occurs?"

I already thought that this was the reason. The solution is simple: Add the disambiguation in parentheses. Example: Fancy Update already is an Asphalt 8 update. Then Asphalt 9 gets an update with the same name. That's how most wikis, including Wikipedia, do it and I found it very clear and easy to handle. That's also what I did with pages like Champion Kit Box which always contains the current version and Champion Kit Box (pre 4.2.0) that contains a hatnote to inform the user that this is an old version, with a link to the current version. Thus, all Champion Kit Box pages are sorted under C, links always point to the current version and all previous versions can easily be distinguished.
 * Rename Fancy Update to Fancy Update (Asphalt 8), including the talk subpages.
 * Create Fancy Update (Asphalt 9).
 * Turn the old redirect page Fancy Update into a disambiguation page saying "Fancy Update is used for two different updates: [...]".


 * "As for the Championship/R&D/EDD/Special Event, how would we rename those [...]"

Equus Bass 770 Championship instead of Championship/Equus Bass 770. This moves the vehicle name to the beginning and makes searching and browsing through categories easy.


 * "[...] and how do we ensure the comments aren't left behind?"

Checking the Rename subpages box will move all comments.