User talk:Corgrind

Talk

Discussion on quest list project and coding
Hello and welcome to the wiki. First of all, let me tell you I like the standards you've set for coding very much and I've tried to apply them in my coding as well. Of course there is a tradeoff to by had and I wanted to let you know before you get too far in. Reusable code and code which separates functions is great in programming because it allows for the creation of complex things by combining the various parts. However, when calling procedures/functions there is a small overhead to generate the stack entry for each function and pass the parameters. Similarly, the wiki parser tells us that there are costs associated with transcluding templates and it has limits on transclusion depth, transcluded size and also doesn't allow recursion. Considering you want to create a quest list template, you should also know that loops have a maximum number of loops and dpl has a maximum number of results. I mention those because I've ran into those issues before and had to make a choice of creating a specialized template with not much reusability or pay the cost of time and server power when loading the page.

With that said, what exactly do you want to achieve by creating a quest list with names instead of categories? We already have so many quest list templates and one of my projects was to eliminate most of them but I've ran into the trouble of admin protected templates and an admin that mostly breaks stuff instead of fixing it. My main question is "Which page do you want to use that quest list?" If it is the adventure pack pages, then the solution would be to properly categorize the quests belonging to that adventure pack and then grab them from that category. Right now the categorization is broken (by the aforementioned admin) because everything is categorized the same way " / / quests". If you want to address that situation, I would contact one of the administrators that is not. Like or  to make the changes proposed to Template:Quest mentioned in Template talk:Quest.

"When I think code is too unreadable I may add the "unfolded" code to the talk page". You can use comments to add line breaks and make the code readable. You can have a look at how I approached this problem in Template:Quest table row meta or basically any of the templates I have created. Start a comment at the end of the code line and end it before your next code line.

&rArr; Faltout (Contribs • Message • Email ) 18:52, February 8, 2021 (EST)