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

Interrupt while harvesting b being attacked makes node unharvestable

Discussion in 'Release 25 Bug Forum' started by Elwyn, Jan 13, 2016.

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

    Elwyn Avatar

    Messages:
    3,619
    Likes Received:
    4,784
    Trophy Points:
    153
    Gender:
    Male
    Location:
    San Antonio, TX
    1/13/2016 7:35 PM
    Title: Interrupt while harvesting from being attacked makes node unharvestable
    Reproduction Rate: not sure, I try to avoid the conditions that cause it
    Blocker? no
    User Specs:
    OS: Windows 7 Service Pack 1 (6.1.7601) 64bit
    CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (4) System RAM: 16266
    GPU: NVIDIA NVS 4200M GPU RAM: 2258
    SotA.PreAlpha.Win.64.364.Date.12.28.15
    Area: SolaceBridge
    Loc: (120.8, 39.0, -73.3)

    Details:
    When harvesting a node, if attacked by an NPC, you will get interrupted. It is possible that this will result in the node not being harvestable. I'm not sure that it's 100%, but I've had it happen enough times so far that I'm finally posting it as a bug.
    Steps to Reproduce:
    - Harvest a node
    - Get attacked by a monster while in the process of harvesting
    - Fight the stupid thing
    - Try to harvest
    - Cursor won't change, node won't double-click, but you can see the survey sparklies

    This is probably not from when you have just finished the harvest; that usually results in a green cursor over the node and you can straight up loot it. But I wouldn't rule out that that is where the problem is. I can't remember that happening (loot mode on the node) much lately, so maybe it is.

    If I videoed my sessions, I might have more info, but I don't do that.

    EDIT: if you see the monster coming and you manually interrupt yourself, this does NOT happen
     
    Last edited: Jan 13, 2016
  2. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    @Elwyn We're having difficulty reproducing this issue Dev-side. We'll keep observing it, because we have seen this reported in the past. We're continuously investigating for a solid repro case to isolate the cause. Thank you for reporting.
     
Thread Status:
Not open for further replies.