~ NO ARGUMENTS = Will attempt to apply name and display settings to all blacks that have set at the front of the blocks name. If you make any changes to settings, be sure to recompile so they are saved! Recompiling the script will save configurations and store them to the custom data of the pb this script is running on. This informs the script that this block does not have a proper name defined and is allowed to be named as the script sees fit. These changes will be documented more in change notes and the reasons for the change, but its core was to make using the script easier and more hands on.Ī block can be modified by the script if the flag is found at the start of the block name. The ordering of the custom data has been changed as well as how blocks are interacted with via the script. NOTICE: The script has underwent some significant changes. The current schema can be dumped straight to custom data to allow you to modify and take with you your own version of naming conventions to any future build. It will by default attach the grid name it belongs to, the type, and an ID which just happens to be the blocks grid coordinates in reference to where the pb is placed, which allows you to quickly hunt down similar blocks and group them with ease.
The script works by finding a prexisting schema that you have defined, and whether defined or not, applies that schema to all block types on your current grid. Do you have your own naming convention you wish to take across builds? Thanks to a custom data dump, you can not only modify block type properties and names en-masse, but also take it with you wherever you go. Builders Script: Intimidated by the sheer volume of configs you need to set to make your ships menus nice and neat? Fear no more as with my NameChanging script you can configure your terminal blocks names and views numbering in the 1000's in mere seconds.