Quick question on client.cfg

[WangFeiHong]

strictly speaking, Is the editing of the client.cfg against the Folding@Home license? E.g. changing MachineID through client.cfg instead of -configonly

"You may not alter the software or associated data files."

[MtM]

I think it's more a question of if direct edits will always be fail safe. clients.cfg uses chr(10) as linebreak as opposed to chr(13) or chr(10) & chr(13) and it might confuse people trying to edit with notepad. Using the clients built in configuration options is just fail safe.

I think I was told it's also not allowed when I made a gui for editing settings for client settings which directly wrote to the cfg file but I'm not sure if I remember that 100% clearly, I do clearly recall the above as a strong point to discourage it as alternative. It's is an associated data file, even if it's not directly the targer of the statement I think ( that would afaik be more aimed at editing wuresults ( creating fake one's ) or altering the clients themselfs to prevent downloading newer core revisions for instance.

[toTOW]

Editing the config.cfg is not recommended because of the reasons described by MtM : manual edit often breaks the formatting, and resets client configuration.

[7im]

Strictly speaking, yes. Editing the client.cfg file is against the EULA. Use -config, or -configonly.