So, currently it seems that the objects score values are provided in one class (ScoreRegister.class), read by World.class.
To introduce flexibility for mission designers, it would require to read a new parameter that could specify a particular score value for whatever assests are desired, as written in the .mis file. If no value is supplied here, the default value from ScoreRegister.class would apply. Or the.mis file has all objects given a score value, whether 'custom' or default.
The code reading the .mis file must be backward compatible for older files having no score values present.
A first notion that comes to me, for a flight in the .mis file:
[11GvIAP12]
Planes 4
Skill0 3
Skill1 2
Skill2 1
Skill3 3
Score0 160
Score1 80
Score2 40
Score3 140
Class air.P_39N
Fuel 100
weapons default
Now, the trick is keeping track of the score value for each object individually. I'm not sure how to do this, as I'm a Java chimp.
Would it require to create an array? Don't know!
An additional element of concern. Making edits manually to the .mis file would be the least troublesome approach initially. Ultimately, the GUI for object creation should include a new field in which to enter a score value (a selection item could be for the "default" value, as read from ScoreRegister.class, perhaps.)
For non aircraft objects, an additional score value would have to be added in the .mis file. For instance chiefs and stationary could have the score value appended to the existing entries as follows:
[Chiefs]
0_Chief Vehicles.OpelBlitz6700A_fuel 2 50
1_Chief Vehicles.OpelBlitz6700A_fuel 2 40
2_Chief Vehicles.OpelBlitz6700A_fuel 2 40
3_Chief Vehicles.GermanyCarsColumnE 2 80
4_Chief Vehicles.OpelBlitzMaultierAA 2 60
[NStationary]
39_Static vehicles.artillery.Artillery$Flak30_20mm 2 72967.19 146773.64 480.00 0.0 0 60
2_Static vehicles.planes.Plane$BF_109G6 2 20431.65 154445.76 495.00 0.0 null 50
8_Static vehicles.stationary.Stationary$OpelBlitz6700A_fuel 2 20359.22 154434.66 465.00 0.0 60
A last concern, for the moment, at least. The scoring scheme presumably (?) must be compatible with campaign requirements as regards winning or losing.
All this is an area about which my understanding is weak. More knowledgeable peeps would be better equipped to dealing with the nitty gritty.