Quote:
Originally Posted by tysok
he hasn't been retired yet, going 2 for 2 with one RBI...
That's a hard code line. Most likely hard coded so it can be controlled better. So we wouldn't ever end up possibly with it saying he hasn't been retired yet, going 2 for 3. Or mentioning he has no RBI for the game.
Anaya is going home...
-----------
he scores...
-----------
Hunt has a double...
-----------
It's a two-run double by Charles Hunt.
Those are all hard code lines. There's not a whole lot of variation to add to that.
[228-11917] rips a liner...
over the third base bag...
McGilchrist is there...
The last 2 lines are hard code. Not much variation in the direction, the "is there" is a stupid line since he misses it 90+% of the time, but not much variation available for that type of play unless he's lunging or diving.
Most of the hard code is stuff that wouldn't have much variation, so it'd be calling from an xml category for no other reason than it isn't hard coded anymore, not for sake of variation. The downside is that the stupid lines can't get fixed unless Markus does it.
|
I understand what you are saying. And I'm sure Markus has a good reason to have hard-coded events in the game. But, just looking at what you posted here, all of these events could be in the XML file. The first example, just remove "he hasn't been retired yet." That's pretty obvious if in the XML you just say "Smith is 2 for 2 today with one RBI..." by using the right tokens. The other two examples seem to be events that are similarly covered already in the XML file, so I don't know what the purpose is of those being hard-coded.
Maybe I'm just too involved in this part of the game. I spent hours building a custom XML file for the last version that didn't work because of the hard-coded events. To me, hard-coded events are no different than a roster set builder finding out that no matter how they built a roster set, it would always include Barry Bonds, Roger Clemens, and Frank Thomas by default, with no way to modify or delete them.