Year of the Dragon: Through May 28th, claim free Expansion Pack (excluding Vecna Unleashed) or a Greater Elixir of Discovery! Speak to Xatheral in the Hall of Heroes. edit

Game mechanicsNewbie guideIn developmentDDO StoreSocial Media


ChallengesClassesCollectablesCraftingEnhancementsEpic DestiniesFavorFeats

GlossaryItemsMapsMonstersPlacesQuestsRacesReincarnationSkillsSpells


Please create an account or log in to remove ads, build a reputation, and unlock more editing privileges and then visit DDO wiki's IRC Chat/Discord if you need any help!

Template talk:Augment

From DDO wiki
Jump to navigation Jump to search

Categories[edit]

I've added some categories. Not sure if we were waiting for something before creating them, but I think we need them. I need them :) Names can be changed, obviously. E.g. adding an article to the name (a/an) would be an option. Ideally we could use better categorizing, allowing us to find e.g. blue-slotted bracers and orange-slotted shields, but I am not sure if that's possible with the tools we have now. --Cru121 (ContributionsMessage) 05:17, July 3, 2013 (EDT)

New categories:


To wordy. Keep it simple <<color>> augment slot, that is all that is needed. Item with are a given, what else they going to be on that is not an item. Bladedge (ContributionsMessage) 13:58, July 3, 2013 (EDT)

Older discussions[edit]

Time for another poke at a revamp.[edit]

Hey guys. I'm thinking that this should be revamped to allow multiple augment slots to be listed with one template and in doing so allowing an additional category to be populated. Something like Multiple Augment Items or something so that people that want to make a weapon with a vampire slayer and a ruby of righteousness and a ruby of undead will know where they can find base items for this kind of thing. Just an idea and I think we can make it work with the loops extension. Anyways, I'll see what I can come up with next week. :) ShoeMaker (Contributions Message) 20:20, September 11, 2014 (EDT)

Edit request 10:44, August 22, 2018 (EDT)[edit]

Please updated this template with the source from T:Augment/sandbox (minus the {{Template testcase TOC}} of course) to allow pre-slotting information to be added to the template and more closely represent what is displayed on an item with an empty slot. Thanks, DDOstream (ContribsMessage) 10:44, August 22, 2018 (EDT)

Update 48 text changes[edit]

Mbox.png
A requested edit has been completed!
 
... by: PurpleSerpent (ContribsMessage) on: 11:50, January 25, 2022 (EST)


Hi all. I've sandboxed this template at Template:Augment/sandbox2 to implement some text modifications that came with Update 48. Stuff like 'Empty <color> Augment Slot' is now displayed as '<color> Augment Slot: Empty' in the UI, and the 'Augment' word is still present when an augment has been applied to the slot, like in 'Blue Augment Slot: Sapphire of Good Luck +1' instead of 'Blue Slot - Sapphire of Good Luck +1'. The bonuses listed in the popup text are still outdated. Please have a look at it and update this template if you like. MrLizard (ContribsMessage) 08:40, November 6, 2020 (EST)

  • Now the tooltip in Template:Augment/sandbox2 is updated as well (to U48). Besides replacing the hard-coded named augments by {{Category listing}}, I tried also to despaghetize the code by defining a variable for each color list, so the list codes don't repeat inside {{Popup}}. This is easier to maintain and update in my opinion. MrLizard (ContribsMessage) 00:16, November 25, 2020 (EST)
    • It's a very long tooltip now, isn't it? I'll see to adding the Saltmarsh augments in a minute, but maybe we need a new solution in the long term. Anyway, now completed. PurpleSerpent (ContribsMessage) 06:55, January 26, 2022 (EST)

Size of template[edit]

Because this template is meant to be used in-line and often en masse, the size of the template is causing some quest pages to not display. First of all, the basics: The size is measured in characters but in a weird way. 1 character = 1 character. A sentence of X characters has the size of X characters. However, when a sentence is inside a parser function or a transclusion, then the size doubles because it is counted once for the initial transclusion and once for the current page. If a sentence is inside 2 transclusions, then the size triples X * (depth).

