No.  You can't.

If you have ever done programming before you know that one tincy wincy fix will break an entire project. It may take time but these things are worth the wait. 

@Dangerlinto, Try reading the original post again, the subject is based around the AI ignoring these rules, so while you can change how the rules work, it wont matter since the AI will still ignore them.

Sincerely
~ Kongdej

I'm quite optimistic that Frogboy will fix this soon as he's stated it needed fixing, so it's on the radar.  Sounds like him and Kael have been flat out getting the LH beta ready, but once that's out... hopefully they can sort this one out for us in the 1.4 patch.

But yeah, understand your frustration... it's at the top of my list of annoyances too.

StevenAus-

Care for some cheese with that? 

The fix is likely going to be the removal,of the 5 turn wait for the human which can be done in elementaldefs.xml

Well anything else is going to take a lot of work. So if Im going to do that I'd want something better tha the 5 turn thibe.

Just occured to me in Civ 5 razing a city would take 2000 years or so if done early on. My army is lazy...pulls out the whip.

I'd *like* to see it where you raze a city and it takes N turns where the turns are 3 per level and each turn results in the destruction of improvements and such.

But that would be a lot of work (not by me of course).  So it's not likely to be done as it would mean cutting some new feature out of LH (it's a zero sum budget).

I think 1 turn razes are perfectly fine.  Not ideal. But good enough.  They were only made 5 turns later to help the AI. But the AI is a lot better now than it was back then.

Maybe something like

for x= 1 to numOfBuildings {

    cityHp += building(x).productionCost

}

cityHp*=cityLevel

if (isBurningDown == true) then

    damageDoneToCity = garrisonedTroop Attack Power * 10

   Look at a sorted list of buidling and from the highest production cost down to the lowest pay back the damage with building to destroy them

}

}

I donno thats rough and ugly and maybe even makes no sense but then you slowly destroy buildings unless you ahve a big army there speeding up the process Also its not entirely random

Yeah that idea was not something that I'd expect in the near future. Was kinda bored at this contracting job, call center with no inbound calls and management recommend we read a book or something, so figured I could try fleshing out an idea for fun. 

That's not how it works.

The AI has to play by the same rules in virtually all cases.  The only time that isn't the case is where a game play rule is implemented at the UI level rather than at the game level.  Generally speaking, we try to avoid this sort of thing precisely because it causes the kinds of problems we're discussing.

So in this case, the Raze City *button* has an IF statement on it that determines if it's enabled or not.  The AI does not.  But the AI only evaluates whether it should raze a city at the time of conquest.  

However, late in the beta, it was decided to change it to require a 5 turn minimum and it was implemented as a UI restriction on the player.