Mabinogi World Wiki is brought to you by Coty C., 808idiotz, our other patrons, and contributors like you!!
Keep this wiki going by contributing to our Patreon!
Please revert this.
I'll answer to the inquiries one point at the time.
- Pages: the current way to list iterations is slated to be replaced with a better method on individual monster pages.
- Not putting in information properly: As of now, the focus is to simply switch what information the wiki already has recorded over. Were I to also put in drop research and information, this already-snail-paced conversion would take much longer. Things like leather drops are also completely skewed from the Ingredient Hunting skill.
- 'Boar' linking to its G19 iteration page: the only 'Boar' monster in the game named as such is, indeed, the g19 Boar.
- Shadow Mission/Field Monsters: As a rule of thumb, Shadow mission monsters are always the same through the missions, until they are not.
- Field does really just mean 'field monsters'.
As this is (for now) essentially a one-man project, the switch will take time and I do not deny it has kinks to smooth over. If you wish to help, you know where to reach me. For the time being, I am not going to touch things until the holidays.
Okay, I'm just going to say this outright, you're setting yourself up for a LOT of additional workload. If you haven't completely figured out the design concept, it should not be changed in the midst of trying to plan for it. As someone who actually does software and web development, this creates way too much extra work. It's hard enough working with some of the wiki syntax without spending time learning it which frankly I'm pretty much done trying to do, because there have been several instances for example of people doing training requirements, but making three separate ways to display the information that achieves the exact same goal.
But if you want my advice, it should be as easy as "I searched this thing, if it has a variation on it, let the UI handle helping with additional information, otherwise make a dedicated page". Essentially meaning the page should either be exactly what we're looking for, or otherwise leading the end user to a page that helps them find what they want, or adding even parentheses to indicate what it is or is a variant of.
The old tables were designed specifically to have all information about a particular enemy in one area where you could see everything, every variation of their difficulty, and then they would have family pages that would sort them out based on where they are. That's why Rydian and previous wiki editors followed that format, because it had an easy to follow, structured flow.
As far as the boars go, they do not spawn in ANY Tara shadow mission, and I don't believe they spawn in any shadow missions in Taillteann either, unless you're targeting specific quests that are considered a shadow mission for something like a gen, and if that's the case (not exclusively to this), just redirect it to some kind of categorical page, or put it in a monster family page.
The goal is to make it easy for the end user to find what they need. But I'm telling you that having to click to extra pages is to put it bluntly, a bad design concept. Monster enemy data should not be on a separate page just because its original page is dedicated to some kind of lore background or whatever. You can code in sections and it will easily identify to the user what they are for.
Take the page on Giga Glas for example, it's great that it explains what it does, but to have the Battle AI and Tips, and then its actual datasheet on a separate page is counter-intuitive. If you look at Shadow Lancer however (which btw, please do not edit in the format you've been doing, its fine the way it is), it displays all the information you could ever need about that enemy and puts it all under one umbrella page.
I'm already dedicating my time to coding something proprietary and it's eating up all of my time, so having to fix stuff on the wiki isn't really in the cards for me. I'm hoping this helps. At the end of the day, please just think about the end-user. Make their search easier, not harder.