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

[By design] Confusion would not gain experience everytime the sill is used

Discussion in 'Combat, Skills, & Magic' started by radi, May 3, 2018.

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

    radi Avatar

    Messages:
    20
    Likes Received:
    22
    Trophy Points:
    3
    Gender:
    Male
    Title: Confusion would not gain experience everytime the sill is used

    Reproduction Rate: every time

    Blocker? Yes?

    Details: Confusion would not gain experience every time the sill is used

    Steps to Reproduce: Use the Confusion skill when the card becomes available

    Expected: Using the Confusion skill will gain experience every time.
    Actual: Using the Confusion skill will gain experience ONLY when the Practice Dummy is confused.


    User Specs: SotA.Win.64.773, GTX 1060
     
  2. FruityTooty

    FruityTooty Avatar

    Messages:
    6
    Likes Received:
    4
    Trophy Points:
    3
    So, in a weird twist, when I cast Chaos Bolt, it's increasing Confusion's skill. Chaos Bolt's skill doesn't increase at all
     
  3. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,729
    Likes Received:
    19,496
    Trophy Points:
    153
    @radi, @FruityTooty, this is expected. skill requirements for dependent skills have changed some in development. if you learned chaos bolt when the confusion requirement was set lower, but it's since been changed and NOW you wouldn't qualify to learn it because your confusion isn't high enough, using any skill dependent on confusion will train confusion until confusion is at the level required by its dependents. it will stop on its own when it reaches that point and start training chaos bolt instead.
     
  4. Lexie

    Lexie Bear Queen Emeritus

    Messages:
    842
    Likes Received:
    2,902
    Trophy Points:
    93
    This is exactly right. Now that the bug is fixed, you have to get confusion up to the pre-req level. This will match the alignment as to how everyone else currently sees it - those who were never affected by the prior bug.

     
Thread Status:
Not open for further replies.