User:Ciovala/Sandbox
User:Ciovala/Sandbox2 Testing a query. 1...2...3
Contents |
[edit] Terminus Quests
[edit] Guardians Quests
Limit to avoid long lists, and link to the full list with 50 elements per page.
SMW offers Concept pages. They look very much like category pages, but display the result of a semantic query. Examples are Concept:Guardian Quests and Concept:Defiant Quests. Concepts don't show any other information apart from the page name.
[edit] Quest list per NPC
Testing some queries to replace the hard-coded list of quests in the NPC template. The default appears if no quests were found, intro is prepended if the list is not empty.
[edit] Quests of Sylver Valis
Name is involved in the following quests.[edit] Quests of Little Lord Fauntleroy
Name is not involved in any quests.
[edit] Problems with involved NPCs
One problem might be to distinguish between "xx is involved" and "xx gives the quest". If NPC A gives a quest which says "talk to NPC B", then this quest will also show up in the list of quests of B (which might or might not be desired). Maybe a special property "Issued by" used once on every quest page? Is it possible to stack properties as in [[Provided by::Name::Some NPC]]?
edit: YES! [1]
It would then be possible to have
- "this NPC offers the following quests" by
-
{{#ask: [[Quest:+]] [[Provided by::XXX]]}}
-
- "this NPC is additionally involved in those quests" (excluding the former) by
-
{{#ask: [[Quest:+]] [[Name::XXX]] [[Provided by::!XXX]]}}
-
- the name of the issuer can be added to the table of quests per location
[edit] Quest dependency
Also a "Requires" property can be added. Quest X [[Requires::Quest:Y]] which is directly used for the list of required quests on Quest:X. The list of back-references for quests depending on Quest:Y however is automatically generated with {{#ask:[[Requires::Quest:Y]]}} (which reduces the manual management effort of maintaining and synchronizing both lists).
This can also be used for recipes requiring components. --Mardur 08:58, 3 February 2011 (CST)