Template talk:Quest

Flagging
This could use a Flagging item. Hoopy Froodle (Contribs • Message • Email ) 21:45, January 23, 2017 (EST)
 * Bump. Flagging parameter still isn't present in the template. Quests with flagging have it, DPL for flagging uses it. The template itself ignores it and doesn't have it documented. &rArr; Faltout (Contribs • Message • Email ) 11:51, April 1, 2018 (EDT)
 * Working as currently intended. Flagging has always gone in the Overview section.  The Flagging parameter is used on some pages to offer a possibly abbreviated version to DPL queries that make use of it and should not replace typing out the full flagging routine on the quest page itself as a subsection of the overview.  If you'd like to change how it's intended to work, feel free to start a discussion on it.  Thanks.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 04:15, April 3, 2018 (EDT)

"Needs to have Parameters updated due to change..."
Kobold Sneak keeps adding this after updating quests to include the bonuses, what "parameters" exactly need updating on all of these? - LrdSlvrhnd (Contribs • Message • Email ) 13:04, June 12, 2017 (EDT)
 * Replace obj with objective_1 through objective_### as a list of in-quest objectives
 * Optionals should be indicated as such with optional_1 through optional_### instead of being grouped into the old obj
 * opt_percent_1 through opt_percent_### should be indicated for completing the corresponding optional_### We are no longer using Calculated XP bonus directly on quest pages.
 * monsters has been deprecated and should no longer be included on the page.
 * External links to YouTube videos or forum posts etc should use corresponding OnYouTube or Forums etc templates in a new external links section.
 * All XP bonuses should now use the following parameters directly in the quest template instead of how we use to do it with k1-3:
 * insidious cunning bonus
 * devious bonus
 * discreet bonus
 * aggression bonus
 * onslaught bonus
 * conquest bonus
 * tamper bonus
 * neutralization bonus
 * ingenious debilitation bonus
 * observance bonus
 * perception bonus
 * vigilant sight bonus
 * mischief bonus
 * vandal bonus
 * ransack bonus
 * bonus_xp_notes list any notes about hitting XP bonuses here.
 * I'll be uploading a DDOwiki talk that goes over all of it in the next day or two. :) ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email ) 18:44, June 12, 2017 (EDT)
 * OK, the XP bonuses are great, but the objectives and optionals 1-XXX seem a bit way-the-heck-over-the-top, IMHO. Why not just keep with the asterisks on a new line? This seems to be needlessly complicated to me. - LrdSlvrhnd (Contribs • Message • Email ) 19:15, June 12, 2017 (EDT)
 * The optionals don't all give the same % bonus of XP, so they need to each have their own line. It's an overall improvement in the appearance (has a much better looking result at the end and uses a lot less bits per page).  ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email ) 21:23, June 12, 2017 (EDT)

Okay, so I got the episode uploaded to YouTube:

I hope this, starting at 25m2s, helps explain it all. ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email ) 10:39, June 13, 2017 (EDT)

Bonus XP Notes
This really should go on its own (preferably indented) line, rather than just tacked on to the end of the final XP bonus. See Ruined Halls - I had to add a couple of asterisks to make it look like that. - LrdSlvrhnd (Contribs • Message • Email ) 12:15, June 20, 2017 (EDT)
 * ✅ &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 12:49, June 20, 2017 (EDT)
 * Looks good, thanks! - LrdSlvrhnd (Contribs • Message • Email ) 17:56, June 20, 2017 (EDT)

