User talk:Poopmcpoop

Reply

We don't chat here. We chat in the wiki-discuss channel on the discord. Elsewise we might not see a discussion was even made, for example I didn't see the one that was originally on that page from over a year ago. And I blanked it to avoid confusion.

As for the part on the plural issue:
"but that fails to address the underlying issue in Template:InfoItem that programmatically causes the issue across the wiki. " The issue is that Lava will pluralize some thing, then not others, then on the wiki we have something in plural form, while not others, or some things that aren't even on their own pages anyway and would still require a redirect.

If you have a solution that doesn't require us to 'manually "correct" this behaviour' and accounts for more than just the InfoItem template, because it affects more than just that and the pluralizer template fyi, then I'm happy to hear it. I made that solution to a problem a while ago, and it ended up having its own issues that I, and so far no one else, has had the time to find a solution for other than a 'manual fix' by creating redirects. Plus, this wiki gets redirects added all the time even just because someone is too lazy to search for something like "Gold ore" instead of "Gold" (Just an example, Don't know if that is actually one of the redirects, but there have been a number created for that reason).

The plural form redirects also help those who would use the wiki bot on the discord but wouldn't know, for example, that they had to search for EXP Balloon instead of EXP Balloons, Exp Balloon, or Exp Balloons. I specifically included those last two because even in your post in the discussion you used the lower case form despite EXP being an abbreviation which traditionally should be all caps.

But for real, come chat on the wiki-discuss channel. We always welcome people who are interested in updating the wiki, and who knows, maybe you will solve this problem we've had for a long time since, despite all of what I said above, I actually abhore redirects.

@Kiokurashi Template:Pluralizer has decent logic and is applied to Template:InfoItem. In fact, it works, and did previously work, for all those three types/pages you made manual redirects for ("EXP Balloon" -> EXP Balloons had been hardcoded in as an exception). That is the purpose of templates: to provide programmatic wiki-wide solutions reducing work load and standardising higher quality content. The issue, much like I originally stated on the talk page you blanked, is relatively simple, and has to do with mediawiki syntax: the pluralizer is, and was, correctly applied to the type format in the infobox, but not to its accompanying wikilink.

The purpose of talk pages is to provide a platform for conversation/context directly tied to specific topics, available to everyone without being restricted to 3rd party closed source platforms such as Discord. Had you found it beneficial, you might have linked it elsewhere to discuss it as you saw fit--or not. Not everyone has to be aware of every talk page, but blanking an unsolved issue is a sure way to reduce awareness to it. I understand that you prefer instant messaging platforms, but I assure you, each come with their own drawbacks and I specifically chose this platform for the purpose it was designed for. It was disrespectful and inconsiderate of you to make such a rash decision to literally trash another editor's input for improving this wiki.

I didn't lament redirects or your use of them. I find them suitable and beneficial in many cases. However, your redirecting all three arbitrary examples of issues resulting from a relatively simple mistake on a single line of a template and blanking my detailed account of said issue, did indicate that you found the issue solved by doing so. Redirect all you want or need. I will too. I am personally quite fond of redirects. - Poopmcpoop (talk) 21:11, 12 April 2024 (UTC)

@Poopmcpoop We did used to have the pluralizer in the link part which actually would have even more issues than just needing to do a handful of redirects. Honestly, the best solution would be to use something like CirrusSearch to be able to index things and use that instead. Unfortunately, our host doesn't let us use it because it requires a script or something in the backend that they said we can't use because it's a vm farm. Regardless, unless a solution is found, the discussion post will remain.