Jump to content
Report an Alpha 21 Bug!

  • Level/Prefab (backpack) Toolbelt error Loop

    EtherRu

    By EtherRu

      • Version: a21.2 b30
     Share

    Summary: A toolbelt error loop appearing after a21.2 b30 update while in level prefab editor.
     

    Game Version: (A21 b30)

    OS/Version: (Windows 11 (10.0.22631) 64bit)

    CPU Model: (13th Gen Intel(R) Core(TM) i7-13700F (cores: 24))

    System Memory: (16gb)

    GPU Model and VRAM: (NVIDIA GeForce RTX 4070 (12026 MB))

    Screen Resolution: (1920x1080? I think)

    Video Settings: (Ultra)

    Game mode: (Level Prefab Editor, alone)

     

    Did you wipe old saves? (No)

     

    Did you start a new game? (No)

     

    Did you validate your files? (Yes)

     

    Are you using any mods? (No)

     

    EAC on or off? (On)

     

    (NOTE)  I have also uninstalled and reinstalled the game and found the same results.  I have logged into a previously saved game <NOT the the level prefab editor> and the game functions as normal.  This error only appears in the editor.

     

    Status: NEW

     

    Bug Description:  After the update I logged into the level prefab editor and was sent a looping error in red, saying... "ERR [XUi] Error while updating window group 'toolbelt':  EXC Empty input string" which loops indefinitely, making the prefabber unusuable.  This error does not apply to saved games.  Only the level prefab editor.

     

    Detailed steps to reproduce the bug:

    1) Log into prefab editor with existing project from previous version (pre-a21.2 b30 stable)

    2) Recieve report of backpack error.

    3) Close report, and open backpack.
    4) Items not previously in backpack are now present, including an item with no image.

    5) Clear backpack and toolbelt using the wastebin function.

    6) Close backpack, and open player menu.  Error loop begins.

     

    Actual result: (Endless string of the same toolbelt error)

     

    Expected result: (The backpack and toolbelt to be empty, so that new objects can be selected from the block menu)

    Link to Pastebin Output Log:      https://pastebin.com/cwY968Re

    0
     Share
    Go to records

    User Feedback

    Recommended Comments

    NekoPawtato

    Thank you for reporting. I haven't been able to reproduce the error thus far attempting to place various different items in my toolbar in A21.1 and then upgrading to A21.2. I think it may require a very specific item.

     

    I'm curious, if you downgrade back to A21.1 and go into the prefab editor, does the error go away? (take a backup before you do this if you want to be extra cautious). If you are able to load into the editor on A21.1, can you take a screenshot of your toolbelt items and upload the image using an image hosting site such as imgur? 

     

    1
    Link to comment
    Share on other sites
    Laz Man

    Worth a shot, try deleting your "Empty" folder in your Saves directory.  See example link below.

     

    C:\Users\<user profile name>\AppData\Roaming\7DaysToDie\Saves\Empty

     

    The Empty folder is specifically used by the prefab editor.  Deleting it will reset any toolbelt / character equipped items when in the prefab editor that could be causing the error.

    Edited by Laz Man (see edit history)
    2
    Link to comment
    Share on other sites
    EtherRu

    Thank you all for your attention and assistance.

    Although I am not sure what item or precise situation that caused the error, I am thrilled to say that Laz Man's solution worked.

    Deleting the "Empty" folder and then loading the prefab editor again, reset all functions and removed the error.

    On 11/23/2023 at 5:11 PM, Laz Man said:

    Worth a shot, try deleting your "Empty" folder in your Saves directory.  See example link below.

     

    C:\Users\<user profile name>\AppData\Roaming\7DaysToDie\Saves\Empty

     

    The Empty folder is specifically used by the prefab editor.  Deleting it will reset any toolbelt / character equipped items when in the prefab editor that could be causing the error.

     

    2
    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...