[NoOne]

if you want to affect statistical output, you are better off adjusting the modifiers for that particular stat.

using "walks" as an example:

too many league wide? or... too many for an individual player? through you observations and personal preferences as to what is realistic/correct relative to your league's context.

one of those being accurate may not lend itself to the toher being accurate.. .which do you care about more?

if you see a value that is way to high for an individual, go ahead and tone down the Walk League Total Modifier (LTM) in Stats and AI settings. -- don't change the totals! use the modifiers.

if you do change walks, it will ikely affect other things related to # of walks per PA etc. keep eye out for additional adjustments teh next few years after any LTM change.

ie you increase walks, which reduces # of ab, so that likely increases BABIP or reduces hits... think it's the babip relative to how LT/LTM work, but proof is in the pudding.

-----------------
you could adjust ratings if you wanted to -- much more complicated and much less predictable results... start by export players to be used in a spreadsheet, apply a factor to the control rating column (one formula at top, then fill down in an empty column), replace that column, delete 'temp' created column for proper formatting, and re-import into game... can quickly add 5% to each players control rating or even using "IF" qualifications make it tiered... if between 0-50 only had 5%, between 51-150 add 10%, 151-200 add 20% etc... you could reshape distribution curve if you wanted to.

pretend the column being altered is "A"

in some empty column type this in the same row# as the top row of the data --

"=a1*1.05"

then "fill" down all the rows that exist in original A column... copy and 'paste special' - "numbers only" option over the original A column. it's now all 5% higher. delete the column you just created... save and re-import. mass adjust every single control rating of every single player in the game.

A DB program like Access/hiedisql can do this even more easily with a sql statement...