Template talk:Gem Infobox
This talk page is for discussing Template:Gem Infobox.
- Sign your posts using four tildes (
~~~~
) - Start a new topic at the bottom under a
==level 2 heading==
- Indent replies using colons (
:
) - Keep it civil
- Assume good faith
- Don't remove past discussions
Broken File Links
All support gems with this template are showing up as having broken file links due to them not having a skill icon. When I'm not fumbling about on a tablet I'll take a look at putting it into an if statement to resolve that. Iamacyborg (talk) 14:50, 9 March 2013 (UTC)
Attribute Requirements
I would like to propose a change to this template for how attributes requirements are displayed. Currently, there is a row that simply lists any attributes that a gem requires to equip; eg., "Dexterity, Intelligence". The change that I propose is to remove that row and add three optional rows below the "Required Level" row that list the actual numbers for attribute requirements.
It would look something like this:
Required Level: 1 to 60 Required Strength: 12 to 80 Required Dexterity: 4 to 112
Since this is a change that requires many pages to be updated, I want to poll the community before implementing this. —Vinifera7 (talk) 04:09, 15 March 2013 (UTC)
Mana Cost Multiplier --> Mana Multiplier
This aspect of support gems was changed quite a long time ago. They no longer have a "mana cost multiplier", it's now simply called a "mana multiplier". I'm not sure how exactly I should change this so maybe someone else could help here. -- Ezhiel (talk) 14:59, 11 January 2014 (UTC)
Add semantic properties/categories to this template?
I think this template needs an overhaul. Gems are manually displayed in extensive lists on several pages. For example
I'm sure there are a few more as well. Keeping these pages up to date is difficult to do manually. By adding semantic properties and putting the gems in consistent categories it will be easy to create lists that updates automatically with semantic queries. I've done a few examples here: User:Illviljan/test2.
I'm no programmer but I was thinking it should work similar to Template:Ascendancy_Class. Parameters that I think need to be used for properties and categories are:
- type
- attributes
- keywords
- (gem color)
I think these should be enough to create consistent categories. They should probably be combined to guarantee unique categories, maybe like ('attributes type')/('keywords type')/('gemcolor type')?--Illviljan (talk) 03:43, 14 February 2016 (UTC)
- I'm working on a overhaul of the item template which the gems are part of. However it is likely it will be a bit more complicated in the end, since skills will receive their own template which then is integrated into item module, since there are plenty of skills that do not have an associated gem, like monster skills. I have an early version here which still doesn't incorporate things like the gem level progression User:OmegaK2/test2.
- All those lists can be auto generated at that point like with the mods, but the template is one that I didn't find as easy as mods to plan out and execute, as the info for gems is derieved from about 6-7 files and the question is how user-editable the things should be. It would lead to pretty huge templates, like this:
{{Skill |id= |name= |dex= |int= |str= |tags= |cast_time= |is_support= |support_gem_letter= |level1_experience |level1_mana_cost |level1_mana_multiplier |level1_damage_multiplier |level1_critical_strike_chance |level1_vaal_souls |level1_level_requirement |level1_stat_text |level1_stat1_id |level1_stat1_value |[other stats] |level1_quality_stat_text |level1_quality_stat1_id |level1_quality_stat1_value |[other stats...] [repeat for all levels until maxlevel]