Config File Issues ComputerCraft 1.33

I'm trying to do a very large project in tekkit classic, and the standard range for the modems doesn't work me, so I decided to change the config file to allow for a greater distance with less need for relay computers(I also wanted to change the terminal color, but that's not super important) My current problem is that whenever I change the config file it always ends up changing back to the defaults whenever I load up my classic tekkit installation. I've included what I'd like the settings in the file to be below, along with what they keep changing back to.

My desired settings:

#MLProperties: name (type:default) min:max -- information
#MLProp : computerBlockID (int:207)
#MLProp : diskDriveBlockID (int:208)
#MLProp : diskItemID (int:4000)
#MLProp : enableAPI_http (int:0)
#MLProp : terminal_width (int:50)
#MLProp : terminal_height (int:18)
#MLProp : terminal_textColour_r (int:0)
#MLProp : terminal_textColour_g (int:255)
#MLProp : terminal_textColour_b (int:0)
#MLProp : modem_range (int:512)
#MLProp : modem_rangeDuringStorm (int:512)
#
#Wed Jun 04 13:21:22 EDT 2014
terminal_width=50
terminal_textColour_g=255
modem_rangeDuringStorm=512
computerBlockID=207
diskItemID=4000
diskDriveBlockID=208
enableAPI_http=0
terminal_textColour_b=0
checksum=440
terminal_textColour_r=0
modem_range=512
diskDriveGUIID=100
terminal_height=18

And the default:

#MLProperties: name (type:default) min:max -- information
#MLProp : computerBlockID (int:207)
#MLProp : diskDriveBlockID (int:208)
#MLProp : diskItemID (int:4000)
#MLProp : enableAPI_http (int:0)
#MLProp : terminal_width (int:50)
#MLProp : terminal_height (int:18)
#MLProp : terminal_textColour_r (int:255)
#MLProp : terminal_textColour_g (int:255)
#MLProp : terminal_textColour_b (int:255)
#MLProp : modem_range (int:64)
#MLProp : modem_rangeDuringStorm (int:16)
#
#Wed Jun 04 13:21:22 EDT 2014
terminal_width=50
terminal_textColour_g=255
modem_rangeDuringStorm=512
computerBlockID=207
diskItemID=4000
diskDriveBlockID=208
enableAPI_http=0
terminal_textColour_b=0
checksum=440
terminal_textColour_r=0
modem_range=512
diskDriveGUIID=100
terminal_height=18

Any help is greatly appreciated, thanks.

Both provided configs have modem range set to 512. Values after a hashtag (#) are comments and changing them doesn't change anything. Only the values that doesn't have a hashtag before them are being read as a config parameter.

So then I'm not sure I understand, A. Why wouldn't it be working then, B. Why would the game make an effort to change the config files comments back to there original values, and not the values that are supposedly being read?

#MLProperties: name (type:default) min:max -- information
#MLProp : computerBlockID (int:207)
#MLProp : diskDriveBlockID (int:208)
#MLProp : diskItemID (int:4000)
#MLProp : enableAPI_http (int:0)
#MLProp : terminal_width (int:50)
#MLProp : terminal_height (int:18)
#MLProp : terminal_textColour_r (int:0)
#MLProp : terminal_textColour_g (int:255)
#MLProp : terminal_textColour_b (int:0)
#MLProp : modem_range (int:512)
#MLProp : modem_rangeDuringStorm (int:512)
#
#Wed Jun 04 13:21:22 EDT 2014

does exactly NOTHING. It's just there to be pretty. I assume it simply overwrites it every time they load the config, for what reason I have no idea.

terminal_width=50
terminal_textColour_g=255
modem_rangeDuringStorm=512
computerBlockID=207
diskItemID=4000
diskDriveBlockID=208
enableAPI_http=0
terminal_textColour_b=0
checksum=440
terminal_textColour_r=0
modem_range=512
diskDriveGUIID=100
terminal_height=18

This stuff is what you want to change…

brad95411, on 04 June 2014 - 09:52 PM said:

A. Why wouldn't it be working then

I guess it does, both configs are exactly the same (not talking about comments).

brad95411, on 04 June 2014 - 09:52 PM said:

B. Why would the game make an effort to change the config files comments back to there original values, and not the values that are supposedly being read?

Maybe it's so if you would ever want to change the configs back to their original values, you would always find them in the comment.

MKlegoman357, on 04 June 2014 - 10:35 PM said:

brad95411, on 04 June 2014 - 09:52 PM said:

B. Why would the game make an effort to change the config files comments back to there original values, and not the values that are supposedly being read?

Maybe it's so if you would ever want to change the configs back to their original values, you would always find them in the comment.

it doesn't actually deliberately change it back its the way the config files are parsed and saved. iirc when the config files are parsed it doesn't bother saving the comments and default values ('cause what's the need) because when the mod asks for values from the config file it must supply a default value and a comment for the value, meaning it gets the details from that, so when it saves the config it would change the comment and default value from what you supplied to what the mod supplies.

but as MKlegoman357 and KingofGamesYami have said you need to change the values towards the bottom of the config that don't have a hash (#) at the start of the line.