When you automate anythng to do anything you're basically telling it to do what the AI would do with it, with certain objective parameters. It's possible the dogs aren't getting great odds or the AI just doesn't see the value in that attack as you do - perhaps because they'd use a different unit to attack with in that case. Generally, dogs are for spotting foes good at camouflage and mopping up battles, not starting them, but that does depend a bit on some option settings in use. In Uncut and non-SM games, they are strong enough usually to be a valid attacker so why they aren't choosing to attack would be a subject for deep study and analysis on a unit in a specific situation to walk through how the AI has processed the decision. It's all very mathematical and based on a lot of factors. Remember, a while back, Koshling added a 'what's the reward?' element to whether the AI would attack, as well as a 'will I likely be killed afterward, even if I win?' consideration, whereas standard Vanilla usually only asked, 'can I win this battle?' consideration, along with possibly, "if I can't win, will the rest of the units with me be able to follow up and win after this battle is lost?" segment to the equation.
He probably activated or left active "stay by hand" status - you can lose track on it when micromanaging a lot.
Possibly - it's not usually something that dogs end up selecting - certainly not by default. There ARE some failures to attack in the AI where it seems they should sometimes.
I prefer to commit stuff partially, as I never worked on events before
I have to admit that it was hilarious when a couple families of islanders isolated during millennia are able to grant you the knowledge needed to build antimatter rockets.
Well most advanced techs, that they could grant were in Atomic era, when I cleaned them.
<DefineName>FIRST_EVENT_DELAY_TURNS</DefineName>
<iDefineIntVal>20</iDefineIntVal>
- No events in first 20 turns (not sure if scaled for game speed).Is that really a good thing? I think we'd turned it down because it can too easily mean we get constant volcanoes going off and too common repeats of events given that there is such a limited number of applicable events that can happen.
I think problem with most common events is that they have bit high weight.
I reduced them from constant player gripes over them. And from own experience of getting the same one over and over. If you make events Too common then players will turn them off. They become an annoyance not something to "liven the play up".
I guess cooldown should be added to events so they wouldn't show up for a while after being triggered last time.
Well this stuff is random.
The relevant code is pretty far down in CvGameTextMgr::setPlotListHelp(...)
Yeah basically. It doesn't compile in at all when it says this. Basically, if this is false, and it always is, then ignore up to the endif. The reason for the difference there is because it's generally set aside to potentially refer to a variable that may actually be established as something - it's usually an edit process that sets this up with the ease of being able to turn it on, recompile, and run with the code included.
I see, then I may have been wrong about the code being awfully inefficient. ^^
alt+X is meant to plan your cities with, you can click a plot to set the fat cross on the map, as many as you want. It is remembered per game in the save file so you don't have to chart out every time you load a save.
