I haven't followed Clash's development for some time, so this may be completely redundant. Any pointers to previous discussions/definitions of the macro language will be appreciated.

I've been experimenting with an XML-based app for a few weeks, and I've become convinced that XML is quite useful for data.

But I'm not convinced yet that I'd like to use it for a macro language, or rather: I'm not so sure if I'd like to actually write anything in that language.

Anyway, I like the idea from a "cool, let's see if it works"-perspective, and I couldn't stop myself from brewing up a few examples of what I imagine an XML-based macro language to look like

(Sorry, no DTDs or implementation details for these examples)

<!-- 
This event will create the Angry Mothers civ in 20,30 and give the
Nasty Evil Buggers 1000 monetary units and the Evil Empire tech 
if the Nasty Evil Buggers conquer the Really Important Province 
before 1230 OR if the Annoyingly Good Guys are destroyed before that same year
-->
<event type="one-shot" >
  
  <cause>
    <any>
      <province-conquered>
        <province>Really Important Province</province>
        <conqueror>Nasty Evil Buggers</conqueror>
        <turn comparator="<" >1230</turn>
      </province-conquered>
      <civ-destroyed>
        <civ>Annoyingly Good Guys</civ>
        <turn comparator="<" >1230</turn>
      </civ-destroyed>
    </any>
  </cause>
  
  <effects>
    <create-civ>
      <name>Angry Mothers</name>
      <population>100</population>
      <location>20,30</location>
      <otherParam>Blah blah</otherParam>
    </create-civ>
    <give-to-civ>
      <civ>Nasty Evil Buggers</civ>
      <gift>
        <money>1000</money>
        <tech>Evil Empire</tech>
      </gift>
    </give-to-civ>
  </effects>
  
</event>

Is the above example intuitive? ugly?

Procedures with conditionals, loops, and such may be a bit more complicated. I'm not satisfied at all with the below attempt.

Boy, is F_Smith gonna love this

I think its both reasonably intuitive And ugly. I think it would be a Real pain to program in, but admire your inquisitive spirit .

I bring this up because if I (and most others in our target market) have to write macros such as the ones mca demonstrates above.....well. Either I'll go to coding school or shoot myself, whichever is easier.

This is NOT a plea to "dumb down" the power of our macro language, but it has to be easy to use. Couldn't we create some type of "Macro Generator" which involves selecting options from a menu, and let THAT create the code? If we make the macro language invisible to the average user, we'll have a gone a long way to ensuring a long and vibrant life for the game of Clash.

Good scenario generation is indeed a major selling point for a civ-like game, and we need to do it well IMO. Don't worry. I too think we need a versitile editor program that will allow a scenario designer easy access to all the variables, descriptions, and graphics that they might want to change. I think most people would agree on this. Since most scenarios are still using the main game functionality with a new map layout, civs, new military units and graphics, an editor is more appropriate.

The macro language is Only for the hardcore sorts who want to Really change things like scripting detailed civ behaviors, changing AI, or altering the basic flow of the game.

LOL. I try to follow the flow of the rutins. I have a couple of years experiment with different program languages, but this was quite criptic even for me.
IMHO the macro language must be something really popular like C or Pascal. I already sent a few ideas in my post "Macro Language Description". Please read it and comment it.

Meanwhile, I've had a look at the Macro Language Description thread, and I'll probably comment there later.