Jump to content

Part CFG question


Recommended Posts

I copied the micronode, it's cfg and it's .mu and dds to a separate nested directory in 'GameData'  to experiment with and I haven't gotten off to a very good start. It appears I am not as capable as I thought.

I have changed the name and I changed the title and description after the '=' sign.

While the 'new' part shows up in my game along with the original, neither the title nor description has changed to the ones in edited cfg.

What am I not seeing?

 

 

Link to comment
Share on other sites

Ok.. Config text.

PART
{
    name = MyStructuralMiniNode
    module = Part
    author = NovaSilisko
    mesh = model.mu
    rescaleFactor = 1
    node_stack_right = 0.1823258, 0, 0, 1, 0, 0, 0
    node_stack_left = -0.1823258, 0, 0, -1, 0, 0, 0
    node_stack_back = 0, 0, 0.1823258, 0, 0, 1, 0
    node_stack_front = 0, 0,-0.1823258, 0, 0, -1, 0
    node_stack_top = 0, 0.1823258, 0, 0, 1, 0, 0
    node_stack_bottom = 0,-0.1823258, 0, 0, -1, 0, 0
    TechRequired = precisionEngineering
    entryCost = 9800
    cost = 25
    category = Structural
    subcategory = 0
    title = #autoLOC_500757 //#autoLOC_500757 = My Micronode
    manufacturer = #autoLOC_501646 //#autoLOC_501646 = Dinkelstein Kerman's Construction Emporium
    description = #autoLOC_500758 //#autoLOC_500758 = A Different Micronode
    attachRules = 1,0,1,0,0
    mass = 1.05
    dragModelType = default
    maximum_drag = 0.2
    minimum_drag = 0.2
    angularDrag = 1
    crashTolerance = 15
    maxTemp = 2000 // = 3200
    bulkheadProfiles = size0
    tags = #autoLOC_500759 //#autoLOC_500759 = build center central connect construct (core extend fabricate hub nexus node structur support
}

Link to comment
Share on other sites

Thanks, alright here's what I think, but I'm not sure, since I haven't been working with the localisationupdate. 
You see those #autoLOC_[number] parameters? I think those refer to a premade autLOC, when set to a different language, the description will change to that language. 
 

In a config, everything behind a //, won't be displayed or won't effect the config. So in this case, changing //#autoLOC_51646 = .... won't effect anything.
 

If you wan't to change the title and discription, it should look like this:

PART
{
    name = MyStructuralMiniNode
    module = Part
    author = NovaSilisko
    mesh = model.mu
    rescaleFactor = 1
    node_stack_right = 0.1823258, 0, 0, 1, 0, 0, 0
    node_stack_left = -0.1823258, 0, 0, -1, 0, 0, 0
    node_stack_back = 0, 0, 0.1823258, 0, 0, 1, 0
    node_stack_front = 0, 0,-0.1823258, 0, 0, -1, 0
    node_stack_top = 0, 0.1823258, 0, 0, 1, 0, 0
    node_stack_bottom = 0,-0.1823258, 0, 0, -1, 0, 0
    TechRequired = precisionEngineering
    entryCost = 9800
    cost = 25
    category = Structural
    subcategory = 0
    title = My Micronode
    manufacturer = #autoLOC_501646 //#autoLOC_501646 = Dinkelstein Kerman's Construction Emporium
    description = A Different Micronode
    attachRules = 1,0,1,0,0
    mass = 1.05
    dragModelType = default
    maximum_drag = 0.2
    minimum_drag = 0.2
    angularDrag = 1
    crashTolerance = 15
    maxTemp = 2000 // = 3200
    bulkheadProfiles = size0
    tags = #autoLOC_500759 //#autoLOC_500759 = build center central connect construct (core extend fabricate hub nexus node structur support
}

the #autoLOC basicly refers to another premade parameter in a different (central) file. 
 

Edited by DrLicor
Link to comment
Share on other sites

The best and most valuable thing you can do is to learn to use ModuleManager.  It will simplify this process, reduce clutter and save on storage space.

So, it looks like you are trying to replicate Parts/Structural/structuralMicronode/structuralMicronode.cfg

Install ModuleManager.

Open any text editor and past this"

+PART[structuralMiniNode]:FINAL
{
    %name = structuralMicroNode.cfg
    %author = Daveroski
    %title = My Micronode
    %description = A pint-sized Structural Micronode
    %rescaleFactor = 0.5
}

+PART, creates a new part based on the [partName]

:FINAL, make MM run this config after all others

%, edits a value if it exists or creates a new value

Note the rescaleFactor. Here, I'm assuming you are trying to make a smaller node

 

Create a directory in your GameData folder called My_MMConfigs

Save this as Filename: structuralMiniNode.cfg

Now, you have a 202byte file instead of a 95.6kB folder.

Result: Stock Structural Node on the bottom and the new Node on top.

ge1yQLw.png

 

ModuleManager wiki: https://github.com/sarbian/ModuleManager/wiki

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...