Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Known] Masterwork failure reduces the +# on items by 1

Discussion in 'Crafting, Harvesting, Salvage, & Agriculture' started by Oakenhammer, Apr 22, 2018.

Thread Status:
Not open for further replies.
  1. Oakenhammer

    Oakenhammer Avatar

    Messages:
    355
    Likes Received:
    999
    Trophy Points:
    55
    Gender:
    Male
    Location:
    Austin
    4/22/2018 12:11 AM
    Title: Masterwork failure reduces the +# on items by 1
    Reproduction Rate: 100%
    Blocker? No
    Details:
    This issue may be intentional, but I'm bug reporting it just in case. In addition to the durability loss of the item on failure, the + number on items is also reduced by 1.

    This reduction is a bit counterintuitive as the relative power of the item is not changed by the loss of durability. In the second image below, the item has modifiers to be a +7 weapon, but the failures cause it to show as a +3. That being said, I can understand the +1 granted by the Exceptional crafting to be lost after 2 failures, but the additional reductions cause confusion when comparing the power of this item to other +3s.

    Steps to Reproduce:
    1. Craft an exceptional longsword (e.g. +1)
    2. Masterwork the sword multiple times
    3. Make note of the +# after each attempt and notice how it is reduced by 1 after each failure

    [​IMG]
    [​IMG]

    User Specs:
    OS: Windows 10 (10.0.0) 64bit
    CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8) System RAM: 32640
    GPU: NVIDIA GeForce GTX 1070 GPU RAM: 8074
    SotA.QA.Win.64.668.Date.04.20.18
    Area: Novia_R3_City_Brittany_Estates
    Area Display Name: Brittany Estates
    Loc: (297.9, 65.0, 253.4)
    Debug: Tm92aWFfUjNfQ2l0eV9Ccml0dGFueV9Fc3RhdGVzfHwoMjk3Ljk0MSwgNjQuOTk3LCAyNTMuMzY4KXwoMCwgMC45OTEsIDAsIC0wLjEzMSl8MTk1LjA2MDV8MTB8Ni41NTgxOA==
     
    Rentier likes this.
  2. Lexie

    Lexie Bear Queen Emeritus

    Messages:
    842
    Likes Received:
    2,902
    Trophy Points:
    93
    Yes, this was reported last week. It had been bugged in JIRA. :)
    @Oakenhammer
     
Thread Status:
Not open for further replies.