Translations:Bugs/4/en: Difference between revisions

Jump to navigation Jump to search
Importing a new version from external source
(Importing a new version from external source)
(Importing a new version from external source)
Line 1:
* Attribute ranges on tooltips are sometimes incorrect
** Runeword tooltips don't account for the stat gained from a rune if the runeword itself adds the same stat. For example, Chains of Honor shows [35-45] all resistance but is actually 50-60 since Um adds +15.
** When multiple affixes add the same attribute, only a single affix's attribute range is shown.
** The attribute range can often show values for a different affix that adds the same attribute, even if that affix might not be able to roll on that particular item.
** The 50% Damage to Undead automod for blunt weapons isn't included in the attribute's range.
** Runeword tooltips don't account for the stat gained from a rune if the runeword itself adds the same stat. For example,(e.g. [[Chains of Honor]] shows [35-45] all resistanceres but is actually 50-60 since Um adds +15.)
** Several additional cases exist for this issue, but are not well documented.
* Lootfilter issues:
** The quantity shown with '''''%QTY%''''' doesn't update correctly sometimes when using cube recipes with stacked gems/runes.
** If the lootfilter attempts to hide stacked gems/runes, they'll usually be loaded regardless and appear with an [[Item_Filtering#Info_Codes|empty name]].
** Magic items without a prefix/suffix will have an extra space in their name where the prefix/suffix name would be, making the overall name appear slightly off-center.
** Some items have their [[Item_Filtering#Colors|default color]] built into '''''%NAME%''''', so their color won't change unless their name is rewritten completely.
** The '''GEMLEVEL''' condition doesn't apply to ''unstacked'' flawless/perfect gems like it intuitively should. ([[Item_Filtering#Gems|individual item codes]] can be used instead as a workaround)
** Conditions values get converted to unsigned integers before comparison, which means negative values count backward from the maximum storeable value (a few billion) rather than counting backward from 0 (multiple [[Item_Filtering#Named_Attribute_Codes|workarounds]] exist)
3,544

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu