View Single Post
  #8  
Old July 2nd, 2009, 10:45 AM

RERomine RERomine is offline
Captain
 
Join Date: Oct 2008
Location: Columbus, Ohio
Posts: 975
Thanks: 1
Thanked 14 Times in 12 Posts
RERomine is on a distinguished road
Default Re: Objective Flag Values

Quote:
Originally Posted by Cross View Post
I manually adjust the v-hex values in every battle I set up. It only takes a couple of seconds if you change all to the same value.

The maximum value is 250 (IIRC) which x21 = 5250
.
That is certainly an option. I just figured some sort of programming approach would be more dynamic and user friendly. While I don't know how the code is set up, it might be possible to set it up so the are based on some percentage of the projected total force present. Since we don't know exactly how many points will be used, the best that can be done is basing it on the projected total. This projected total will be available before unit selection for main force in stand alone battles or support points campaign battles are used. I say projected points because you can never be sure someone will use all the points they have available for purchasing units. It is the only solid value available before the map complete with flags is available for view in the purchase screen.

The appropriate percentage would be subject to debate, but the general standard set by WinSPWW2 could be used. For grouped flags in a WW2 "meeting engagement", flags are 65 points each, giving each flag a value of .8% of the total force points based on 4,000 points for each side (8,000 total force points). If the total force points increase to 30,000 as very possible in an MBT battle, those flags would be dynamically set to 240 points each. This doesn't put the player into the position of having to determine the appropriate flag values to maintain the balance and significance intended in "meeting engagements".

It gets a bit more complicated if the objectives are scattered since they seem to run four different values: 95, 120, 220, 230. Percentages can still be used here as well. It's just a matter of calculating it out.

The value cap is somewhat constraining, but there isn't anything magic about the constraint. It is likely the constraint is based on the programming data type selected for the variable, but that data type could be changed as well. That's all up to the people with the source code to determine. From a programming perspective, it can be done. Pretty much anything can be done. It boils down to practicality, which is a question I can't answer without the source code.
Reply With Quote