Optional XP
Can we get this set off from the objective more distinctly? "(Optional) Kill the Ogre Shaman who has allied with the Hobgoblin raiders Heroic: +10% Bonus." just looks shabby. As an aside, I like how the "(Optional)" part looks on the actual page. Perhaps doing the same thing for the "Heroic: +10% Bonus" would work? - LrdSlvrhnd (Contribs • Message • Email ) 00:08, June 30, 2017 (EDT) I'm working on this now!!! DDOstream (Contribs • Message • Email ) 08:54, October 10, 2017 (EDT) XP: Heroic &#9827;800 &#9830;1,200 &#9829;1,400 &#9824;1,700  / Epic &#9827;2,800 &#9830;3,200 &#9829;3,400 &#9824;3,700    &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 12:38, November 26, 2017 (EST)
 * I read this a few times now, and I'm still not sure I understand what you want. I'm planning on getting rid of the Heroic/Epic heading for XP all together since the percent bonus should be the same for both across the board.  How will that affect your request?  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 22:29, July 8, 2017 (EDT)
 * I still think the "+X% Bonus" should be different. Italicized, or italicized/greyed to look the same way as "Optional" at the beginning of the line, or something.  It's just that right now it looks like the text says "(Optional) blah blah blah Heroic: 10% Bonus".  And "(Optional) blah blah blah 10% Bonus" would just look better, IMHO.  I know we had a similar discussion back with the old style about making the bonus distinct from the actual text, and I forget what we settled on looks-wise. - LrdSlvrhnd (Contribs • Message • Email ) 22:45, July 8, 2017 (EDT)
 * It's in a collapsed section at Ut:Technical 13/2015/3, and yes, I'll be formatting it per whatever the consensus was there when I get to the formatting stage of the revamp. I currently am just trying to get all the functionality worked out how everyone likes first.   &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 10:45, July 9, 2017 (EDT)
 * Cool, thanks! - LrdSlvrhnd (Contribs • Message • Email ) 16:01, July 9, 2017 (EDT)
 * I'll be working on this for the next episode of DDOwiki talk (October 3rd). That will have given everyone three whole months to throw feedback, ideas, suggestions at me.  Feel free to tune in on  hosting my personal  for the stream - you can even pop in on the  - and give feedback to help shape it in a way that pleases your eyes. :) DDOstream (Contribs • Message • Email ) 09:05, September 19, 2017 (EDT)
 * Ah-ha! This is what I was going to work on Tuesday... I couldn't remember what I said I was going to do and didn't come across it doing my normal run through the S:RC list.  I'll try to remember the 10th... :)  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 21:34, October 5, 2017 (EDT)
 * Made the modifications noted in the discussion on my talk page. Still doesn't seem to be rendering the way I expect, but maybe I'm just too tired (I'm 25 hours into a 36 hour livestream at the moment.) DDOstream (Contribs • Message • Email ) 09:10, October 10, 2017 (EDT)
 * Query: Do we really need "Heroic" and "Epic"? I mean, are there any cases where the percentage is different?  If you look at Fathom the Depths, for instance, it says "(Optional) Free the Raveneye captives before lowering the barriers (7 total) Heroic: (+20% Bonus.) Epic: (+20% Bonus.)"  Now, the "(+20% Bonus)" looks good, but the "blah blah blah objective blah blah Heroic" part looks shabby, and I really don't think that we need 1) the distinction between heroic & epic, or 2) the words "Heroic" or "Epic" to be in there.  Just "(Optional) Free the Raveneye captives before lowering the barriers (7 total) (+20% Bonus.). - LrdSlvrhnd (Contribs • Message • Email ) 21:29, October 11, 2017 (EDT)
 * I can add some logic later that will compare the two percentages and if they are equal, eliminate the redundant text. That will take a bit of work, so it probably won't be on wiki talk this week. DDOstream (Contribs • Message • Email ) 08:15, October 17, 2017 (EDT)
 * Okay, so I looked at this and I don't really understand the request. The input is opt_percent_# which is the same for both heroic and epic.  The reason both texts are there is because the base for heroic and epic is different, not the percent.  I'm thinking that the resulting text should read something like:

Quest Failure
We need a "quest failure" parameter. I just updated The Faithful Departed, but... there's no failure parameter. So I did "|failure = " for it, in hopes that somebody who can actually do these things will make it. And if you use something other than "|failure = ", make sure to change that quest, please! - LrdSlvrhnd (Contribs • Message • Email ) 21:47, July 8, 2017 (EDT) Since we got the failure parameter, now we need more of them. The_Weapons_Shipment has 2 failure cases. Actually, I think the best way to do it is to add _failure to the objectives. If an objective contains a failure case or not completing it means quest failure, then you could tag that objective as objective_##_failure. Then, you can check objIndex for failure cases. &rArr; Faltout (Contribs • Message • Email ) 05:47, January 16, 2018 (EST)
 * You mean as an objective option? Like " Break no more than 10 sarcophagi"?  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 21:55, July 8, 2017 (EDT)
 * Exactly. I mean, it could probably be done as a regular objective, but if we're gonna have all the rest of them... why not, right? *g*  - LrdSlvrhnd (Contribs • Message • Email ) 22:09, July 8, 2017 (EDT)
 * ✅ &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 22:24, July 8, 2017 (EDT)
 * Thanks! Now can you do something about the above-listed optional? *g* - LrdSlvrhnd (Contribs • Message • Email ) 22:25, July 8, 2017 (EDT)
 * Sure. I can update it to be obj_failure_## and let it be a boolean value of true/false &rArr; DDOstream (Contribs • Message • Email ) 08:30, January 16, 2018 (EST)
 * ✅ and backwards compatible for now. Please update quests in . &rArr; DDOstream (Contribs • Message • Email ) 09:25, January 16, 2018 (EST)
 * No reason to add more parameters. Some of the quest objectives can contain failure clauses. What we need is a way to determine which ones contain that and which ones don't. So, we could replace the failure with objective_##_failure. This way, the code  will loop through both the normal objectives AND through the failure objectives. Except the failure objectives would have   in   which we can detect with  . With this solution, we also get the failure objectives to appear in the middle of the normal objectives instead of at the end (where they may be irrelevant). Check T:Quest/sandbox when applied to The Weapons Shipment. &rArr; Faltout (Contribs • Message • Email ) 09:29, January 16, 2018 (EST)
 * failure was just deprecated on live stream. What you want to do is already done, you just didn't use the parameter as indicated.  Also, with the way   reads things, your way would not work as you think it would. &rArr; DDOstream (Contribs • Message • Email ) 09:39, January 16, 2018 (EST)
 * Actually, it already did work. You just didn't see T:Quest/sandbox applied to The Weapons Shipment (I was watching the stream at that moment). Anyway, both ways are basically the same with slight differences so I can consider it fixed. &rArr; Faltout (Contribs • Message • Email ) 10:14, January 16, 2018 (EST)

Extra newline in objectives when there are no optionals
✅ &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 04:10, April 3, 2018 (EDT)
 * The "fix" fixed the updated quests and broke all the non-updated quests. The Deadly Package: The Stronghold Key (note: the sandbox2 fix is still correct for both) &rArr; Faltout (Contribs • Message • Email ) 06:08, April 4, 2018 (EDT)

This can be viewed in quests such as The Friar's Niece. I think this can be fixed with a nowiki tag as in Template:Quest/sandbox2. I tested it for the 5 unique situations I could think of:

1. objective_# (quest updated to new template format) with no optionals (such as Endgame: The Archbishop's Fate)

2. objective_# (quest updated to new template format) with optionals (such as The Old Archives)

3. obj (quest NOT updated to new template format) with no optionals (such as Protect Baudry's Interests)

4. obj (quest NOT updated to new template format) with optionals (such as The Depths of Despair)

5. no objectives or optionals (such as To_Find_a_Witness:_Archbishop_Dryden)

I also made sure that I tested each of the 5 cases for when the expect parameter was present or missing and it worked in all 10 trials. Is this a valid fix? Kkoliver (Contribs • Message • Email ) 09:42, September 14, 2017 (EDT)
 * Bump. Extra newline still plagues the quest pages despite there being a fix. If you're gonna admin protect all the templates that do something, at least be there to update them. &rArr; Faltout (Contribs • Message • Email ) 11:54, April 1, 2018 (EDT)
 * Go ahead and fix it if you like, there's nothing stopping you from editing any page on the wiki. I don't know of any sandbox pages that are protected.  Get it working how you think it should work, and put in a request - Should make sure to sync the live template with whatever sandbox page you want first to make sure they can be merged easily.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 04:07, April 3, 2018 (EDT)

Bestower
There is an incosistency with the bestower. While the npc contact has a link, the bestower does not. Change to: | bestower = &rArr; Faltout (Contribs • Message • Email ) 18:36, January 10, 2018 (EST)
 * IIRC... It was intentionally left non-linked because not all quests are bestowed by an NPC and the ones that are "walk ups" or bestowed from an item in your inventory or a sign-post caused all kinds of annoying issues when linked like that. &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 22:54, January 10, 2018 (EST)
 * If you can point me in the direction of the ones that are causing the trouble I'll be happy to fix them. I corrected all the Twelve patron quests and intend to edit all the quests adding the "bestower" field and will keep correcting the other quests with their correct bestower (most of them have this field blank leading to erroneous information displayed). I'll be removing any links from the bestower, so I'm suggesting you add them here. For example, Palace of Stone has had the bestower updated to Housewarming Invitation instead of Housewarming Invitation, so it needs the link back through the Quest template. &rArr; Faltout (Contribs • Message • Email ) 06:16, January 11, 2018 (EST)
 * What about the case where there are multiple different people that can bestow the same quest? This happens for Tutorial: How to advance your character. Having the link on the template side in a simple way would not work unless the workaround I used for the npc field were used every time. &rArr; Kkoliver (Contribs • Message • Email ) 17:00, January 11, 2018 (EST)
 * This is a valid point too. There are a couple edge cases like this where it's really not worth the extra load on the server to update the template to accept multiple NPCs for one or two quests but you don't want those quests to be broken.  Another option is to use the Extra template for multiple NPCs, although it may need to be adjusted to work correctly for this use case.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 17:05, January 11, 2018 (EST)
 * To be fair, those quests should not use this template that adds them in several categories where they don't belong and tries to display information that is irrelevant to those quests (duration? free to play? extreme challenge? monsters?). I'll try to create a new template to use on them that gives them their proper categorization. &rArr; Faltout (Contribs • Message • Email ) 15:15, January 16, 2018 (EST)
 * I can get behind a new template for these type of "quests". My idea for adding them is because they show up in the journal and people that are completionists like me may want to clear every quest from their journal. Some of these non-quests that show up the journal are bugged or it is not clear how to complete them so I just figured I'd add them. The quest template didn't fit perfectly but I didn't know what else to use. There were a lot of these type of quests already on the wiki. (See Refugee Toll, The Rewards of Treachery, To Find a Witness: Archbishop Dryden, etc.) &rArr; Kkoliver (Contribs • Message • Email ) 15:31, January 16, 2018 (EST)
 * There are still quests, and as such should use the Quest template. I don't agree that the categorization is irrelevant although I could get behind a new parameter and additional category for "starter quests" or something of that nature to identify these quests are "special".  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 15:39, January 16, 2018 (EST)
 * I strongly disagree that they should use the Quest template. The template is extremelly cluttered as it is, adding special cases like that would only lead to more confusion, editing and miscategorized quests. This template is focused on quests that take place in a dungeon, have monsters, xp, rewards. The quests in question are tutorial quests, seasonal quests, chain quests, etc. A slayer quest in an explorer area does not use the quest template and it shouldn't. Neither should those quests. &rArr; Faltout (Contribs • Message • Email ) 15:59, January 16, 2018 (EST)
 * I do not know off the top of my head. I'd have to do a Special:Search for  I know there are a bunch in Gianthold and the desert, not sure where else.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 17:05, January 11, 2018 (EST)

questloc, adpack categorization
I have a couple of requests for this template. I have more modifications in mind, but those will do for now so I can start working on updating a bunch of pages with DPL. &rArr; Faltout (Contribs • Message • Email ) 07:48, April 26, 2018 (EDT)
 * Starting with questloc. First requested here (Template_talk:Quest/Archive01) but never implemented. This parameter should have at least 2 possible values because of 2 quests (Desert Caravan, Ritual Sacrifice) that can be accessed from 2 places. It should also be linked automatically by the template. Finally, quests should be categorized using this information (Quests in ) and categorization using zone should have a different name (Quests aqcuired in ).
 * All quests have had their adpack updated. I made sure of that. Now it is time for the template to start categorizing the quests to adventure packs ( quests). Also, do not add this categorization to the Adpack template or a whole bunch of irrelevant pages will be categorized as well.
 * I believe Into the Mists can also be entered from two places, House J and EStar; and the two free L15 Wheloon pre-quests can be entered from EStar or Wheloon (the third one that's part of the Shadowfell XPac can be picked up in EStar, but you have to go to Wheloon to enter, and a few others have alternative entrances but in the same zone, so I think these don't fit the parameters of this). But... where's the second entrance for RitSac?  I only know about the one from Vale along the ridge. &rArr; LrdSlvrhnd (Contribs • Message • Email ) 14:02, April 26, 2018 (EDT)
 * &rArr; Faltout (Contribs • Message • Email ) 23:14, April 26, 2018 (EDT)
 * Huh, weird, I've been annoyed by the "can't use this waypoint..." or whatever it is when you have both Shrouds active, never noticed an entry point for RitSac. &rArr; LrdSlvrhnd (Contribs • Message • Email ) 23:44, April 26, 2018 (EDT)


 * I added the dungeonentrance in Template:Quest/sandbox2 and Template:MissionInfoBox/sandbox2. It can accept multiple values separated by comma. For example (Desert Caravan): dungeonentrance=House Phiarlan,Zawabi's Refuge. Before deciding on the comma separation, I checked all the known zones for commas present in their name and didn't find any. Also added categorization for dungeonentrance ("Quests in "), for adpack (" quests") and changed the categorization of zone from " quests" to "Quests acquired in ". The new parameter "dungeonentrance" will be visible in the MissionInfoBox (testcase1). I await for the code review and discussion. Note that the testcase doesn't have any categories because then it would appear in quest tables. To see if categorization works, remove the DPL section at the top of the testcase page and preview. The categories should be visible at the bottom. &rArr; Faltout (Contribs • Message • Email ) 15:15, July 14, 2018 (EDT)
 * Made the zone parameter also accept comma-separated values. &rArr; Faltout (Contribs • Message • Email ) 01:58, July 20, 2018 (EDT)

Quests sharing favour but with different names
Relevant to quests such as Madstone Crater (Heroic)/Return to Madstone Crater (Epic)

The following 2 parameters are intended for the level of the quest: | level           = | epic            = Problem 1: As the quests have different names, filling both entries in means both quests are listed at both Epic and Heroic Levels

Problem 2: If the entry is left blank, an end user of the wiki is not informed about the epic version when the look at the level list of the heroic version and vice versa

Currently: | level           = Accepts Numbers and Text allowing placement of link in Epic Quest back to Heroic Version | epic            = Accepts Numbers only, preventing placement of link in Heroic Quest back to Epic Version Problem: "Category:Compendium:Level {}" automatically creates a link if the field is populated, whether by a number or text

Additionally: | Shares Favor    = Parameter exists (and is theoretically useful) but does not display in info box for quest

Solution:

Update "epic" to allow Text as well as numbers

Update "Category:Compendium:Level {}" to so it is only cross-referenced/populated if "epic" or "level" contain numerical values

Add "Shares Favor" to Template:Quest and display it in info box below "Favor"

End Result:

Any wiki users can see clearly that there is an epic version of the heroic quest (and vice versa) automatically, no matter where they look.

Incorrect assumptions about favour not being shared due to difference in name and each quest saying Heroic: None" or "Epic: None" cannot be made.

The important thing with the wiki is that relevant information is visible to users where they would expect to see it, which the current set up does not allow for.
 * My proposal is to use the shares favor (which I recently added to some quests for future use from my templates) to indicate that the quest has a heroic/epic counterpart. If level is empty or not defined and shares favor is non-empty, then display "Heroic Level: " . Same for epic. If epic is empty or not defined and shares favor is non-empty, then display "Epic Level: " . It won't display the actual level of the heroic/epic counterpart, but I think it's a good compromise, don't you agree?.
 * (Instead of "Heroic Level:" you can display "Heroic counterpart:")
 * (If you want to display the level as well, you can add another parameter similar to "shares favor" with the other level OR you can get it automatically via DPL)
 * &rArr; Faltout (Contribs • Message • Email ) 11:08, April 28, 2018 (EDT)

As long as something rather than "None" gets displayed against Heroic and Epic Levels in these scenarios, it's good. Autopopulation of xp / level and epicxp / epic when they are unpopulated/not present and shares favor is populated definitely would save manual effort, while still providing the relevant information to people in the relevant places and avoiding cross-reference issues.-- &rArr; Glmfw1 (Contribs • Message • Email ) 12:12, April 28, 2018 (EDT)

I updated Template:Quest/sandbox and Template:MissionInfoBox/sandbox with the shares favor parameter and it will not show the name of the epic/heroic counterpart at the Heroic level or Epic level rows instead of a purple "None". Now someone with access to the template code should update the template. Do we want the level and/or the xp of the other quest displayed? &rArr; Faltout (Contribs • Message • Email ) 14:36, May 25, 2018 (EDT)
 * Bump. It's been almost 2 weeks. Can someone review and apply the changes please? &rArr; Faltout (Contribs • Message • Email ) 08:10, June 5, 2018 (EDT)
 * Bump #2. It's now been 1 month. If the administrators don't do their job of reviewing requested changes for protected pages then perhaps they should either recruit more administrators to do this job or unprotect the pages. This is my last bump on this talk page. Next move will be to edit the quest pages to use the unprotected and updated template in the sandbox. &rArr; Faltout (Contribs • Message • Email ) 12:53, June 27, 2018 (EDT)
 * (at least for now) After your last edit request needed to be reverted, I'm hesitant to make other edits on your behalf without multiple tried and proven test cases showing things won't break. I personally haven't acted on this request as I have not seen any convincing support for the change.  The only comment I see is someone who thinks something is better than "none", and I believe sometimes "none" is appropriate.  Threatening to cause mass disruption usually won't get you what you want, but may get you blocked and banned.   &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 01:09, June 28, 2018 (EDT)
 * There IS a way to test the changes I've made. Go to the quest pages described above, apply the MissionInfoBox/sandbox template, hit preview and see if it's broken. Or apply the changes, go to a bunch of quest pages and see if it's broken. Then revert. I can't do the tests for you (without creating a bunch of useless sandbox pages). If "reviewing" the changes shows an error, then you don't apply the changes. That's what the "reviewing the changes" means. I wouldn't have seen that the last edit request wasn't perfect without widespread application. In any case, at least now there is a response to the request. If admins don't do what they advertise their job to be, then the wiki doesn't work is all I'm saying. &rArr; Faltout (Contribs • Message • Email ) 01:28, June 28, 2018 (EDT)
 * Don't you worry about "useless sandbox pages", we can always delete them later. Please place Template testcase TOC at the top of each to ease navigation.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 01:38, June 28, 2018 (EDT)
 * Sure, it's not like you were arguing that nothing gets deleted in the wiki and that the wiki has very finite resourses not long ago in JJMC89's talk page. In any case, I don't know how to use the above template and there isn't any USAGE info on the template page. &rArr; Faltout (Contribs • Message • Email ) 01:52, June 28, 2018 (EDT)
 * This seems like a reasonable request and implementation. The change to this template is trivial, and the change to MissionInfoBox is straightforward. —&thinsp; Zav &thinsp; (T·C) 02:37, June 28, 2018 (EDT)
 * was straightforward and trivial too until it had to be because it was badly broken.  A few testcases pages to make sure that's not going to happen again doesn't seem like an unreasonable request and a couple testcases pages will use a lot less space than having to revert template parameter changes to a few hundred pages.  I have to seriously question the ability of an editor to make edits to complex templates when they have to ask how to use a template such as Template testcase TOC; especially when I already said how to use it:    &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message<span class="emailLink emailTechnical_13">&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 11:55, June 28, 2018 (EDT)
 * Testcase pasted. You must have the impression that changes to every quest page are needed. If you read the start of this topic carefully, you'll find out that the relevant parameters are already in place where needed. &rArr; Faltout (Contribs • Message • Email ) 15:17, June 28, 2018 (EDT)