Sorry I've been MIA for a little while; I've only gotten to about 300 turns in a game with the dev version released prior to the current one - so no WTO yet... I was hoping to get some more stuff to comment on before posting, but the only thing I've found worth mentioning was the hammer increase for the forum: I thought it was a little too costly, but I see you have already lowered it! Most importantly, nothing seems broken or unbalanced with this build.
I do have a couple quick questions for you if you don't mind, however. I'm playing with the latest Balance - Combined mod, which has some interesting new features to CS diplomacy:
and
*Do you think these adjustments conflict with tweaks you made in CSD? Because I'm only getting quests from CSs who I already have relations with (Diplo unit only - the SP for 20 minimum influence didn't seem to affect this). I will also ask about this in the B-C thread.
*Also, obviously I'm not getting any kill CS quests because you have turned them off - what value should I enter into the XML to turn them back on (I tried 0 but that didn't work), or should I simply delete that line?
[EDIT: Never mind, both of these issues are resolved in the new game I started. 0 is the correct value, and I'm getting missions normally.]
Once I get these issues sorted out I'll test it and let you know if I think they should be incorporated here.
Cheers, keep up the good work
I like those additions. Killing the 'kill city-state' quest (appropriate?) was a stopgap attempt to keep 75% of CSs from wanting to kill other CSs. This made late-game quests almost always kill quests, thus ruining diversity. You did the right thing by setting the value to 0. You can also just erase the line, as redundancies might make the game sad.
It shouldn't conflict the only quest-related changes I made concerned the time between quests (making quests more frequent) and the disabling of the kill city-state quest. Everything else I did relates to CS AI and production capacity.
Let me know what you think perhaps a collaboration is in order with CCMAT (if he'll have me )
I was in quite a mountainous section of map so possibly. It was late game on a large map. 32 bit windows.
Let me know if it happens again. It might be a perfect storm of memory peak + erratic pathfinding. If anyone else see this problem, let me know and I'll just remove the hover command from the ambassador (no more levitating ambassadors? NOOO!)
(No, they don't really float).
Keep up the good work, guys!