Mabinogi World Wiki is brought to you by Coty C., 808idiotz, our other patrons, and contributors like you!!
Want to make the wiki better? Contribute towards getting larger projects done on our Patreon!

Please learn how the wiki works.

Fragment of a discussion from User talk:Kapra

Both of you stop the reversion war already.

The real issue here is that the page is way too big with or without commas. It should be split into multiple pages.

Commas are more readable, so commas are definitely preferred.

Kadalyn (talk)01:35, 10 May 2015

The page had commas before, that's not the issue.

Splitting the page into multiple pages does not help in the aim to reduce the page sizes (unless you don't intend on re-including those new subpages into the main page) so that the Hero Talent Tables can be included in the Talents page.

MRTFlippy (talk)01:40, 10 May 2015

The commas seem to be Kapra's issue? The diff shows that basically the only difference is 3000 commas.

I don't think all the tables should be included on any one page at all, they're way too big and the processing time for that page is ridiculous.

I'm not sure how to best handle it though. I would like a more dataless summary of talents with links to talent-specific pages that contain those tables and such, personally.

Kadalyn (talk)01:47, 10 May 2015

I did start a discussion but no one seems interested in talking.

Your friendly Server Status Script admin, Xcelled19401:49, 10 May 2015
 
 

The page before had {{formatnum: . . . }}. Converting it to commas shows no visual difference and actually increases the file size, from what I've gathered.

I approve of the changes Flippy has made to the Hero Talent page, though. But I still think he should consult the talk page before doing such a thing.

Kapra - (Talk)02:22, 10 May 2015

Flippy, some of the changes you just made to the homestead template were good, but moving the event checker to the |- broke it, look at the homestead animals section on the homestead page.

Kapra - (Talk)02:25, 10 May 2015

I realized that, but I was too busy responding to this thread, which interrupt my fixing of the change.

MRTFlippy (talk)02:30, 10 May 2015
 
Scenario 1
{{template}} expands into -> ...(shit ton of content)...
Replace template with actual content of template -> increases page code length, but no change to page file size
Scenario 2
{{formatnum}} expands into -> ...(shit ton of formatting code)...
Replace formatnum with a single comma -> decreases page code length ({{formatnum}} -> ,), but big change to page file size (...(shit ton of formatting code)... -> ,)
Scenario 3
The same as scenario 2, except you're adding thousands of commas, and removing multiple formatnums
...(shit ton of formatting code × however many times it's in there)... > , × however many times it's in there
MRTFlippy (talk)02:30, 10 May 2015