The Altera Centauri collection has been brought up to date by Darsnan. It comprises every decent scenario he's been able to find anywhere on the web, going back over 20 years.
25 themes/skins/styles are now available to members. Check the select drop-down at the bottom-left of each page.
Call To Power 2 Cradle 3+ mod in progress: https://apolyton.net/forum/other-games/call-to-power-2/ctp2-creation/9437883-making-cradle-3-fully-compatible-with-the-apolyton-edition
Doh! well serves me right for digging up an old thread! Still ds-5-li(sorry for the errors!) geezer was having a problem with an apolyton mod still causeing this error, and it comes up from time to time - i guess it must be with the older Mods? This crash and the ex-city tile pillage crash are probably the most annoying bugs, especially in MP.
Still nice to know it's fixed now in Craddle
thanks to Locotus for the link to this
Hexagonian, what was the final workaround for this and anychance of it making it into the next Craddle update?
I take it it all worked fine?
And nice work Spanscape and Dale(now departed, sniff).
- The InitDiplomaticState directs the AI's diplomatic stance to the new modified ones I'd written right from turn 1. By default, the AI will always select one of the original diplomatic settings. My code put it into the better ones.
- The NextDiplomaticState is the check to keep the AI player in the new diplomatic states.
- If a new AI is formed due to conquest, it'll automatically select one of the default diplomatic stances. On it's first diplomatic check it'll run NextDiplomaticState and be forced into the new diplomatic states.
I see no problem with an AI running the default states for a few turns. It won't have an impact as I modified the default states to very close to warmonger state.
Looks good, Dale's reasoning seems perfectly sound. Why it should be crashing when it creates a new civ is really puzzling.
To be on the safe side, it's probably a good idea to remove the ChangeDiplomaticState calls from the NextDiplomaticState event handler. They did say:
Do not call the ChangeDiplomaticState function from within these handlers; it will be called after all handlers have been executed and cause a change to the one with the highest priority.
Good stuff, guys. Careful about getting hooked on this, Scanscape. It's argueably more fun than playing games but can take up a lot of time.
At the start of the InitDiplomaticState function, add this line in:
Code:
HandleEvent(InitDiplomaticState) 'DIP_InitDiploState' pre {
if(g.year > 1) {
DisableTrigger('DIP_InitDiploState');
} else {
...... Current code goes here .......
} // Don't forget to add another of these at the end of the function.
My reason for this is that when a Civ is destroyed, it'll create a new one (if MaxPlayers > NumPlayers in userprofile.txt). When it creates a new Civ it'll probably run InitDiplomaticState (it's logical to do this). The function doesn't crash at the beginning of the game, so it works on turn 0. It may be crashing in later turns. This code will only allow the script to run on the first turn of the game (thus setting up the diplomatic stances).
Here's an interesting thought. According to the SLIC documentation, InitDiplomaticState is only called at the start of the game to initialise the AI's original diplomatic states. During the game, NextDiplomaticState is called.
The initial diplomatic state record load for a player can be redefined by writing a SLIC function that handles the InitDiplomaticState event and calls ConsiderDiplomaticState followed by a call to ChangeDiplomaticState. For example:
HandleEvent (InitDiplomaticState) ‘Example_DiplomaticStateInit’ post {
// player[0] is the player being initialized
// player[1] is the foreigner
// code that ends up calling ConsiderDiplomaticState
// code that calls ChangeDiplomaticState
}
At the beginning of every turn the NextDiplomaticState event will be triggered for every foreigner that has been contacted. You can define SLIC functions to handle this event and change which diplomacy record should be loaded by calling the ConsiderDiplomaticState function. Do not call the ChangeDiplomaticState function from within these handlers; it will be called after all handlers have been executed and cause a change to the one with the highest priority.
HandleEvent (NextDiplomaticState) ‘Example_NextDiplomaticState’ pre {
// player[0] is the player being whose turn it is
// player[1] is the foreigner
// code that ends up calling ConsiderDiplomaticState
}
Doh! well serves me right for digging up an old thread! Still ds-5-li(sorry for the errors!) geezer was having a problem with an apolyton mod still causeing this error, and it comes up from time to time - i guess it must be with the older Mods? This crash and the ex-city tile pillage crash are probably the most annoying bugs, especially in MP.
Leave a comment: