Difference between revisions of "Template talk:Vendor item row"

From Project: Gorgon Wiki
Jump to: navigation, search
(Recipes: new section)
m (Recipes)
Line 5: Line 5:
 
== Recipes ==
 
== Recipes ==
  
I got a bit derailed from completing this template when I encountered recipes.  See [[Braigon]] Training section.  I went so far as to modify the item description thinking I was dealing with a recipe description, before I realized that we need something like: {{tlc|Recipe}} which would show the icon and link to Recipe: Item (instead of Item), and then a {{tlc|vendor recipe row}} which would work just like this template, but call {{tlc|Recipe}} instead of item, to link the correct recipes.  The problem is: we don't currently have any Recipes in the wiki.  So trying to decide if I should push forward and just do it, or skip it for now.
+
I got a bit derailed from completing this template when I encountered recipes.  See [[Braigon]] Training section.  I went so far as to modify the item description thinking I was dealing with a recipe description, before I realized that we need something like: {{tlc|Recipe}} which would show the icon and link to Recipe: Item (instead of Item), and then a {{tlc|vendor recipe row}} which would work just like this template, but call {{tlc|Recipe}} instead of {{tlc|Item}}, to link the correct recipes.  The problem is: we don't currently have any Recipes in the wiki.  So trying to decide if I should push forward and just do it, or skip it for now.
  
 
There does seem to be some utility for Recipes in the wiki though.  Have a look at [[Basic Rennet]].  Completely wrong from an item perspective, but perhaps useful from a recipe perspective.  I still have recipes which I'd like to know where to find, what the ingredients list is, etc. and having Recipe pages would help with that.
 
There does seem to be some utility for Recipes in the wiki though.  Have a look at [[Basic Rennet]].  Completely wrong from an item perspective, but perhaps useful from a recipe perspective.  I still have recipes which I'd like to know where to find, what the ingredients list is, etc. and having Recipe pages would help with that.

Revision as of 14:54, 3 March 2017

Parameter 'level' to 'favor' ?

I'd like to change 'level' to 'favor' if that's alright before too much stuff uses this template. I think it would be a more descriptive parameter name. Alleryn (talk) 10:00, 3 March 2017 (CST)

Yes, was a bit torn by that creating the template. Unfortunately, "favor" is often used in the context of a numerical value: i.e. 60 favor for gifting a Council Certificate. This template is still very much under construction, and thinking it might get inherited by something else that does use numerical favor (maybe by a table of items that can be traded for favor?), I opted to go with "level" to possibly avoid confusion. But I agree, not the best term. Maybe something else will come to mind. "favor-level" is most accurate, but cumbersome. Others: Relationship, association (no better), status (not very description). Trying to remember what other games use instead of "favor". Arindor (talk) 12:42, 3 March 2017 (CST)

Recipes

I got a bit derailed from completing this template when I encountered recipes. See Braigon Training section. I went so far as to modify the item description thinking I was dealing with a recipe description, before I realized that we need something like: Template:Tlc which would show the icon and link to Recipe: Item (instead of Item), and then a Template:Tlc which would work just like this template, but call Template:Tlc instead of Template:Tlc, to link the correct recipes. The problem is: we don't currently have any Recipes in the wiki. So trying to decide if I should push forward and just do it, or skip it for now.

There does seem to be some utility for Recipes in the wiki though. Have a look at Basic Rennet. Completely wrong from an item perspective, but perhaps useful from a recipe perspective. I still have recipes which I'd like to know where to find, what the ingredients list is, etc. and having Recipe pages would help with that.