Amaroq
Posts: 1100
Joined: 8/3/2005 From: San Diego, California Status: offline
|
1. Not from within the game UI. 2. No - you can get them through 8 innings routinely, but the AI always wants to use a 'closer'. 3. No - except via starter association as you describe. Personally, I 'export' ballparks once I'm happy with them, so that I can import them to future associations. 4. See the face pack thread, I'm not sure re: stadiums. .... One thing you may want to play with is editing the puresim.xml file. I'd recommend making a copy, say 'campy.xml', and playing with that. You'll find many of the in-game AI decisions are 'exposed' in the .xml file. To address point #2, you would want to look for the "RECOVERY_PITCHER" tag; I found that raising that about 10 points helped pitchers go every 4th game instead of every 5th game. Likewise, if you wanted to adjust the frequency with which AI managers pinch hit, you might look at "BASE_PINCH_HIT_CHANCE_BY_INNING", "MIN_PINCH_HIT_INNING", "BASE_PINCH_HIT_CHANCE", and "CANCEL_PINCH_HIT_IF_AHEAD_BY". Getting back to #2, there's a "PITCHER_HOOK" entry which specifies how quickly or un-quickly managers bring pitchers out of games. If those names aren't intuitive enough, there are some great comments in there explaining what the entries do. .... I repeat again, make sure you don't modify the default puresim.xml file yourself, or have a backup copy out there - if you mess this file up badly, the game can crash on loading - but that said, its a text file, so you can edit it with WordPad or notepad, and you can play with a bunch of things. I'd also recommend not immediately starting to use your new .xml file with your beloved association - I typically run long unattended tests (set it on Autoplay when you leave for work, look at data when you get home) to see if I "like" what the changes have done. Some settings, even a subtle change can feel like 'too much', while on others you may find it takes large changes to make a measurable impact. Typically, I run the default .xml once, then run a (heavily) modified .xml once, and compare. With those baselines in place, I start 'tweaking' the modified .xml, modifying only one variable at a time and seeing what it does; usually the comparison data has given me an indication of whether changes to that variable should be large or small.
|