conquering cities option

[bill2505]

something like this would be great http://forums.civfanatics.com/showpost.php?p=9031051&postcount=4

 

[Dancing Hoskuld]

Can't be done in python in part because the change civic event is not 'exposed' to the python event handler. That does not put a stop to it though. I wonder why Afforess did not implement it? If he had we would have it also.

 

[bill2505]

Can't be done in python in part because the change civic event is not 'exposed' to the python event handler. That does not put a stop to it though. I wonder why Afforess did not implement it? If he had we would have it also.

ok. thanks for the answer. also in the future do you plan to create a future to do list.

 

[Dancing Hoskuld]

In theory that is what the discussion thread is about. If one of the modders decides t take it on they will usually make a new thread about that particular change to get more input and so on.

 

[Koshling]

In theory that is what the discussion thread is about. If one of the modders decides t take it on they will usually make a new thread about that particular change to get more input and so on.

I think I could add a change civic event fairly easily, but I'm not sure why you'd need one for this - surely you can just query the curent civics at the time of the city capture, or am I missing something?

 

[Dancing Hoskuld]

I think I could add a change civic event fairly easily, but I'm not sure why you'd need one for this - surely you can just query the curent civics at the time of the city capture, or am I missing something?

Only the BIG picture. Which you are probably not privy to. There are a whole bunch of things we could do 'if only' there was a onCivicChange event that provided the old and new civic. The BUG people keep saying that they will get around to it sometime but it is very low priority.

For example: currently you can capture slaves and they remain slaves for ever unless you build something with them, convert them to a one shot unit or settle them into a city.

If we had the onCivicChange then those slaves could also be put to work in the fields and when you change from slavery they could be changed into something else, eg one in two become a worker and the rest go "free". Thus removing the main complaint of having slaves when you aren't running slavery.

 

[Koshling]

Only the BIG picture. Which you are probably not privy to. There are a whole bunch of things we could do 'if only' there was a onCivicChange event that provided the old and new civic. The BUG people keep saying that they will get around to it sometime but it is very low priority.

For example: currently you can capture slaves and they remain slaves for ever unless you build something with them, convert them to a one shot unit or settle them into a city.

If we had the onCivicChange then those slaves could also be put to work in the fields and when you change from slavery they could be changed into something else, eg one in two become a worker and the rest go "free". Thus removing the main complaint of having slaves when you aren't running slavery.

Ok, I'll put it highish on my list then - likely about the next after next. I want to adjust war weariness and food wastage, plus look at the reported ctds and errors first.

 

[bill2505]

this mod ROCKS

 

[Koshling]

Ok, I'll put it highish on my list then - likely about the next after next. I want to adjust war weariness and food wastage, plus look at the reported ctds and errors first.

Damned iPad auto correct! I meant 'likely about the week after next'

 

[stolenrays]

The enslave/sack option exist in the sdk of AND, but I haven't gotten them to work. I have been really close and getting it to work though and have isolated the code for the sack option.