Nookipedia talk:The Roost/2023

Add internal name and ID regarding item
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Something that has been on my mind lately was adding internal name and ID regarding a particular item. For instance, the tulip table in Animal Crossing has the filename sum_poptable01
and the internal ID 126C
. I believe having information on the item pages would be useful for dataminers, modders, and such if they wanted to inspect information regarding a particular item instead of having to waddle through loads of spreadsheet information. -- PanchamBro (talk • contributions) 09:26, January 29, 2023 (EST)
Support for the reasons you've given. --BladeofEvilsBane (talk) 10:36, January 29, 2023 (EST)
Support ~ AlexBot2004 (Talk) 14:58, January 29, 2023 (EST)
Support Briky
15:34, January 6, 2024 (EST)
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
The animal emoji redirects
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
Right now there are some emoji redirects involving the species pages. Currently these redirects exist: 🐂 🐊 🐒 🐕 🐦 🐵 🐶 🐺 🐻 🦍 They are kind of peculiar, and I can't really gauge if these would necessarily be useful. They're so silly that I wouldn't even mind keeping them. I had to do a double-take when I checked Wikipedia, and they actually utilize emoji redirects, so it seems like they potentially serve some sort of usefulness. But either way, we should either:
a. Complete the collection and create more redirects involving the remaining missing animal emojis from the species pages
b. Delete the existing animal emoji redirects.
What do you think? HylianAngel (talk) 02:28, February 6, 2023 (EST)
- Very much against the use of animal emoji redirects. I just do not think they are reasonably used or feasibly searched. Trig - 02:07, February 10, 2023 (EST)
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.
New Project: Project Languages
I think we should start a project where we fill up the boxes with "unknown" in on templates. --Sylveon (Autistic and proud!)🍉🌺 08:53, February 17, 2023 (EST)
- Currently, the major missing romanization on all articles, especially villager articles, is Traditional Chinese, as it was made a separate entry from Simplified Chinese. For Japanese, Korean, and Simplified Chinese (the mainland language of China), you can pretty much use Google Translate to obtain an acceptable romanization of the name. However, Traditional Chinese is a slightly more complicated subject to tackle.
- I asked my Chinese friend if this Traditional Chinese romanization of Marina's name was correct, because it was so different from the Simplified Chinese romanization. Zhānglìnà vs. Jēung Laahp Nóh is crazy different, to me as an English-speaking person. But no, she mulled it for a few seconds and said, yep, the Traditional Chinese romanization in this situation is correct. Nookipedia is using the Hong Kong flag, which implies the dialect is Cantonese. I asked her to ignore the flag, and she said you can't do that, the flag matters. I told her that most other wikis, like Bulbapedia and WiKirby don't use flags, and they usually have it simply stated as "Simplified Chinese" and "Traditional Chinese" in written text without flags, and that they tend to make both of those romanizations identical. She said that's the wrong way to approach it, since you're basically erasing an entire dialect from existence by making the romanizations identical. I asked her, would it make sense to make the Traditional and Simplified Chinese romanizations the same if the flag was not there at all, and she said, yes, some dialects of Traditional Chinese would have identical romanization as Simplified Chinese, but that is why the flag is so important in this scenario because the Hong Kong flag implies the Cantonese dialect, and you shouldn't make the romanizations the same if it's the Hong Kong flag.
- She also explained that China has been attempting to erase Cantonese for some time in order to make Simplified Chinese the main language. Another unfortunate aspect is that we wouldn't even be able to obtain any Cantonese Traditional Chinese romanizations on Nookipedia without the help of a Cantonese-speaking person, because Google Translate spits out identical romanizations for Simplified and Traditional Chinese anyways. So we have a major problem where the Hong Kong flag would be misleading if we were to copy-paste the Simplified Chinese romanizations to be the same as the Traditional Chinese romanizations, but if we were to decide to stick with Hong Kong/Cantonese, we probably will never have any Traditional Chinese romanizations ever, unless a Cantonese person decides to join and contribute for every page (and my Chinese friend does not know Cantonese). HylianAngel (talk) 16:13, February 17, 2023 (EST)
- I may not know much about Cantonese at the moment, but I've been thinking about it considering that it has several romanizations that could be used here. I'm pretty sure Bulbapedia used Yale romanization for Cantonese, but on the other hand, there's also Jyutping romanization. If we can get some pointers on which of these romanizations should be used here, it would be a good start. Not to mention, the example of Marina earlier on seems to be using Yale's. Starry Windy★ 23:05, November 29, 2023 (EST)
Villager Quotes
Hi! I am new to being an editor, but recently I noticed Nookipedia doesn't do individual quotes for villagers, something the Animal Crossing Wiki does do. I've been adding quotes for a few villagers, but not too many. I wanted to garner some support before I continue to do more. I know most quotes are similar within personality, but there are some, like picture quotes, that are individual to certain villagers. I think this could be really cool to do for every villager, because the rest of the villager page isn't very personalized at all. Plus, sometimes, people only need the page to look for the picture quote, and putting it at the top of the page could be useful. I think it would be fun for the editors, and readers, to mix it up a little. So, community, do you have an opinion? Should I keep going? Omigpine11 (talk) 17:59, March 11, 2023 (EST)Omigpine11
- Although photo quotes are "unique dialogue" involving the villager, I feel it is not needed to include it at the top of the page, since this info is available within the infobox ("favorite saying"), which is very close to the top of the page already. If a reader only needs the photo quote, they already have easy access. These quotes are also located on the Photo page. I personally
Oppose adding photo quotes to the top of villager pages. However, I
Support adding quotes on villager pages in cases where it is in-game dialogue completely exclusive to the villager. These cases are rare, but some cases do occur in New Horizons involving very specific species-personality combos (where there is only 1 villager who is that species-personality, like Wendy the peppy sheep, on Year of the Sheep). While it's not really from the game, I agree with the Alfonso quote you added from the official NH website, since it is indeed completely unique. HylianAngel (talk) 18:25, March 11, 2023 (EST)
- Actually HylianAngel, the top quote on Alfonso's page is a quote lazy villagers say in New Horizons, just that "This place" is replaced with whatever you named your island. Just a warning that the source I am about to provide does contain some very crude language, but it's the only proof I was able to find of the quote being used in-game, so please bear with me on this one (quote is on the 4th pic): https://imgflip.com/i/43nbpn
- That being said, I don't really mind it being Alfonso's top quote since the website does make that association.
The Jacketed Terrapin
18:31, March 11, 2023 (EST)
- Thanks, I should have worded it more clearly that it's a unique association. I did remember the dialogue from playing NH, so saying "completely unique" was not entirely correct when I was trying to convey my reasoning. HylianAngel (talk) 18:34, March 11, 2023 (EST)
- That being said, I don't really mind it being Alfonso's top quote since the website does make that association.
- I wanted to mention that I went ahead and added the unique dialogue involving New Year's Day for unique species-personality combos to the "Trivia" sections of the involved pages, but only for bulls/cows (2021), tigers (2022), and rabbits (2023). So this would be Coach, Norma, Patty, Rolf, Claudia, Gaston, Coco, and Mira.
- I didn't add the dialogue for future years yet, which would be horses (2026), sheep (2027), monkeys (2028), birds (2029), dogs (2030), pigs (2031), and mice (2032). Actually, from reading the dialogue files, it's unclear if Year of the Rooster (2029) will apply to all bird-related species (birds, ducks, eagles, ostriches, penguins, and chickens), a subset of these bird species, or just chickens themselves. The dialogue specifically says "Year of the Bird," or "Year of the Rooster," depending on the personality type of the speaking villager, but mostly these dialogues state "Year of the Bird." Unless someone time travels to 2029 and checks each species, or unless a dataminer could examine the code, it probably won't be known. Anyways, I felt it would make sense to just add the dialogue for 2021-2023 and not the future years yet. However, I wouldn't be against adding the future years either. HylianAngel (talk) 07:14, March 12, 2023 (EDT)
Villager catchphrases
I strongly believe that villager pages should have a dedicated section to their catchphrases in each language, in the same style as their given name in the "Names in other languages" section. Currently there is not a good place to describe the meaning of a villager's foreign catchphrases, so there are cases where the Japanese catchphrase holds some relevance to the character, but since there is no decent section to place it, it is instead placed at the top of the page, where it sits next to any relevant English given name and English catchphrase origin information. That location is somewhat awkward, since it's inconsistent to have the English given name, the English catchphrase, no Japanese given name (since Japanese name info is generally placed in the "Names in other languages" section), and then the Japanese catchphrase.
If there was a dedicated section for catchphrases in other languages, it would not only allow describing any Japanese catchphrase relevance, but also the relevance of catchphrases of every other language as well, and there is currently no location to place non-English or non-Japanese catchphrase relevancy information. Basic "names in other languages" and "catchphrases in other languages" data exists in the infobox, and yet only the "names in other languages" is duplicated at the bottom of the page. I believe both should be at the bottom of the page.
While the main article header would be "Names in other languages," there are 2 different formatting styles that could be implemented:
- The sub-headers are the words "Given name" and "Catchphrase."
- Optionally and additionally, in combination with this style so that the name and catchphrase are extremely explicit, a parameter for the English name can be included, like how Fire Emblem Wiki does it (example here). While it might be currently redundant with the English information included in the intro prose, I think it's fine for there to be redundant information, as many villager pages already do repeat redundant information (like the infobox repeating the foreign names information), and it can serve a very useful utility purpose if intros are ever repurposed to no longer include English name/catchphrase origins. Plus, it would allow for future "favorite sayings" English explanations, which no intros do unless it's related to the character's identity/species somehow, but I feel this would be good information to include no matter what.
- The sub-headers are the character's actual name and catchphrase, like for example Sherb, the sub-headers would be "Sherb" and "bawwww."
I'm also open to other suggestions for the formatting style. I'm slightly partial to the first style, just because there might be a case where "favorite sayings" are also given their own dedicated section in the future, and the full saying might be weird as a header. What formatting do you think would be best? HylianAngel (talk) 14:50, April 4, 2023 (EDT), edited again on 16:11, April 22, 2023 (EDT)
- If this is something you're still interested in, I'd love to work with you on implementation! I agree that catchphrases are one of the few unique personality-defining characteristics of a villager (as most of their dialog is shared), and agree we should have a space to talk about the nuances of their catchphrase in different languages. I'm not entirely sure I understand what you're suggesting regarding implementation, though. I can't tell whether you're suggesting to add catchphrases to {{Foreignname}} or whether you're suggesting a new template & section that also includes the given name. I think that having its own section and template is best, and it would appear very similar to Foreignname, which actually doesn't have any headers at all (the meaning of the columns is inferred from the title of the section).
(talk) 02:30, June 27, 2024 (EDT)
I caught the spirit!!
I caught farley!! ~ 08:51, April 11, 2023 (EDT)
Trig Jegman's File Template
As I am sure you have seen, I've been working on the creation and generation of my file module for Nookipedia. The time is now to suggest that it is used instead of the existing Template:File Info.
First, to be explicitly clear, this module would work the same as a template to the degree that I have made sure everything will retroactively work on it. Nothing would break by the implementation of the module.
Second: My module is a lot beefier than the existing template is now. Here's the main takeaways:
- Combined licensing. No more need for having 33 different licensing templates, when the module will take care of all of them collectively.
- More maintenance parameters and a closer analysis of sourcing. There are several maintenance features included, such as files taken from FANDOM sources or YouTube.
- Predesignated sources for when the user captures an image themself.
- Automatic categorization. This is the big one: Through the introduction of two new parameters (game and type), files will now automatically be categorized into their appropriate categories, making widescale changes easier and formatting more consistent.
- This is an excellent opportunity to look at all of the files on site and reduce duplicates, fix naming, improve quality, and get specific sources amongst other tasks.
I wouldn't propose this if I didn't have great success in implementing this before. I have completely added this style of template to every single file on WiKirby, Wars Wiki, Inkipedia, MiiWiki, The Cycle: Frontier, as well as partial completion on Mystery Dungeon Francise Wiki, FamiWiki, and StrategyWiki. I've done it before and I'm more than happy to do it again to get this implemented. I really think that having this upgrade is a valuable resource and helps create consistency both on this site and in conjunction with other wikis as well. I have a few examples of use cases here to understand what it might look like. The new parameters are the following:
- Game — Allows an automatic link to a game, and can work to add automatic categories.
- Type/Meta — These two pull from a determined list of common types (such as Artwork, Screenshots, Amiibo, or User Files) in order to automatically categorize files. The difference between type and meta is that type will categorize based off the game entry (New Leaf sprites), meta will only do off the type (Sprites).
- User — Used for user files or when attributing the source to someone else.
- Author — At the suggestion/request of Shams, useful for creative commons files.
- License — All those licensing templates are here now
- Fandom/Youtube — By setting these to yes, it places files taken from these less than desirable locations into a maintenance category for replacement.
I'm happy to make more examples, or give breakdowns of how I would go about fixing these, or answer any questions about it. Please let me know how you feel about implementing it on Nookipedia as well! Trig - 13:22, June 28, 2023 (EDT)
Support - Everything here looks great! The combined licensing and automatic categorization are especially welcome additions; I can't think of anything at the moment that I'd add or change. ~ AlexBot2004 (Talk) 01:08, July 6, 2023 (EDT)
Support I think this could work. I do believe though that if we agree on this more, we should set up a proposal to implement. -- PanchamBro (talk • contributions) 16:41, September 5, 2023 (EDT)
New Horizons villager box item capitalization
PanchamBro's bot fixed the capitalization of New Horizons items on almost all villager pages, but since Jacob/Jakey and Spork/Crackle have 2 different names, I think the bot skipped over those two. Making a note here that it needs to eventually be fixed, don't have time to fix it myself at the moment. HylianAngel (talk) 15:51, July 29, 2023 (EDT)
- This should be fixed now! -- PanchamBro (talk • contributions) 01:05, August 2, 2023 (EDT)
- Thank you! HylianAngel (talk) 20:51, August 4, 2023 (EDT)
wanna join my club???
it is called bob fan club - unsigned comment from FroggyPotter (talk • contribs)
Help with Cargo Tables
Are there any resources to help figure out how they work? If not can some please explain them to me? TheMajesticPineapple (talk) 22:56, August 24, 2023 (EDT)
- Here are a couple of resources:
- https://www.mediawiki.org/wiki/Extension:Cargo (also check out the Storing data and Querying data subpages)
- https://help.fandom.com/wiki/Extension:Cargo
- https://support.wiki.gg/wiki/Cargo
- My personal understanding of it is that the gist of it is that you'll have a template for a type of page with a bunch of input fields. In the template you say that inputs in those fields get stored in a big behind-the-scenes table. You can then create a cargo query table to list specific stuff from that big table on any page you want. For better understanding the template side of things it helps to look at templates that use cargo, and for cargo query tables it helps to look at and compare different pages that use different cargo queries. Hope this helps a bit! Bassieeee (talk) 07:19, August 25, 2023 (EDT)
- Thank you so much, I couldn't find anything on them anywhere.
- TheMajesticPineapple (talk) 09:30, August 25, 2023 (EDT)
- Nookipedia:Project Database has some good information on cargo tables, and we have a channel for discussing cargo tables on our Discord server. --BladeofEvilsBane (talk) 19:00, August 26, 2023 (EDT)
Ideas.
1. Project Trivia. A project focused on trivia. I would be happy to lead this project.
2. An Animal Crossing Debate Club.
Thanks, --SunsetBay (Talk) 14:29, September 5, 2023 (EDT)
- Going to lean with the former not being necessary. Trivia as a whole is not an inherent requirement for pages to have, and in many instances (broadly across all wikis, not exclusively here), people get really obsessed with adding trivia points that would much better be served in main article sections like descriptions or are so vague or stretches that they aren't inherently useful—I'd be concerned a project like that would encourage something like that. If the project was to perhaps update and consolidate or re-integrate trivia, I would be more on board.
- The idea of a debate club is cool, but it's not really what a wiki is for. Furthermore, the format of a wiki isn't terribly constructive for a rapid-fire debate club style of writing/conversation. I would suggest joining an Animal Crossing discord (or making your own) for something like this.
- These are just my opinions on the matter, hope it helps. Trig - 02:28, September 28, 2023 (EDT)
Discussing our proposal system
I'm starting to think non-Trustees shouldn't make proposals here. While so far we only had FroggyPotter's recent proposal asking for "one staff to be active at all time", I get this feeling that users not acquainted with policy-making will go to the proposal system for something that isn't a change affecting "a large number of pages or users".
What do you think? Should we limit the creation of proposal to only Trustees or not? -- PanchamBro (talk • contributions) 16:32, September 5, 2023 (EDT)
Comment I probably wouldn't support going that far; I think everyone should have a chance to submit their ideas as a proposal. We could limit to autoconfirmed, but that wouldn't help much.
- I do, however, think there should be an ability for admins to veto proposals that are clearly unnecessary or relate to how the staff operate, like there is on MarioWiki. FroggyPotter's proposal would fall into the latter category. Drago (talk)
10:46, September 6, 2023 (EDT)
- I dig an ability to veto a proposal that is unnecessary or is in regards to staff and all. -- PanchamBro (talk • contributions) 16:32, September 7, 2023 (EDT)
- When overhauling Inkipedia's proposal system recently, we introduced a veto that would require three administrators to veto a proposal in a publicly listed third vote in order to shut things down. Not saying this is better or worse than the above listed, just that it is another option. Trig - 02:28, September 28, 2023 (EDT)
Comment Agree with Drago on both points. Chubby Bub (talk) 21:00, September 6, 2023 (EDT)
Translating the wiki
I would like to translate the wiki to Italian. Does anyone know if I have to get permission or if there's a way to add new languages to pages? Edit: I see both the Spanish and German version have gone separate ways but I was aiming to just add something to Nookipedia itself. FUGOSHROOM (talk) 15:20, October 14, 2023 (EDT)FUGOSHROOM