User:©TriMoon™/Sandbox

Infobox

{{infobox}}:

Template:Infobox/debugTheme	Template:Infobox/debugTheme
Template:Infobox/debugTheme	Template:Infobox/debugTheme

Semantics use

Lets try to describe properties of Objects using their placement in the game-menus to aid in later auto-categorization....

See Property:IsinGameMenu for current menu-names.

fe. Blazing Brazier, would need:

• isGameMenu=n
• isinGameMenu=Claims & Defenses

See these pages for documentation

• Help:Selecting pages
• Help:Displaying information
• Help:Inline queries (Parser function #show)
• Extension:StringFunctions (#explode:)
• List the set of unique values for a property
• Multiple values for the same field

---

Property settings

• isGameMenu=n
• isinGameMenu=Test
• String=Board;6
• String=Wooden Plugs;4
• String=Nails;2
• RequiresObj=Anvil
• RequiresObj=Flint;1
• RequiresObj=Stone;3
• RequiresObj=Board;10
• RequiresObj=Nails;4
• RequiresObj=Lime;15;Startpost
• RequiresObj=Flint;15;Startpost
• RequiresObj=Stone;30;Startpost
• RequiresObj=Lime;8;Cornerpost
• RequiresObj=Flint;8;Cornerpost
• RequiresObj=Stone;15;Cornerpost

Querries

1. {{List MenuEntries|menu=Test}}
   no Non-menu entries found.
2. ---{{#show: {{FULLPAGENAME}} |?IsinGameMenu}}---
   ------
3. Listing values for Property:RequiresObj on current page
   1. {{#show: {{FULLPAGENAME}} |?RequiresObj |link=none |sep=<br/> }}
      
   2. {{#ask: [[{{FULLPAGENAME}}]] [[RequiresObj::+]] | ?RequiresObj= |link=none |sep=<br/> }}
      
   3. Automatic listing in mind: {{PropVals |prop=RequiresObj |page={{PAGENAME}}}}
      (example property-data using Stone Hedge)
      1. {{PropVals/getRecords|prop={{{prop|RequiresObj}}}|page={{{page|{{FULLPAGENAME}} }}} }}
      2. {{PropVals/Group | <output from step above> }} internally using {{PropVals/Split}}
         Startpost|Lime;15|Flint;15|Stone;30/\ Cornerpost|Lime;8|Flint;8|Stone;15/\ Wallsegment|Flint;1|Stone;3/\ Gate|Board;10|Nails;4
         • As you can see the usage below doesn't work because the parser does not recognize the records as extra arguments...
           • {{PropVals/Group |{{PropVals/getRecords|prop={{{prop|RequiresObj}}}|page={{{page|{{FULLPAGENAME}} }}} }} }}
         • Therefore we need to use {{#arraymap:}} as a wrapper to inject the records as extra arguments...
           • {{#arraymap: {{PropVals/getRecords|prop={{{prop|RequiresObj}}}|page={{{page|{{FULLPAGENAME}} }}} }}{{{grpsep|/\}}} |{{{grpsep|/\}}} |x |{{PropVals/Group |sep={{{sep|;}}} |grpsep={{{grpsep|/\}}} |x }} |}}
           • {{PropVals/getGroupedRecords|prop={{{prop|RequiresObj}}}|page={{{page|{{FULLPAGENAME}} }}} }}
      3. <ul>{{#arraymap: <output from step above> |{{{grpsep|/\}}} |x |{{PropVals/List|x}} |}}</ul>
         
         • each {{PropVals/List}} using {{PropVals/Print Entry}} which will internally use {{PropVals/Split}}
         • <ul> {{#arraymap: |{{{grpsep|/\}}} |x |{{PropVals/List|x}} | }} </ul>
           
      4. {{PropVals|prop=RequiresObj}} gives:
         
      5. {{PropVals|prop=RequiresObj|page=Stone Hedge}} gives:
         
4. floating code...
   • {{PropVals/Split |val={{#show:{{FULLPAGENAME}} |?RequiresObj |link=none |sep=/\}} |sep=/\ |part=2 }}
     
   • {{#replace:{{#show:{{FULLPAGENAME}} |?RequiresObj |link=none |sep=/\}}|;|{{!}} }}
     
   • {{#arraymap: {{#replace:{{#show:{{FULLPAGENAME}} |?RequiresObj |link=none |sep=/\}}|;|{{!}} }} |/\|x|{{t|t|x}}|<br/> }}