1. This forum is for bug reporting of current Player Test Environment (QA Server) issues ONLY.
    Be sure to follow the format below, it will help us out greatly in responding. If you do not, your report may not be entered into the system.

    Read BEFORE submitting your first bug: Reporting Bugsā€¦ QA 101 Document
    • Search for your bug in all likely categories before posting in order to avoid duplicate reports.
    • Be sure to provide details of what the issue is and how to re-produce it, but keep your bug report factual.
    • Reply to an existing thread if you have additional information for the reported bug.
      Do not use this forum for commentary, your post will be deleted and you may be moderated, suspended or banned if the activity continues.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    NOTE: Important information including your location and system specs are automatically put into your clipboard when using /devbug in the game (DO NOT add additional system specs unless requested). When starting your post, just use <CTRL>-V to insert the data and fill in the entries with no data.

    Please include Screenshots if possible. Images can be saved on our SotA Discord Server here

    If the clipboard does not work, use and fill in this Bug Report Template:
    1. Title:
    2. Reproducible?
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs: (RAM, CPU, GPU and Operating System only)

[Patch Pending 68278] Explosive chests - attacking them after they have exploded causes re-explosion

Discussion in 'World Building, Scenes, Environment, & Overworld' started by Rinaldi, Nov 28, 2020.

  1. Rinaldi

    Rinaldi Bug Hunter

    Messages:
    1,131
    Likes Received:
    3,005
    Trophy Points:
    113
    Gender:
    Male
    11/28/2020 08:00
    Title: Explosive chests - attacking them after they have exploded causes re-explosion
    Reproduction Rate: 100%
    Blocker? no
    Details: I open an explosive chest and it explodes, leaving behind burned debris. Then, I swing with my sword at the burned debris and the debris explodes. The burned debris keeps exploding as long as i attack it. If i exit combat and click on the burned debris, nothing happens. The re-explosions only happen when i attack the burned debris. In fact, i can go somewhere else in the zone for a few minutes then comeback to attack the burned debris...and boom it still explodes. I have seen this behavior in all zones that I have found explosive chests, including tanglemire and the breach. This is present on the current live server as well.
    Steps to Reproduce: see above.
    User Specs:
    OS: Windows 10 (10.0.0) 64bit
    CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8) System RAM: 32708
    GPU: NVIDIA GeForce GTX 1070 GPU RAM: 8088
    SotA.QA.Win.64.1104.Date.11.23.20
    Area: Mistrendur_TheBreach
    Area Display Name: The Breach
    Loc: (48.0, 67.1, 71.2)
    Debug: TWlzdHJlbmR1cl9UaGVCcmVhY2h8fCg0Ny45NjYsIDY3LjA5MywgNzEuMTkzKXwoMCwgLTAuNDI0LCAwLCAwLjkwNil8LTQyNi4yMzh8NjIuMjU3MDZ8MTEuMzY4NzY=

    Addendum 12-9-2020
    Still present in QA.1108.Date.12.05.20
     
    Last edited: Dec 9, 2020
  2. Sannio

    Sannio Lead Quest and Level Designer Moderator SOTA Developer

    Messages:
    3,021
    Likes Received:
    4,856
    Trophy Points:
    153
    Gender:
    Male
    Thanks for the report! Issue #68352
     
  3. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    11,731
    Likes Received:
    16,800
    Trophy Points:
    153
    @Sannio, if you're looking at the exploding barrels be aware of 68278, too
     
  4. Sannio

    Sannio Lead Quest and Level Designer Moderator SOTA Developer

    Messages:
    3,021
    Likes Received:
    4,856
    Trophy Points:
    153
    Gender:
    Male
    Thanks for pointing this out. Closing out the Jira I created and adding this info to the 68278 issue.
     
  5. DavidDC

    DavidDC The New Guy Moderator SOTA Developer

    Messages:
    1,156
    Likes Received:
    2,376
    Trophy Points:
    113
    Should be fixed in a upcoming patch