You will never write a new parameter file from scratch. Typically, you take an old file (e.g. the one controlling the simulation which produced the model which is used to start the new run) and edit it:
character descriptionarray (Sect. 220.127.116.11). You might add a remark about the parent file of the parameter file under construction and the current date into the
character history(Sect. 18.104.22.168) array in the header (see Sect.7.1.2).
outfile_mean(Sect. 22.214.171.124), etc. On a system with batch queue this has not to be done in the parameter file itself but in the external command file (see Sect.7.1.21).
LuminosityPerVolume(Sect. 126.96.36.199), ...
mass_star(Sect. 188.8.131.52), ...
opafile(Sect. 184.108.40.206). Check the paths
eospath(Sect. 220.127.116.11) and
u=cm(see Sections 7.1.20 and 7.1.21).
Of course, a complete control of CO5BOLD is only possible after studying of the meaning of the parameters in detail (e.g. by reading the following pages) AND - unfortunately - an accompanying look into the source code itself.