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

[Known] Purchasing arrows is bugged

Discussion in 'Release 35 Bug Forum' started by Neiro, Oct 27, 2016.

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

    Neiro Avatar

    Messages:
    45
    Likes Received:
    38
    Trophy Points:
    8
    Gender:
    Male
    Location:
    Denmark
    10/27/2016 8:19 PM
    Title: Purchasing arrows is bugged
    Reproduction Rate: unsure
    Blocker?
    Details: Purchasing arrows is not working as it should. I had 700 something, and purchased another 25 stacks. Ended up with 15x 'bundle of 24 arrows' and the rest were 'arrow' x24 - didn't count em, but could be the last 10 ones. Had to select all of them and drag them over the 700 something I already had several times before they were all in the stack
    Steps to Reproduce:
    User Specs:
    OS: Windows 10 (10.0.0) 64bit
    CPU: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz (4) System RAM: 15296
    GPU: NVIDIA GeForce GTX 770 GPU RAM: 2017
    SotA.EarlyAccess.Win.64.495.Date.10.26.16
    Area: Novia_R3_City_Brittany_Estates
    Area Display Name: Brittany Estates
    Loc: (135.6, 74.2, 434.2)
     
    Kelly O\'Shay likes this.
  2. Mishikal

    Mishikal Avatar

    Messages:
    1,965
    Likes Received:
    2,834
    Trophy Points:
    113
    Location:
    Brittany Estates
    Already reported earlier. :)
     
  3. Gamician

    Gamician Avatar

    Messages:
    370
    Likes Received:
    1,306
    Trophy Points:
    43
    @Neiro, Thank you for reporting. Previously reported in R34, Issue has been resubmitted again to Team for review. Keep up the good work and keep those reports coming.
     
  4. Mishikal

    Mishikal Avatar

    Messages:
    1,965
    Likes Received:
    2,834
    Trophy Points:
    113
    Location:
    Brittany Estates
    This bug did not exist in R34.
     
  5. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    Known issue.

    Bug reference id: 36211
     
Thread Status:
Not open for further replies.