Part CFG question

[Daveroski]

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?

 

 

[DrLicor]

Could you upload the CFG and some screens of the situation how you've placed the files etc.

[Daveroski]

Was something about my explanation of the problem unclear?

 

 

[DrLicor]

No not at all. But by uploading the config text, we can look into it if you have overseen things.
It's earier to see those things with your situation in front of us, while so remote.  

[Daveroski]

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
}

[DrLicor]

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 January 19, 2018 by DrLicor

[Daveroski]

So get rid of the #autoLOC and get rid of the problem.. ok. Cheers

 

[DrLicor]

Just now, Daveroski said:

So get rid of the #autoLOC and get rid of the problem.. ok. Cheers

 

exactly, at least, I'm 90% sure that that will solve the problem.   Good luck modding.  

[Daveroski]

Ok tested that.. seems to be working as expected. cheers.

 

[TranceaddicT]

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.

 

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