Jump to content
Report an Alpha 21 Bug!

  • player cant loot after prefab reset if player was in a container when prefab is reset

    wolfbain5

    By wolfbain5

     Share

     Summary: player cant loot after prefab reset if player was in a container when prefab is reset

     

    Game Version: (A20b238)

    Platform: (PC)

    OS/Version: (Windows)

    CPU Model: (AMD Ryzen 5 3600 6-Core Processor 3.60 GHz)

    System Memory: (32 gb)

    GPU Model and VRAM: (radeon rx 580 8 gb)

    Screen Resolution: (1920 x 1080)

    Video Settings: ( High)

    Game mode: (MP host, RWG)

     

    Did you wipe old saves? (Yes)

    Did you start a new game? (Yes)

    Did you validate your files? (Yes)

    Are you using any mods? (Yes) stack size mod

    EAC off

     

    Status: NEW

     

    Bug Description: player cant loot after prefab reset if player was in a container when prefab is reset

     

    Detailed steps to reproduce the bug:

    1) be in party

    2) accept quest

    3) be in process of looting a container or in a container <do not exit container>

    4) party member starts quest

    5) exit container

     

    Actual result: the person can no longer loot containers while other players can. the "stuck" player can still interact with items, just cant open them to loot. doors can still be used.

     

    Expected result: to be able to loot as normal.

    1
     Share
    Go to records

    User Feedback

    Recommended Comments

    Blake_

    Not only does it happen exactly like that, but if you also take apart the POI with a wrench before producing the issue, the respawned place becomes a structural integrity nightmare, things collapsing for no reason and weird blocks all over the place, some containers previously wrenched become invisible to the client, some unlootable by the admin.... etc

     

     

    Link to comment
    Share on other sites
    chikorina

    Thank you for the report.  I have confirmed the issue,  only when I reset the chunk by command.  I was not able to confirm it when activating a quest in the current stable (A20.2 b2).  I will do further testing in an earlier version. 

    Edited by chikorina (see edit history)
    Link to comment
    Share on other sites
    chikorina

    I have confirmed that this will happen with chunk resets,  but was not able to reproduce the issue with quest activation by a party member.  I tried with both the host activating the quest and the client activating the quest.

    I have made a ticket for this issue happening upon chunk reset.

    Link to comment
    Share on other sites


    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...