This means that the deeper the bulk of the information is, the bigger the template size. One of the ways to mitigate that is to ensure that deep templates (such as {{Hlist}} which is used for {{Category listing}} which is used from here) need to be as small as possible or not used at all (as can be the case for {{Category listing}} which doesn't need to use {{Hlist}}.

Another area to improve on is the template cache. A template with no parameters is cached and always produces the same value no matter what. If the augment template calls sub-templates with no arguments according to the color parameter, then the size of a page using this template many times would be (the size of the text produced by this template) * (the number of times this template is used) + (the size of the text produced by the sub-templates) * (once). This would be a significant size reduction for pages using this template many times. Faltout (ContribsMessage) 14:21, February 1, 2022 (EST)

  • I'll be honest, I still can't figure this particular template out. I've called MrLizard in - they designed this version of the template so they should know what they're doing better than I do. (My suggested fix would be to remove the named augments and the values of the bonuses for the standard ones.) PurpleSerpent (ContribsMessage) 15:25, February 1, 2022 (EST)
  • OK, I seem to have got something working, at least. I've replaced the category listing for named augments with a link to the category - this has dramatically reduced the template size. I will now test Temple of Elemental Evil Part One to see if that's enough. PurpleSerpent (ContribsMessage) 07:02, February 2, 2022 (EST)
  • Good to know. That should do for now, then - maybe in the long term I can work out how to condense the info for the standard items. PurpleSerpent (ContribsMessage) 15:25, February 2, 2022 (EST)
  • I know I'm repetitive but I still think this Wiki overuses Popup to an annoying rate. And this template creates one top ranking, maybe even place One:
    • for it's size especially blue and yellow. Together with the zero delay for popups you often cannot "leave" the popup through the bottom and have to make a "loop" with the mouse. In item lists hate +1
    • for it's constant being not uptodate in blue and yellow; see my latest change on the augment page for a drop only sapphire
    • for it's general uselessness (in my point of view): There is no sense in selecting augments related to a single item, you need to take into account your whole equipment and there you need another approach than this popup

Corgrind (ContribsMessage) 13:48, February 3, 2022 (EST)

  • As a counterpoint, I think T:Popup is really helpful for condensing information on items so item pages are actually readable without having to navigate to another page when you don't know what something does, and having an Augment popup is really helpful when trying to work out gear selection. Otherwise I have to go and stare at a really long table for twenty minutes and try to ignore all the irritating verify tags. PurpleSerpent (ContribsMessage) 14:02, February 3, 2022 (EST)
  • I'm no longer a big fan of {{Popup}} either due to it's poor display on mobile devices. It was great in the beginning before phone/tablet was the primary access option. That said, I don't have a better solution to offer at this time. I'm open to suggestions on how to offer the information without the popup template as it exists now.  👟 ShoeMaker ( Talk • Contribs • Patrol • Moves • B • D • I • PP • UM • UR ) 👟 17:20, May 24, 2024 (EDT)
  • Just an idea... I believe the usage of {{Popup}} in this template appeared way before the list of possible item augments became so big. I think it made sense for what the game had before U48. I have thought on an alternative... we could possibly create pages listing all the item augments of each color, which must include both non-named and named augments for that color. The named ones can be pulled automatically using {{Category listing}}. Example, having a page for blue augments listing all the existing non-named and named blue augments, without listing 'sub-color' ones, like colorless augments. Those would be listed only in their respective page, for colorless augments. This page could be even C:Blue augments itself, after adding the list of non-named blue augments to the page text (not new pages in the category). Then, remove {{Popup}} from this template, and add colored symbols appearing after the template display text... like "Blue augment slot BC". Using letters B and C here just an example for symbols. In pratice, would use symbols similar to the ones in {{Xpcolors}}. In this example, 'B' being a blue symbol, and 'C' being a transparent (colorless, somehow ??) symbol. Link 'B' to the page listing all the blue augments, and 'C' to the page listing all the colorless augments. Another example, a Purple augment slot would appear as "Purple augment slot PRBC", with 'P' being a purple symbol, 'R' being a red symbol, and so on, linking to the respective color list pages. I would have no problem on opening a few extra tabs in the browser, one for each color list, considering that all augment slots of same color have the same list of possible augments. Does this make any sense? MrLizard (ContribsMessage) 00:48, May 25, 2024 (EDT)
  • I've removed all of the stuff related to pre-slotted augments since they're no longer a thing. I'll do some testing tomorrow on the caching idea and just using {{Augment/red}}, {{Augment/blue}}, etc instead of {{ Augment | red }}, {{ Augment | blue }}, etc respectively.  👟 ShoeMaker ( Talk • Contribs • Patrol • Moves • B • D • I • PP • UM • UR ) 👟 10:57, May 26, 2024 (EDT)
  • Faltout I ran a test on your template cache theory and the results that I see are as follows:
U:Technical_13/SandBox/1x8 uses {{Augment}} 8 times with no parameter being passed in and the Post-expand include size 20,136/2,097,152 bytes.
U:Technical_13/SandBox/8x8 uses {{ Augment | colorless }} 8 times with a colorless parameter being passed in and the Post-expand include size 20,280/2,097,152 bytes.
The difference between the two is 144 bytes for the set of 8 calls or an average of 18 bytes per call. This does not seem to be a valid solution. If what you were saying was accurate, I'd have expected the 1x8 example to be closer to 2,535/20,097,152 bytes.  👟 ShoeMaker ( Talk • Contribs • Patrol • Moves • B • D • I • PP • UM • UR ) 👟 10:10, May 28, 2024 (EDT)
I think there is a major misunderstanding: MrLizard and Me are talking about the display size (height) of the box, not the impact on the cache usage. In fact all the discussions about popups are related to their display size, issues on overlapping with other page elements and just being in the way. Corgrind (ContribsMessage) 10:54, May 28, 2024 (EDT)