Filed / Tracking 'prefabinfo' command not working on many BPs [5978]

Discussion in 'Tracking / Filed' started by NimrodX, Jan 28, 2019.

  1. NimrodX

    NimrodX Commander

    Joined:
    Dec 13, 2018
    Messages:
    91
    Likes Received:
    103
    Mode: All (tested in creative and survival)
    Mode: SP

    SERVER NAME: NA
    SEED-ID: NA

    MODIFIED PLAYFIELDS: No

    Reproducibility: Sometimes (some BPs and not others)
    Severity: Minor

    Type: Blueprints, Console

    Summary: The 'prefabinfo' console command says "prefab not found" on many blueprints.

    Description: For some reason it can find some blueprints and not others. This is even when using single quotes to quote the name of the blueprint if it contains spaces. Some BPs it works on, others it doesn't. It doesn't seem to matter if the BP has been spawned in the current playfield or not.

    Steps to Reproduce: Hit F2, have some custom local blueprints (not workshop and not game-included), note the BP names. Attempt to use the prefabinfo command on them. It will work on some and others it will keep saying "not found".

    This is a problem for people trying to fix blueprints that have become invalid due to changes to blocks.
     
    #1
  2. Myrmidon

    Myrmidon Rear Admiral

    Joined:
    Mar 26, 2016
    Messages:
    1,737
    Likes Received:
    2,067
    The command 'prefabinfo' works when you use the exact folder name of the blueprint. Have you tried copy paste? some have numbers.
     
    #2
    Injunuity likes this.
  3. NimrodX

    NimrodX Commander

    Joined:
    Dec 13, 2018
    Messages:
    91
    Likes Received:
    103
    That's bizarre and would explain the problem, but it still seems like a bug that needs fixing. As far as anyone is concerned, the name of their BP is Ship not Ship__32394832954

    Looking through my BPs, the ones with the number are the ones published to the workshop. The ones with unmangled names are all ones I didn't publish.
     
    #3
  4. RazzleWin

    RazzleWin Rear Admiral

    Joined:
    May 22, 2017
    Messages:
    622
    Likes Received:
    1,464
    Could it be because some of them use group names?
     
    #4
  5. Myrmidon

    Myrmidon Rear Admiral

    Joined:
    Mar 26, 2016
    Messages:
    1,737
    Likes Received:
    2,067
    I do not think so.
     
    #5
  6. Txawen

    Txawen Ensign

    Joined:
    Jan 15, 2019
    Messages:
    5
    Likes Received:
    0
    I couldnt prefabinfo with and old BP, it had numbers a "-" sign and letters, saved them again with name aa and it worked, prefabinfo aa
     
    #6
  7. jadefalcon

    jadefalcon Captain

    Joined:
    Jan 30, 2018
    Messages:
    555
    Likes Received:
    2,302
    Ive had this issue with BPs which have the ' character in them.
    I suspect that used as a delimiter somewhere
     
    #7
  8. ravien_ff

    ravien_ff Rear Admiral

    Joined:
    Oct 22, 2017
    Messages:
    6,291
    Likes Received:
    11,948
    I read a comment that if your blueprint name has spaces in it, try enclosing the name in single quotes when you use the command. So Big Base 17 would be 'Big Base 17'

    Try that.
     
    #8
  9. ASTIC

    ASTIC Rear Admiral

    Joined:
    Dec 11, 2016
    Messages:
    1,094
    Likes Received:
    735
    If you have published the blueprint in the workshop, that's the reason, as you've already found out, no bug, it will be added to this unique number in the directory that ensures the connection to the workshop object.
    So you always have to specify the FULL directory name in "prefabinfo".
     
    #9
  10. It's still technically an error in the game, since even the game tells you to "(specify a name as listed in your Blueprint Library)".
    It says nothing about the directory, and the Blueprint Library is in-game.
    It might be working as intended, but it's still listed wrong in the console when using the "help prefabinfo" command.
     
    #10
  11. NimrodX

    NimrodX Commander

    Joined:
    Dec 13, 2018
    Messages:
    91
    Likes Received:
    103
    Yes, exactly. At absolute minimum, the help text needs to be updated to not suggest using the display name.

    I suspect the command just hasn't been updated or touched at all since Workshop support was added.
     
    #11
  12. Robot Shark

    Robot Shark Rear Admiral

    Joined:
    Jul 3, 2016
    Messages:
    2,198
    Likes Received:
    5,768
    I could not get the command to work using "CV-Condor" but I re-saved the blueprint as "aaa" and was able to use it.

    I made sure the capitalization matched in my attempt before using "save as". Maybe the command does not recognize the dash?
     
    #12
  13. Donbingo

    Donbingo Captain

    Joined:
    Aug 17, 2016
    Messages:
    55
    Likes Received:
    368
    Its late and I am a bit sick, so it could be an error in the carbon unit, but I got this error message:

    20190130221301_1.jpg
     
    #13
  14. NimrodX

    NimrodX Commander

    Joined:
    Dec 13, 2018
    Messages:
    91
    Likes Received:
    103
    Console commands need things quoted with single quotes. So for names requiring spaces, "This Name" will not work but 'This Name' will (unless something else is wrong.)
     
    #14
  15. Injunuity

    Injunuity Ensign

    Joined:
    Aug 20, 2020
    Messages:
    2
    Likes Received:
    1
    took awhile to find this, tysm, it saved my sanity lol
     
    #15
    Myrmidon likes this.

Share This Page