Difference between revisions of "Nookipedia talk:The Roost"
PanchamBro (talk | contribs) (→Create villager/special character ID redirects: new section) |
|||
| Line 663: | Line 663: | ||
There are certain articles that will need to have a notice due to this (e.g. [[Doc]] already exists as a villager so a notice would need to be added to redirect people to [[Wilbur]] in the event that someone wanted to search his codename). -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 10:00, March 14, 2022 (EDT) | There are certain articles that will need to have a notice due to this (e.g. [[Doc]] already exists as a villager so a notice would need to be added to redirect people to [[Wilbur]] in the event that someone wanted to search his codename). -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 10:00, March 14, 2022 (EDT) | ||
| + | :{{Support}} It makes sense to have them. It makes things easier. --[[User:Dr. Peach|Dr. Peach]] ([[User talk:Dr. Peach|talk]]) 12:01, March 14, 2022 (EDT) | ||
Revision as of 12:01, March 14, 2022
Welcome to The Roost, a hub for editing help and community discussion. New topics go at the bottom of the page.
| |||||||||||
Tasks
Specific tasks
Expand content
Work on images
More tasks
Join an ongoing project
| |||||||||||
Need help?
|
Example topic
Post new topics below! Drago (talk) 
11:03, January 1, 2019 (EST)
Split {{Availability}} into separate availability templates
I know this won't be popular considering a lot of pages use Template:Availability, but at this point, I feel like there's too much to add that it's becoming a growing nightmare to deal with, especially with how limited MediaWiki can handle a template like this anymore.
I think long-term goal we should split this template into multiple sections. There are two options to consider.
- We split the template by their category. This means that Plants go to a specific category, and NPCs go in another. The Fortune Cookies from Animal Crossing: Pocket Camp therefore have their own separate template.
- We split the template into their own game. This is a big deal because this could mean linking specific items such as flower items by using Template:I. Long-term, when we do include items from other games like Animal Crossing: New Leaf, Animal Crossing: Pocket Camp, and Animal Crossing: Wild World, we don't have items that have to linked to one page in order to maintain consistency. We can have
{{Availability|NH|Orange Tree}}for Animal Crossing: New Horizons redirect to{{I|Orange Tree|New Horizons}}and in Animal Crossing: New Leaf,{{Availability|NL|Orange Tree}}goes to{{I|Orange Tree|New Leaf}}. This can also factor in specific icons for specific games, depending on if those icons exists. Now things that are common across multiple games, such as{{Availability|Starting item}}and{{Availability|Unobtainable}}, we can opt to keep those in the main template as they are not really game-specific in that regard.
This needs to be addressed, because the more we add to this template, the harder it gets to add new availability factors and the more likely that the template will cease to operate due to how many items need to be added (e.g. Pocket Camp fortune cookies). -- PanchamBro (talk • contributions) 13:21, June 6, 2021 (EDT)
- I'm quite onto this, having separate templates could simplify things quite a bit, but it will probably be a long process getting everything back together since we have so many pages with the availability template. ~ Vivian (talk)
13:28, June 6, 2021 (EDT)
- I would like to point out that we have bots that we can rely on to replace those texts. And that most templates can easily swap stuff around and add those specific names (see Template:CargoDisplayNHFurniture). -- PanchamBro (talk • contributions) 13:36, June 6, 2021 (EDT)
- The switch parser function help page over on wikipedia says that while a function can technically contain between 1k-2k branches, it "should be split to have less than 100 branches, in multiple or nested parts". If we expect that we will ever reach the upper limit/run into performance concerns, then splitting it would be easier to do sooner rather than later. Also, I didn't see this post before I made edits to the template to simplify it. Even though it's more readable/editable now, I agree that splitting it is still something we should consider. If we didn't want to adjust the template call on all of the pages in which {{Availability}} appears, we could create a template that determines which 'category' the call fits into (e.g. is it a plant, fortune cookie etc.). We could then use this determination to split the huge switch into several nested switches:
{{AvailabilityCategory|{{{1|}}}}}
{{#switch: {{#var:category}}
| fortune = {{#switch: {{{1|}}}
| Clothing Fortune Cookie
| Timmy's Fortune Cookie
.
.
.
- The
{{AvailabilityCategory}}template would determine what category the input belongs to, and this information could be accessed by calling the variable{{#var:category}}. This would still result in the template being very long though, as all of the different options would exist in the same template, just nested in multiple switch functions to improve performance.
(talk) 20:33, June 27, 2021 (EDT) - Minor suggestion if this would be implemented in the future, subpages could be used to separate between games e.g., {{Availability/NH}} and {{Availability/PC}}, to prevent
{{{#switch}}}ing hell. Regardless, the template definitely has to be split in the future.
Decomposer 10:59, August 11, 2021 (EDT)
SVGs, indexing, and gadgets
Hello editors! Thanks to the hard work of Jake, we've recently upgraded our MediaWiki version and made some small changes and improvements.
- You can now upload SVGs - huzzah!
- Userpages and all talk pages have been noindexed, meaning they will no longer appear in search results (Google, Bing, etc.). This was done to help protect user privacy, and to keep discussions, draft, and fan content out of public search results. If you'd like your userpage to appear in search results again, just add
__INDEX__to the top of it. - While we've had these for a while, they've never been formally announced: if you go into your Preferences -> Gadgets, there are some nifty tools here that can enhance your browsing and editing experience, like a scroll-to-top button, talk page discussion counter, syntax highlighter, and more.
Cheers, ~SuperHamster Talk Contribs 22:24, June 15, 2021 (EDT)
The index category is a redlink, should someone create it? Petaldancer66😺 Petaldancer66 talk 00:15, June 27, 2021 (EDT)
Question.
Bunny currently redirects to Rabbit, a Villager's name is also Bunnie. Some people might not know know Bunnie's name is spelled B-U-N-N-I-E. Should we put a Wrong page template on Rabbit or make a redirect page? Petaldancer66😺 Petaldancer66 talk 15:43, July 7, 2021 (EDT)
- I'd go with the wrongpage template. Drago (talk)
11:34, July 8, 2021 (EDT) - I agree, seems like a perfect use for the wrongpage template. --Jake (talk) 13:42, July 8, 2021 (EDT)
Okay, did that. Thanks for the feedback! Petaldancer66😺 Petaldancer66 talk 15:03, July 8, 2021 (EDT)
Page about sleep
I think we need a page on this wiki about sleep, we could talk about all the messages left on doors while villagers are asleep, what hours they fall asleep and wake up at on each day, etc. Anyone got any thoughts on this? Meganium39 (talk) 05:58, July 22, 2021 (EDT)
- I think this is an interesting idea, I just don't know if there is enough information for its own page. If you'd like to mockup the page in a sandbox to get an idea of how much info there is that would be helpful. And then if it looks good we can move it to the main article space. At the very least though, sleep schedules deserve mention in the personality section on the villager page. I think they are only mentioned on the individual personality pages right now. (talk) 13:12, July 23, 2021 (EDT)
Doubutsu no Mori e+ Monthly Fishes: New pages or extra sections on Animal Crossing pages?
Hi. I was asked to post this question here because I added sections for Doubutsu no Mori e+ on [[1]] and subsequent articles up to May atm, and while I didn't think much about them, I should have probably asked others beforehand. Here's the issue, resumed:
- Doubutsu no Mori e+ was missing all pages for monthly fishes, so I, instead of making new pages per month for the 8 new fishes added to this game, decided to include those in a section of the Animal Crossing monthly fishes pages.
- While I did it to prevent copying all Animal Crossing's monthly pages only to add those 8 fishes, or for making a really short page, it hadn't occurred to me that such change could be questionable, as both games are seen as quite different, but in reality Doubutsu no Mori e+ hadn't expanded much on the fishes, bugs, and fossils areas.
Given that the changes I tried to do weren't as small as I thought, I came here to ask everyone interested for a better solution to this. By either undoing the changes and placing that list on its own page, changing the title to reflect the actual change inside of the article, or by doing something someone else thinks that's better. - unsigned comment from SEISHI★ (talk • contribs)
- I
Oppose. I'd prefer to make a list Like this. Petaldancer66😺 Petaldancer66 talk 19:09, July 22, 2021 (EDT)
- First off, I just want to say that I appreciate you taking the initiative work with cargo and generate these tables for us. You've done a great job so far. That said, while I agree that it does seem a little silly to generate a very similar table for e+ on its own page, we've established a naming system where each game gets its own yearly and monthly lists, regardless of how similar those lists may end up being. (Doubutsu no Mori+ doesn't get its own list because it is the Japanese version of Animal Crossing, even though there are significant localization differences between them.) So, in summary, for consistency I think it would be better to have the full e+ list on its own page. (talk) 13:23, July 23, 2021 (EDT)
- I see, I probably should have done that from the very beginning instead of deciding on my own to simplify everything (even if it was mostly copying and pasting code). Unless I see someone else has fixed what I've done in the time I wasn't around, I'll start undoing my changes and creating the respectives pages for each month in e+. Thank you very much to the both of you and sorry for cluttering those pages up, lol -- SEISHI★ (talk • contributions) 09:28, July 24, 2021 (EDT)
So I had an idea to create a new navbox for 🎬 Gekijōban Doubutsu no Mori, and this is what I've developed so far:
| Gekijōban Doubutsu no Mori | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Let me know what are your thoughts on the new navbox and whether or not it's necessary. -- PanchamBro (talk • contributions) 05:47, July 25, 2021 (EDT)
- Looks good! I think we could also add a section for locations. ~ AlexBot2004 (Talk) 16:37, July 25, 2021 (EDT)
- Again, looks good. We gonna have to create redlink pages at some ponit tho. Petaldancer66😺 Petaldancer66 talk 23:01, August 3, 2021 (EDT)
Images
The Tie dye shirt CF page got deleted so I think the images should be deleted too. The Files are File:Green tie-dye.jpg, File:Orange tie-dye.jpg, File:Purple tie-dye.jpg, File:Red tie-dye.jpg, and File:Blue tie-dye.jpg. If there are any more just tell me here. Petaldancer66😺 Petaldancer66 talk 17:10, July 27, 2021 (EDT)
- Oppose. The images could always be used for a list of clothing in City Folk when we get to that. ~ Vivian (talk) 17:21, July 27, 2021 (EDT)
Ya probably could. Petaldancer66😺 Petaldancer66 talk 22:52, July 28, 2021 (EDT)
- I disagree with Vivian. While we haven't gotten to Animal Crossing: City Folk items yet, we have to recognize that eventually they'll be replaced by transparent images provided by Phil and Alex whenever they get to images for City Folk items. We can keep the images for now, but they will be deleted upon replacement. -- PanchamBro (talk • contributions) 23:45, July 28, 2021 (EDT)
Individual item pages for stationery
I would like to suggest individual item pages for specific stationeries. Particularly because until Animal Crossing: New Horizons, they are items that the player can collect, and the Stationery page is not enough to document the specifics in general. I would say it would be perfectly suitable for games before New Horizons, but for New Horizons stationeries, I would like to know whether or not those stationeries deserve their own page. -- PanchamBro (talk • contributions) 17:34, August 2, 2021 (EDT)
- I agree that for games prior to New Horizons, all stationery deserve their own item pages. I would argue that since stationery is no longer an obtainable item (and does not appear in the item catalog) in NH it doesn't make sense to put NH stationery into the Item namespace. (talk) 22:29, August 5, 2021 (EDT)
- I see the point, though I do think we could find a way to include other translations for various stationeries in Animal Crossing: New Horizons. Would there be any tangible way to include translations for each stationary in New Horizons? -- PanchamBro (talk • contributions) 22:47, August 5, 2021 (EDT)
- You know, thinking about it again I think I've changed my mind lol. There are stationery items in previous games that are unobtainable (although they sometimes appear in the catalog), so existing as an inventory item or place-able object is kind of an arbitrary rule to decide on whether or not something is an item. Plus, there is a mailbox 'inventory' of sorts that can store letters in New Horizons. Using the existing infobox templates on designated item pages would also be easier/more consistent. So I think I'm on board with the idea. I'm still curious what other editors think though. (talk) 23:24, August 5, 2021 (EDT)
- You know, thinking about it again I think I've changed my mind lol. There are stationery items in previous games that are unobtainable (although they sometimes appear in the catalog), so existing as an inventory item or place-able object is kind of an arbitrary rule to decide on whether or not something is an item. Plus, there is a mailbox 'inventory' of sorts that can store letters in New Horizons. Using the existing infobox templates on designated item pages would also be easier/more consistent. So I think I'm on board with the idea. I'm still curious what other editors think though.
- I see the point, though I do think we could find a way to include other translations for various stationeries in Animal Crossing: New Horizons. Would there be any tangible way to include translations for each stationary in New Horizons? -- PanchamBro (talk • contributions) 22:47, August 5, 2021 (EDT)
Link template refactor
Hello everyone, I wanted to get your thoughts on re-coding our link templates. Right now they use a lot of nested switches and are a bit dense/difficult to edit. But more than just replicating the original functionality, I also wanted to take this opportunity to improve them and wanted to get your input on this.
Proposed changes:
- Shortening the
nolinkparameter tonl. - Removing the
shorterparameter altogether and just having the long name (Animal Crossing: New Horizons), the short name (New Horizons), and the abbreviation (NH). - Changing the default behavior to produce the short name (New Horizons) instead of the full name (Animal Crossing: New Horizons).
- Adding the parameter
fullto produce the full name (Animal Crossing: New Horizons).
- Adding the parameter
- Changing the
shortestparameter (e.g. NH) toab(short for 'abbreviation') oracro(short for 'acronym').
These link templates are the most used templates on the site. The {{NH}} template alone is used on over 30,000 pages, so this is something that would affect nearly every page of the wiki (as at least one of these templates is probably found there). Would love to hear your thoughts on the proposed changes, and also on implementation. Do you even think it's worth it to change these templates? All feedback is welcome. (talk) 23:17, August 5, 2021 (EDT)
- I don't see a reason why "ACNH" could be used for an article link, so I
Support removing it. As for the template changes, I think I have a weak Support given how massive these templates are being used and the massive work that will need to be done to change all of those parameters. But I'm not opposed, I think the replacements may work out well. -- PanchamBro (talk • contributions) 01:43, August 10, 2021 (EDT)
Addressing problematic issues with the Nook Shopping seasonal event page
This is not something that can be easily swayed for given the circumstances at hand here, but I think we may as well address the current uprising.
As of now, Nintendo is leaning focus to perpetuate a cycle of Nook Shopping seasonal events while they wiggle it out with adding new content. Looking at these "events" closely, the only major factor is that these events just has the player purchase them via Nook Shopping and have it straight delivered from there.
However, having it be logged in a single page present some problems. Firstly, although they are significantly minor events that are way less interactive than the previous events at hand, they are still events. They still count as an event internally through the game's code. Secondly, each event name has its own set of translations that cannot simply be fit on a page that is already becoming too big. There's also the added bonus of not being able to use interlanguage links to our German affiliate for these specific events, but they do have a unified page, so it isn't a problem.
What is a problem though, is that as Nintendo continues to grow the list of items, it's starting to grow more unbearable to add these new events and items to the table. And all that mess results in a table that is why less mobile friendly than it is. The table looks good on desktop, but looks outright intimidating on mobile. There are ways to make the table not stick out as a sore thumb, but because all that information needs to be scrolled horizontally, there is the potential for readers to not see a complete information.
At this point, there are three ways to approach this issue:
- Create pages for Nook Shopping event. Now this won't eliminate the Nook Shopping event page in general, but it will help downsize the page's main table significantly since we want to assure that our mobile readers can read their info better by not forcing them to scroll horizontally. Individual pages also have the opportunity to add in missing translations that we have not added yet. This present a problem however, since there is very little to say about these events other than a small pace of words.
- Downsize the table into a few columns, and just have event names, date, or description. It's not ideal, certainly there are merits to have info about this events, but it is something to help improve readability on this page.
- Transform the table into an article-based structure where each event gets a date and the list of items. This would mean that we'd have a longer page to scroll through, but it is certainly better than having a table that readers will need to horizontally scroll though to see the other portions of information.
These are just a few ways to go through this issue, but I'd like to know what are your thoughts on the option and if there are any ways to address this problem. -- PanchamBro (talk • contributions) 04:19, August 10, 2021 (EDT)
- I think we should treat them as standard events and give them their own pages. Even though they only offer an item and some info about the event itself, at the end of the day that's all the minor events in previous games were (going to Isabelle/Tortimer and getting an item and some event-exclusive dialog). ~ AlexBot2004 (Talk) 17:14, August 10, 2021 (EDT)
- I agree with Alexbot2004 that each event should have its own page. That will solve the translation issue and will open up the opportunity to cargo store event info (if we aren't doing that already). As for the table issue, I think it would be great if we could develop some way to have tables display less columns on screens with less space. If that's not feasible, I think moving the description to each event's individual article page will go a long way to reduce horizontal scrolling. You could also condense columns into the same cell (for example, place the date below the event name on a new line instead of in a separate column) to help with this as well since the table isn't sortable. (talk) 22:15, August 10, 2021 (EDT)
Where to link Wild World items to?
Hi, I've recently been trying to edit some Wild World item lists to include their textures in pages like this: https://nookipedia.com/wiki/Wallpaper/Wild_World I wanted to link the items to their individual pages, for example, the Ancient Wall to Item:Ancient Wall, but I found the only related item pages are for Animal Crossing (the first one) and for New Horizons. So my question is, is it fine for me to link the Wild World list to the Animal Crossing Item pages? And if it is, should they be edited to add the Wild World textures? Sorry if it has been discussed elsewhere, I didn't quite know where to ask this. --Roli300 (talk) 08:33, September 3, 2021 (EDT)
- Our item pages are specific to one species of game, due to the fact that each game has its own set of data for each item. Though we haven't developed any Wild World item pages yet, you can help create those pages on this wiki. The Spreadsheet for Wild World is over here if you need to reference on making those pages. -- PanchamBro (talk • contributions) 09:05, September 3, 2021 (EDT)
- Oh, I see, thanks a lot for the quick response. I'll try to slowly create some Wild World pages, then. Should I use the same template as the one in the Animal Crossing pages or is there some other template I should follow? --Roli300 (talk) 09:15, September 3, 2021 (EDT)
- They would have to use their own template, although we have not created one yet for Wild World walls/carpets. Just to let you know though, the item pages can be created automatically by a script to save time, since there are hundreds of items in the game; this is how we created the GameCube and New Horizons pages. ~ AlexBot2004 (Talk) 10:18, September 3, 2021 (EDT)
- Oh, I see, thanks a lot for the quick response. I'll try to slowly create some Wild World pages, then. Should I use the same template as the one in the Animal Crossing pages or is there some other template I should follow? --Roli300 (talk) 09:15, September 3, 2021 (EDT)
- I just wanted to provide a bit more context for you in regard to your question. The wiki is moving towards a database-generated model for our item tables, meaning that we use a tool called Cargo to generate databases of items, and then we pull certain groupings of items (example:clothing, wallpaper etc.) from that database for display in tables. This way, we don't have to manually enter data cell by cell as is currently being done at Wallpaper/Wild World. In order to fill our cargo database, we create individual item pages, which have a special code in them that tells cargo to store whatever data fields we specify. So, you're more than welcome to work on a page like Wallpaper/Wild World, but once the individual item pages are all created, the content at Wallpaper/Wild World will be replaced using a Cargo-generated table. Essentially your work on pages like this will eventually be 'erased'.
- The workflow we are currently using is something like this:
- Extract data from the relevant Animal Crossing game (item data & images/model renders)
- Compile that data in a spreadsheet, broken down by item category
- Create the appropriate cargo & infobox templates for each item type
- Create a script to automatically generate pages for each item using the appropriate template(s)
- Once the relevant item pages have been created, create pages for lists of items, populated using cargo queries
- I'm not certain which stage we're at in this process for Wild World items, but we do have a channel on Discord if you're interested in getting involved. (talk) 17:30, September 3, 2021 (EDT)
More hourly type pages for people who like playing at their local times
One of the main things that i wanted to add to this wiki was to add two more pages to it.One of them would be about hourly changes to the game, for example, for the 7 A.M. section of it, there could something saying stuff like, Animal Crossing -Nook n go opens- or for the 8 P.M. section of it, Animal Crossing City Folk -K.K. Starts playing songs- which is something I've wanted on this wiki for a long time. Another page idea is for hourly songs in all of the games as well as their rain and snow versions as well as their cherry blossom and e+ versions. - unsigned comment from Admin20Z (talk • contribs)
- Thanks for your suggestions, Admin20Z! I really like these ideas and will put them on my to-do list. Also, when you leave a comment on a talk page, please remember to sign it with four tildes at the end:
~~~~. This will produce a time-stamped signature so we can all more easily follow the conversation and can see who is replying to who. (talk) 18:12, September 28, 2021 (EDT)
Move Nookipedia:Community Fountain over to the talk page instead
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
After glossing over Nookipedia:Community Fountain, I have to say that there is no need for the page, especially since not much has updated for that page since Animal Crossing: New Horizons's launch, and it would be more appreciated to have a convenient spot to talk about discussions across Nookipedia.
There is still some useful info to use on Community Fountain, but I think we should just axe the page in favor of a redirect to this talk page. Do any of you agree? -- PanchamBro (talk • contributions) 20:47, September 30, 2021 (EDT)
- Move or redirect? You used both terms. ~SuperHamster Talk Contribs 20:53, September 30, 2021 (EDT)
- Ah sorry. I refer to moving as in making the main page a redirect and moving some or all content from that page over here. -- PanchamBro (talk • contributions) 20:54, September 30, 2021 (EDT)
- Gotcha, just wanted to make sure I understood. Thanks! ~SuperHamster Talk Contribs 20:55, September 30, 2021 (EDT)
- Ah sorry. I refer to moving as in making the main page a redirect and moving some or all content from that page over here. -- PanchamBro (talk • contributions) 20:54, September 30, 2021 (EDT)
- Support - Just for reference, this was originally brought up by Drago back in May on Discord. I agree that the sidebar should link to this page, rather than the project page. I don't support a redirect though, rather I think we should pare down the project page and transclude it to the top of the talk page. I suggested just keeping the 'things to do' and 'need help?' sections. If we do this though, we need to make sure we replace all links to the project page, since it will not be a redirect. This should be a relatively simple text replace.
- Also, this is perhaps a separate discussion, but how do we feel about changing the name of the Community Fountain to something else? It seems like maybe this was in reference to Serena's fountain in City Folk, and perhaps an AC-style take on Wikipedia's 'Village Pump'? Either way, I think that something like "The Bulletin Board" would be more appropriate, as it's something that is found in every game and its function is very similar to that of the Community Fountain (collecting messages/promoting discussion). (talk) 23:45, September 30, 2021 (EDT)
- Support - My preference would be to remove the main Community Fountain page (which I agree isn't very useful), and then move this talk page (and the archives) over to the regular Nookipedia namespace (so this would become the 'new' Community Fountain, if that makes sense).
- You're probably now thinking "But if this isn't going to be a talk page anymore, we won't be able to add new sections." I think there is a way to get around that, though, but I can't remember what it is right now. You definitely see it on Wikipedia with their village pump, admin noticeboard etc.
- As for the name, I think Community Fountain is fine, but I wouldn't be opposed to changing it to something related to New Horizons. I don't think "The Bulletin Board" is a good idea; it might be confused with our old Bulletin Board forums. I have thought of "Community Plaza" or "Resident Services" as alternatives (although this page isn't really a service). Drago (talk) 10:40, October 1, 2021 (EDT)
- To make sure I'm understanding correctly, you're suggesting we move the content from Nookipedia talk:Community Fountain to Nookipedia:Community Fountain and delete the current content at Nookipedia:Community Fountain?
- Not to put down the forums, but... I think you're giving their name recognition a bit too much credit, lol. Also I think it's a nice homage/call back to them. To be 100% honest... I was thinking to myself as I typed up the post "Wasn't there a Bulletin Boards site or forum or something? ...where am I remembering that from?" It's embarrassing to say I didn't remember that it used to be our own forum lol.
- I agree that it would be nice to change the name to relate to the most recent game, and I think The Town Tree would have been a good pick for ACNL, but I don't think that ACNH has many good options. Resident Services doesn't really make sense. Maybe The Roost? Would certainly capitalize on the hype, but I don't know if ACNH will become known for that (perhaps it's already infamous...). (talk) 19:58, October 1, 2021 (EDT)
- I agree that it would be nice to change the name to relate to the most recent game, and I think The Town Tree would have been a good pick for ACNL, but I don't think that ACNH has many good options. Resident Services doesn't really make sense. Maybe The Roost? Would certainly capitalize on the hype, but I don't know if ACNH will become known for that (perhaps it's already infamous...).
- Support per above. Also, I actually quite like the suggestion of renaming this space to "The Roost". The name also has the added bonus of being a consistent location throughout the series, so we wouldn't have to rebrand for each era of the series in future. :p --
Dorsal Axe (talk) 12:21, October 15, 2021 (EDT)
- Support per the above. ~ AlexBot2004 (Talk) 00:20, October 20, 2021 (EDT)
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Rename Community Fountain to 'The Roost'
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Given that a few of us have now discussed above renaming this space to 'The Roost', I figure why not open a separate discussion about this to avoid the original proposal from veering too far off-track.
Personally I Support this name suggestion. --
Dorsal Axe (talk) 15:32, October 18, 2021 (EDT)
Support per my comments above. Drago (talk) 11:10, October 19, 2021 (EDT)
Support per DorsalAxe's rationale in above section. --Jake (talk) 11:20, October 19, 2021 (EDT)
Support per DorsalAxe's comments in the above section. Ruthless Cutie
(Say hello :]) 19:54, October 19, 2021 (EDT)
Support - Sounds good to me! Thanks for making this a proper section/suggestion. (talk) 21:05, October 19, 2021 (EDT)
Support per the above. ~ AlexBot2004 (Talk) 00:20, October 20, 2021 (EDT)
Support per above. -- PanchamBro (talk • contributions) 01:14, October 20, 2021 (EDT)
Support per above too! vmario97 (talk) 01:37, October 20, 2021 (EDT)
Support per above, better tie in to Animal Crossing. ~SuperHamster Talk Contribs 02:13, October 20, 2021 (EDT)
Support per above. Kalina (talk) 
09:47, October 20, 2021 (CEST)
Support for the same reason as SuperHamster. Petaldancer66 {talk}
21:32, October 23, 2021 (EDT)
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Protection policy
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
I'd like to propose this written by Dorsal Axe as our new Protection Policy. It looks pretty much complete and I already made a few suggestions that were implemented. Please list your support/opposition here, thanks! Drago (talk) 12:07, October 5, 2021 (EDT)
- Support - Looks great! Very thoughtfully done, thank you Dorsal Axe for the time/effort spent, and Drago for providing suggestions/feedback.
(talk) 13:43, October 5, 2021 (EDT) - Support - Looks nice and great for a policy page. --Dr. Peach (talk) 13:07, October 6, 2021 (EDT)
- Support - Looks good to me. I will have to go over things more thoroughly prior to implementation to ensure everything is possible, but as it stands, this is a great improvement. --Jake (talk) 15:22, October 6, 2021 (EDT)
- Support per policy. -- PanchamBro (talk • contributions) 18:35, October 6, 2021 (EDT)
- Support - policy looks great and is very thorough. ~ AlexBot2004 (Talk) 15:20, October 9, 2021 (EDT)
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
writeapidenied on login via API using a Bot password
When I try to log in using a Bot password from Autotroph (talk | contribs | logs), I am received with the following message. Note that MY_PASSWORD_HERE is the bot password, and TOKEN_I_ACQUIRED is from the tokens API with type=login:
| Expand to view full error message content |
|---|
$ curl -v --request POST "https://nookipedia.com/w/api.php?action=login&lgname=Autotroph@Bruh&lgpassword=MY_PASSWORD_HERE&lgtoken=TOKEN_I_ACQUIRED&format=json" | jq
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 159.203.175.115:443...
* TCP_NODELAY set
* Trying 2604:a880:800:10::5f5:1:443...
* TCP_NODELAY set
* Immediate connect fail for 2604:a880:800:10::5f5:1: Network is unreachable
* Connected to nookipedia.com (159.203.175.115) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [10 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4048 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=nookipedia.com
* start date: Sep 28 21:50:52 2021 GMT
* expire date: Dec 27 21:50:51 2021 GMT
* subjectAltName: host "nookipedia.com" matched cert's "nookipedia.com"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
} [5 bytes data]
> POST /w/api.php?action=login&lgname=Autotroph@Bruh&lgpassword=MY_PASSWORD_HERE&lgtoken=TOKEN_I_ACQUIRED&format=json HTTP/1.1
> Host: nookipedia.com
> User-Agent: curl/7.68.0
> Accept: */*
>
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [57 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [57 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< server: nginx/1.18.0 (Ubuntu)
< date: Mon, 01 Nov 2021 10:30:02 GMT
< content-type: application/json; charset=utf-8
< x-content-type-options: nosniff
< mediawiki-api-error: writeapidenied
< x-frame-options: DENY
< content-disposition: inline; filename=api-result.json
< cache-control: private, must-revalidate, max-age=0
< x-request-id: f6e7719b7bb38ebcfa5bbbf3
< x-varnish: 42719977
< age: 0
< via: 1.1 varnish (Varnish/6.2)
< accept-ranges: bytes
< content-length: 341
<
{ [341 bytes data]
100 341 100 341 0 0 335 0 0:00:01 0:00:01 --:--:-- 335
* Connection #0 to host nookipedia.com left intact
{
"error": {
"code": "writeapidenied",
"info": "You're not allowed to edit this wiki through the API.",
"*": "See https://nookipedia.com/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
}
}
|
This also affects tools such as AWB. Have some settings changed in the last few months? The last time I used a bot was in 7 August 2021. Decomposer 06:36, November 1, 2021 (EDT)
- Ouch. Both User:Vmario97 and myself have also experienced this error when trying to use PyWikiBot. Oddly enough, it only happens on Windows for me - PyWikiBot continues to work fine on my Mac. Not sure the source of this error, but we'll continue to investigate. Also CCing User:Jake. ~SuperHamster Talk Contribs 16:38, November 2, 2021 (EDT)
- Just thinking out loud here. We recently upgraded to MediaWiki 1.35.4, so I took at the release notes to see if I can find anything related. There was a change to the login process ("Mark ApiClientLogin/ApiLogin as requiring write mode"), but we already grant bots the
writeapiuser right, so...there shouldn't be an issue there. ~SuperHamster Talk Contribs 18:04, November 2, 2021 (EDT)- Actually, this is likely it! Most wikis grant everyone (including the unauthenticated) access to writeapi; we do not. As a result, logging in fails since it was marked as requiring writeapi in 1.35.4. ~SuperHamster Talk Contribs 20:35, November 2, 2021 (EDT)
- I have made this temporary adjustment until the upstream change is reverted by the MediaWiki core team, and I suspect API queries will now work as intended. I still have no idea why Mac users were not affected by this. --Jake (talk) 21:30, November 2, 2021 (EDT)
- Succeeded for me, thanks! Maybe my Mac still had a proper auth token or something ¯\_(ツ)_/¯ ~SuperHamster Talk Contribs 21:42, November 2, 2021 (EDT)
- Nice, it works for me as well. Thanks! Decomposer 00:13, November 3, 2021 (EDT)
- I have made this temporary adjustment until the upstream change is reverted by the MediaWiki core team, and I suspect API queries will now work as intended. I still have no idea why Mac users were not affected by this. --Jake (talk) 21:30, November 2, 2021 (EDT)
- Actually, this is likely it! Most wikis grant everyone (including the unauthenticated) access to writeapi; we do not. As a result, logging in fails since it was marked as requiring writeapi in 1.35.4. ~SuperHamster Talk Contribs 20:35, November 2, 2021 (EDT)
New Leaf remixes
In many pages there are no NL remixes of K.K. Slider's music (SNES and House). In my opinion, they should be like Aircheck and Live. I was wondering about two option. Option 1 Add two slots in Infobox Music to add NL remixes and Option 2 add a small table for NL remixes. What do you think about it? If you have a better idea, please feel free to write, Thanks. Kalina (talk) 19:15, November 4, 2021 (CET)
- It makes sense to me to add the New Leaf remixes to the infobox... unless there are even more versions from other games, in which case I would be more in favor of option 2. Are these files already on the wiki? (talk) 21:15, November 4, 2021 (EDT)
- There are also versions like Music Box, Aircheck ("Cheap"), Aircheck ("Phono") and Aircheck ("Retro"), so I guess the table will make more sense. Probably not, but I know that Chubby Bub wants to upload NL music files. Kalina (talk) 7:24, November 5, 2021 (CET)
- Personally I'd prefer a separate table for all the different mixes/variations. Otherwise the infobox is going to become quite large, and I don't think it's necessary to have every single version of a song in there to be honest. -- Dorsal Axe (talk) 03:48, November 8, 2021 (EST)
- Personally I'd prefer a separate table for all the different mixes/variations. Otherwise the infobox is going to become quite large, and I don't think it's necessary to have every single version of a song in there to be honest. --
- There are also versions like Music Box, Aircheck ("Cheap"), Aircheck ("Phono") and Aircheck ("Retro"), so I guess the table will make more sense. Probably not, but I know that Chubby Bub wants to upload NL music files. Kalina (talk)
- I think a table is the way to go. But I have bigger ideas... I'm working on ripping every game, and hopefully at some point everything will be done... right now only NL is and I intend to upload it soon. But each K.K. song has a different amount of variations in each game, and those variations themselves differ from game to game. So I think we should include each of these under each game's section under Appearances on a song's page. Personally, I think the best way to do this would be to use Template:Music Box in a similar fashion to the first part of SuperHamster's sandbox here, with each box representing a variation of the song per game. For example, under a song's "In New Leaf" section, we would have boxes for Live, Aircheck, Music Box, DJ KK House, and DJ KK NES. And text could go in these sections describing relevant aspects of the songs and how they changed in between games. Chubby Bub (talk) 03:09, November 9, 2021 (EST)
Add the villager's Japanese name in main prose
There's a concerning amount of readers who often gloss over our villager articles simply due to the fact that we lack the Japanese names in the main prose, both in the original language and romanized. I would suggest adding this information in so that people will understand their Japanese name more. -- PanchamBro (talk • contributions) 11:54, November 11, 2021 (EST)
- Regarding "concerning amount" - on Discord you mentioned one user, is there more? ~SuperHamster Talk Contribs 12:05, November 11, 2021 (EST)
- I believe there are two additional users who aren't too pleased with the fact that we omit their Japanese name from the prose. -- PanchamBro (talk • contributions) 19:56, November 11, 2021 (EST)
- I agree that we should add the Japanese name to the prose for villagers without an official English name. I also think we should do so for villagers who received an official English name in the most recent main-series Animal Crossing title (in this case, New Horizons), as up to that point they have been known by their Japanese name longer than their English name. As for villager pages generally, I don't see it being particularly useful to readers. If there is something of interest having to do with their Japanese name it can be mentioned in the Trivia section or in their introduction. (talk) 16:05, November 12, 2021 (EST)
- This is something we used to have, but was stripped out to give equal prominence to all supported languages. I'm not really for or against reinstating it, though I agree with Sunmarsh's suggestion above that this would be best for characters that haven't been localised.
- I do think the lack of romanisations in the infobox is a big problem however, not just for Japanese, but all non-Latin-based languages. I saw the idea of improving Template:Tt was floated on the Discord, but I'm against that as it's still not intuitive and has accessibility concerns (and quite frankly, that template just needs to go at this point). I think it would be straightforward enough to add the romanisations into Template:Translation in plain text. Though...I must admit I've never really understood why the infoboxes even contain this information in the first place, given that we have a dedicated section for languages on each character's article. It's always seemed a bit of unnecessary bloat to me. -- Dorsal Axe (talk) 18:21, November 12, 2021 (EST)
- Support re-adding the note to the Japan-only villagers and the returning ones from Doubutsu no Mori e+ in New Horizons per sunmarsh. ~ AlexBot2004 (Talk) 19:04, November 12, 2021 (EST)
- I would Support this on all villager and special character pages using Template:Nihongo, I think it's useful information especially as the Japanese names often convey info about the character it might be good to have as context before reading the article. Wikipedia often does the same thing for similar reasons, and the reason Japanese is of note is because that is the character's "original" name. I think it's better to be consistent than to just do some pages. That said, it's not that big of a deal to omit, as it's still present later in the article. As Dorsal Axe points out, there was talk of using the Tt template for infoboxes, but that discussion was actually about making it more clear, and accessible on other devices. I don't know if anything will come of it though. Plain text would work too. Chubby Bub (talk) 02:24, November 23, 2021 (EST)
Comment - Just making a note here that I have created Category:Characters with no English localization, which will help a bit if we decide on partial implementation. (talk) 13:35, November 29, 2021 (EST)
Table for villager's catchphases
I think would it be good if the catchphrase page contained a table with all the villager's catchphrases. It would be easier to find all villagers catchphrases instead of searching through pages. What do you think? Kalina (talk) 16:21, November 12, 2021 (CET)
- Support - sounds good to me! ~ AlexBot2004 (Talk) 13:43, November 12, 2021 (EST)
- Support - I also like this idea. Akuhime-sama (talk) 15:03, November 12, 2021 (EST)
- Support - This is a great idea, thanks for the suggestion! (talk) 16:06, November 12, 2021 (EST)
Establishing a formal proposal process for major wiki changes
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
I'd like to propose adding a new page to the Nookipedia namespace (Nookipedia:Proposals), and creating a new formal process for implementing large-scale changes to the wiki. In the past, we've simply used the Community Fountain for this purpose, have held discussions on individual talk pages, or have discussed externally (Bulletin Board Forums/Discord) before coming to consensus and then taking action. I think that both this page and other individual talk pages are great for inviting discussion on a topic, generating ideas, and getting feedback, but for proposals that impact a large amount of pages or users, I think there should be a more formal approval process so that everyone has a chance to participate in discussion before implementation. Here are some of the ideas I had for this proposal system:
- Proposals are necessary for changes that would affect a large number of pages or users. Some examples: rules/policy changes, adding/removing namespaces, making major modifications to/replacing templates that affect 1000+ pages.
- Proposals are for voting on fully worked out ideas. Proposals can be submitted without prior public comment or feedback, but should not receive major edits or changes once voting has started.
- The voting period for a proposal lasts a set period of time, similar to a staff application, and is open to vote and commentary from all editors.
- At the end of the voting period, the support/oppose tally will be counted by a staff member, and a specific user will be assigned to implement the change (it could be the user who submitted the propsal, or a staff member, as necessary). This helps to make sure the change takes effect as promptly as possible once a decision has been reached.
- Ideally, active proposals would be displayed on the main page, and staff members (or ribbot) could alert those with the Editor role on discord when a proposal is coming to a close.
I'd love to hear your thoughts/feedback on this! (talk) 10:23, November 17, 2021 (EST)
- Support It's a great idea to create Nookipedia: Proposals. Also, I think it would be helpful if this page had an instruction or something like rules. I really like the ideas you wrote, they would definitely be useful! Kalina (talk) 20:48, November 17, 2021 (CET)
- Support - I think a more formal proposal system would be very helpful in bringing more attention to proposals and preventing them from potentially getting buried here. ~ AlexBot2004 (Talk) 21:08, November 17, 2021 (EST)
- Comment So far this is looking good, and as the rest of the staff will know, I've long been a supporter of this idea. However, there's a few questions I'd like to ask before I consider a vote:
- 1. Will there be a minimum support percentage needed? What happens if there's a tie? Does the proposal get extended?
- 2. You've suggested that voting and commentary would be open to all editors. I agree that anyone should be able to comment, but allowing IP voting is not something I'm keen on. It would be too easy for someone to vote twice.
- 3. Regarding assigning someone to make the changes; this could work, but it could also get messy. Can you explain a little more on how this would work?
- 4. Will we just be limited to Support/Oppose proposals, or will we be able to create ones with three or more options (this could also get messy)?
- Overall though, great work so far, and I look forward to seeing how this develops! Drago (talk) 12:23, November 18, 2021 (EST)
- Answering your questions:
- 1. I had initially thought it would be simple pass/fail based on the number of support vs oppose votes, but I think it makes more sense to get 2/3 majority (similar to the adjustments put forward by SuperHamster at Nookipedia talk:Staff/Apply). This also solves the tie problem, as a tie vote would not be enough to pass. As far as proposal extensions are concerned, I think it should be at the discretion of the staff member(s) who is/are in charge of administering/closing the proposal process. So, an extension could be requested by the user who submitted the proposal, or it could be extended independently by a staff member, at their discretion.
- 2. I agree that all those who intend to vote must have an account/be logged in. Additionally, I think that only registered users should be able to put forth proposals.
- 3. After thinking about how assigning specific users (or even user ranks) would work, I think that it makes things a bit overly complicated. We would need to have some conversation about this among staff members, but I think that it could be the role of bureaucrats to administer/close voting on proposals, and then, if a proposal passes, they should then either enact the proposal themselves, or coordinate with other staff members to make sure the proposal is completed. Perhaps a bureaucrat is responsible for closing voting, and then whoever actually enacts the proposal follows up and adds a note to the closed proposal to confirm it has been completed. The bureaucrat could be responsible for adding the task to the Nookipedia Tasks board, for example. Alternatively, they might discuss the proposal implementation process in either the staff channel on Discord, or on some other channel explicitly created for handling proposals.
- 4. I think a proposal should not have any yet-to-be-determined components. It should be a complete proposal with no 'option a, b, or c'. This is why getting input prior to submitting the proposal (e.g. by posting about it here), should continue to be encouraged. (talk) 19:40, November 18, 2021 (EST)
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Image gallery to infoboxes
Wouldn't it be good if infobox such as: Infobox Video Game, Infobox Location e.t.c had gallery (look at Isabelle's infobox)? I think it would be easier to find a gallery. What do you think? Kalina (talk) 12:11, November 19, 2021 (CET)
- Support - You're referring to the purple gallery button in the Infobox, right? I agree that it would be helpful on other types of pages, especially the game pages as they have tons of images. (talk) 10:08, November 19, 2021 (EST)
- Support though I'm not sure this even really needs to be put to a vote. It's trivial to enable this, as the functionality is built directly into the base infobox template. All you have to do is add
subtitlebelow = galleryto the infobox template and it will show this link if a gallery subpage exists. -- Dorsal Axe (talk) 11:30, November 23, 2021 (EST)
Compliments to the person or people who made the random page/item generator! It's quite cool! MyDearDeirdre (talk) 13:33, November 19, 2021 (EST) Oh, and if this is in the wrong category, move it to the right one please! I'm new.
Music in infoboxes
Thanks to Kalina70's hard work, we have tables for each version of a song on K.K.'s song pages, and event and location pages have a similar music section. (They currently generally only have the versions from New Leaf and New Horizons since that's what I've finished ripping, but the rest are still to come.) Right now, the infoboxes for each of these types of pages has the newest and/or default version of the song, and the tables in the music section are missing these since they're in the infobox. I am proposing that at the very least all versions of the song are included in the table, and that perhaps they're unnecessary in the infobox at all now that we have dedicated music sections. Chubby Bub (talk) 02:09, November 23, 2021 (EST)
- Support I think it would be good if that were the case as it doesn't make sense that there is two songs from NH in infobox, but the rest of the music from other games in the music section. Btw i can do it if proposal will be supported. Kalina (talk) 13:44, November 23, 2021 (CET)
- Support I've been thinking the same thing, and it's kind of confusing having it in both the infobox and the table. I think going forward, we should only have music in the infobox for video game articles (e.g. the main theme of the game) and articles for K.K. Slider songs (where each song is always the same across different games). -- Dorsal Axe (talk) 11:26, November 23, 2021 (EST)
- Support - I agree with Dorsal Axe that we should just have one song in the infobox and it should be limited to K.K. Slider Songs & main themes. I also agree that the music table should list all versions of the song (even if that means the song appears twice on the page- once in the infobox and once in the table). (talk) 13:48, November 26, 2021 (EST)
- Support - Per everyone. --Dr. Peach (talk) 14:52, January 8, 2022 (EST)
Realign the sections on our villager pages
As of now, our villager pages are organized under this fashion (example from Rosie):
- 1 Characteristics
- 1.1 Appearance
- 1.2 Personality
- 2 Villager information
- 2.1 In Animal Crossing
- 2.2 In Wild World
- 2.3 In City Folk
- 2.4 In New Leaf
- 2.5 In New Horizons
- 2.5.1 In Happy Home Paradise
- 3 House
- 3.1 In Doubutsu no Mori and Doubutsu no Mori+
- 3.2 In Animal Crossing
- 3.3 In Wild World
- 3.4 In City Folk
- 3.5 In New Leaf
- 3.6 In New Horizons
- 4 Other appearances
- 4.1 In Gekijōban Doubutsu no Mori
- 4.2 In Happy Home Designer
- 4.3 In Pocket Camp
- 4.4 In Super Smash Bros. Brawl
- 5 Card profiles
- 5.1 Animal Crossing e-Reader card
- 5.2 amiibo cards
- 6 Gallery
- 7 Trivia
- 8 Names in other languages
- 9 See also
- 10 Notes
- 11 References
Currently, we divide the other appearances section from the villager information section, but given how Animal Crossing: Happy Home Designer and Animal Crossing: Pocket Camp are still Animal Crossing games, we should move the Happy Home Designer and Pocket Camp sections up to villager information and leave the other appearances for 🎬 Gekijōban Doubutsu no Mori and (if applicable) the Super Smash Bros. series and Mario Kart 8. -- PanchamBro (talk • contributions) 11:15, November 23, 2021 (EST)
- Support - Makes sense to organize them in your suggested way.--Dr. Peach (talk) 13:10, November 23, 2021 (EST)
- Oppose - I think that this makes things a bit confusing as it departs from the way these games are organized in the Infobox (they are listed under 'Other appearances'). I think the distinction between main-series titles and spinoffs is important, especially when it comes to items, and specifically when it concerns Animal Crossing: Pocket Camp (e.g. Pocket Camp-only fish and bugs that don't function the same as they do in other games). Edit: I understand this proposal is specifically for villagers, but these pages would then be inconsistent with other article pages. (talk) 13:54, November 26, 2021 (EST)
- I see where you're coming from, but when you address fish and bugs, there are some that have both Pocket Camp and mainline games all under the same section. In my opinion, it would be nicer to have the information unified under one section, given how large {{PCVillagerInfo}} has become thanks to my redesign. Perhaps we could move the "Other appearance" section to be above "House", but I don't know how viable it could be. -- PanchamBro (talk • contributions) 13:08, November 27, 2021 (EST)
How to upload images (Mobile)
Hi, I’m trying to figure out how to upload an image. It says that I removed the file info template even though I didn’t do anything. How do I fix this? Thanks, BadTime123 (talk) 06:57, December 30, 2021 (EST)
- Hi, you need to add {{File Info}} template to the image and fill it (Add source and description). Also here is example File:395 Cally amiibo card JP.png. Kalina (talk) 14:00, December 30, 2021 (CET)
How do you make a bot?
Hi,
Does anyone know how to make a bot code?
Cheers,
ToadetteFan007 (Talk) 
04:47, February 5, 2022 (EST)
- Majority of bots used here are operated using a programming language (e.g. Go, C++). My bot (PanchamBot), uses Python for parameter additions, file moves, and page creation functions. Warning tho, you will need to have administration permission and lots of coding experience if you want to operate your own bot someday. -- PanchamBro (talk • contributions) 10:20, February 6, 2022 (EST)
HHA furniture theme collection mergers
I'm proposing for Pirate Ship Theme and Mario Theme to merge with Pirate Series and Mario Series (with or without Super Mario Set merged) respectively. A big reason has to be how they are transcribed in different languages. For Pirate Ship Theme and Pirate Series, they share the same Japanese (かいぞく), Korean (해적), Spanish (pirata), and German (Piraten) translations. As for the Mario Theme and Mario Series, their translations are pretty identical,
I have another reason, that given how furniture series have changed in New Horizons from having the same bed, drawer, table, and chair features to diverse furniture parts that may or may not have all of the following classifications, that it addition to the translations, they are justified because of the changes made to New Horizons's furniture collection classification. So they are the same collection, just under a different name.
Let me know what you guys think of these changes. -- PanchamBro (talk • contributions) 18:08, February 27, 2022 (EST)
- Comment Are there existing pages where themes/sets and series have been merged? I'd like to know what they look like. Also I don't understand why translations should matter in decisions like these since this is an English wiki. Could you clarify/expand your reasoning here, please? Melicent (talk) 19:07, February 27, 2022 (EST)
- Comment Jingle Series merging with Festive Series and Pavé Series merging with Festivale Series on the premise of shared Japanese translation for each are instances. And translations can matter in situation in regards to if a furniture series/set/theme is the same as before or if it's a different series/set/theme overall. Office Set and Office Set (Clerical) is an example of this. -- PanchamBro (talk • contributions) 19:31, February 27, 2022 (EST)
- Comment Thanks for taking the time to explain! I was wondering specically about sets and/or themes being merged into series pages (or sets being merged into themes) and whether there were already precedents, in which case what you suggest is usual modus operandi on the wiki and I'm all for it. I've tried looking for some but only found the cases you mention (series being merged into other series with similar names/furniture, etc.). However, I don't know the franchise and the Nooki well enough. Melicent (talk) 07:08, February 28, 2022 (EST)
Festivale Feathers
Hey, I noticed that when referring to the Feathers collected during the Festivale event, the hyperlink for ‘Feathers’ leads to the disambiguation page for Feather. I was wondering whether I should create a new page for specifically the Feathers collected during Festivale or if I should change the hyperlink to one of the individual feather pages and if so, which one? Thank you for the input and of course please tell me if I have overlooked something or made an error in someway!
--TapDanceDruid (talk) 11:32, February 28, 2022 (EST)
- Welcome to Nookipedia, TapDanceDruid! In response to your question, I'd say the link should just be removed. The feathers already have individual item pages for New Horizons and I don't think they're notable enough for their own page. Drago (talk) 11:41, February 28, 2022 (EST)
- Drago beat me to it, but I'll say what I was suppose to say: in regards to the disambiguation page I would probably add the item pages associated with the feathers to the page (e.g. Green Feather, Blue Feather, Red Feather, Purple Feather, and Rainbow Feather) but a new article about feathers doesn't sound bad to me. I would like to know how it would look like first, so I recommend creating a user sandbox here. But as Drago mentioned, there might be some notablility problems, so keep that in mind. -- PanchamBro (talk • contributions) 11:49, February 28, 2022 (EST)
- I agree that the wiki could use a Feathers page. They are collectibles in both New Leaf and New Horizons, having a centralized page that's all about feathers would be useful. HylianAngel (talk) 16:46, February 28, 2022 (EST)
- Drago beat me to it, but I'll say what I was suppose to say: in regards to the disambiguation page I would probably add the item pages associated with the feathers to the page (e.g. Green Feather, Blue Feather, Red Feather, Purple Feather, and Rainbow Feather) but a new article about feathers doesn't sound bad to me. I would like to know how it would look like first, so I recommend creating a user sandbox here. But as Drago mentioned, there might be some notablility problems, so keep that in mind. -- PanchamBro (talk • contributions) 11:49, February 28, 2022 (EST)
Create villager/special character ID redirects
I've been thinking a lot about the implementation of IDs for villagers and special characters, and if it's plausible to have redirects based on a villager or special characters's ID. It would certainly be somewhat easier to search for a particular codename and then go to the character associated with it.
There are certain articles that will need to have a notice due to this (e.g. Doc already exists as a villager so a notice would need to be added to redirect people to Wilbur in the event that someone wanted to search his codename). -- PanchamBro (talk • contributions) 10:00, March 14, 2022 (EDT)
