| abstract
| - I think the most interesting output of this project would be a list of NPCs which have a quest mark, but no known quest involvement. Would be easiest if this could be DPL generated, so the bubble parameter should add a category to the NPC like "NPC involved in a quest" and maybe a quest parameter should be added to NPCs a well? Or the notes parameter must be searched with a regular expression for the keyword "quest". -- Bennie (talk ~ fellows) 11:07, March 8, 2014 (UTC) I agree the NPC template should add categories based on the icon. I was thinking something like Category:NPCs with Trade Icon Category:NPCs with Quest Icon I think "NPC involved in a quest" is misleading because we cannot prove they are involved with quests, it may actually be a bug or something we don't consider to be a quest. About quests parameter: I used to advocate this but I don't think it's worth it anymore. It would involve editing all NPCs and unnecessarily separate the notes from the spoiler. If it's applied to npcs then for consistency we'd want it for items and objects and everything else, and there we have 4000 articles to edit. It's easier to just have that information in the notes. Besides, if there's very few uses of this then those specific tasks can be done manually. If is adopted we could use this to our advantage as well, because DPL can filter based on templates not used (notuses). -- Sixorish (talk) 13:06, March 8, 2014 (UTC) Ok, your category argument makes sense. I'm also not convinced CIP implemented this change without a single error, but hopefully they will fix any errors in the near future. I also agree we should refrain from projects which require mass-editing, if possible. Could SixBot replace all spoiler tag instances with JSpoiler? Seems like a simple search-and-replace operation to me. Does JSpoiler have functionality to be less than 100% wide, or is still necessary? I would be in favor to apply JSpoiler to a small test batch (like 100 pages) first, before replacing all spoiler tags altogether. This way we can monitor unexpected behaviour more easy. -- Bennie (talk ~ fellows) 14:04, March 8, 2014 (UTC) At the moment, no the JSpoiler doesn't allow custom styles but since it's a template we could easily add support for it as needed. FixSpoiler's overflow: auto is in the CSS so we shouldn't need to use this. This is just one example of how JSpoiler is better: we can actually change this instantly if we need to; the FixSpoiler is not a workaround, it's the solution and we have no option but to use it as a workaround. I will set up SixBot to do this task but it will take some time. -- Sixorish (talk) 12:03, March 9, 2014 (UTC) It is highly unlikely that Cip manually added every NPC to a list to show the bubbles. They probably used existing flags, for example the Trade bubble shows if NPC can do a standard "trade" as well as special item trades. Quest bubbles are likely based on a quest flag, especially considering the update a few years back which at least let players know something changed by seeing "Your quest log was updated". With this in mind i should think that all NPCs with Trade and/or Quest bubbles are correct and perhaps only some NPCs are missing them because they do not have a related trade or quest flag. I suspect this change is a partial response from Cip to the player request for knowledge about solvable quests, thinking of the recent article "The Secret of Secrets" and forum discussion, as this can hopefully let as identify NPCs as involved in a Quest were there previously was doubt. --DM ><((°> Contribs <°))>< talk to me 21:24, March 9, 2014 (UTC)
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)