Some ui improvements for the particle editor would help. Being able to select from a drop down box, or a list of icons would be much faster for selecting sprites or colors (rather than having to click through each one). Also, many of the white or lighter color sprites are on a white background which makes them more difficult to recognize.

Well, it might work but then you could only save a tile if it had a hull type and engines...

lol Functionality of the designer man.

Also, scripting support for random events (with "response choices") a la FFH2!

More improved tutorials always help.

Or add a manual edit (text box) to fine tune the tile.

Speaking of CurrentHealth... what about MaxHealth?  AFAIK that isn't even accessible with spells.

That would be a critical item for creating heal spells that work.
I mean technically the current heal spell works but healing a 1200 HP unit for 12 HP per spell gets old really fast.

So heal spells should heal  ( x% of MaxHealth ) + (fixed amount as it does now)

The things I most want to see are copy functions in the builder forge and cauldron, and a test map/ console function to place a tile (modded ones specificly) for testing.  The ability to scale objects out of starting proportion would be great too. 

I do like the no clipping on objects though as it allows for some neat effects when hiding undesired parts of an object.

While this does not concern the process of modding, it's a requirement (IMO = ) before wild and crazy spell effects can be coded.

What I'm asking for is an   event / trigger system   that can ideally be used from the spell XML files.
Usually that would be used in buffs / debuffs, doing... stuff... depending on certain triggers.
   Example:  A buff (or magical sword internal effect) that has a 10% chance per swing to cast a firebolt on the target.

In MMO lingo that's a proc (process). A buff could have one or more effects, triggered like...

• ProcsOnMelee
• ProcsOnRanged
• ProcsOnSpellCast
• ProcsOnGetHit  
• ProcsBeforeDeath
• ProcsAfterDeath
• ProcsOnMovement
• ProcsOnWearOff 
• ProcsOnEnter  (Trap spells)
• ProcsStartOfTurn   (aura)
• ProcsEndOfTurn

I have posted this before so I'll skip lenghty details and explanations here.

Even if such things could later be "Python scripted" the hard way, an event / trigger system is usually far more efficient and reliable when done by the engine.
Scripting an entire event handler is also not everyone's cup of tea, which would limit what many can do with the engine.
Modders with crazy ideas and serious coding skills aren't that common. In the entire X3 community I'd guesstimate that there are 6-10 and that's a very well documented script language by now.

Two more requests concerning problems that are appearing. I've chatted with Cari_Elf about it, but I think it can't hurt to repeat them here. They are both in regards to compatibility between mods, and won't only affect just one mod but rather deal with how mods interact with each other.

First, I would like the in-game research windows to only show unlocks for technologies that will actually affect the race researching the technology. For example, if I hook in a completely new elf only building to a standard kingdom technology, it will show up for everyone. I would like it to show up for noone but elves, if the the building has a prereq for race: elf. If this was done, we could hook an entire custom race to the standard tech tree, instead of having to build a completely new tech tree. This in turn will make it easier for others to mod the single tech tree, instead of having to deal with one for each custom race. Note that buildings are only an example, the problem extends to weapon and armor and equipment too.

Second, I would like a way to link modeltypes, or a way to modify instead of overwriting itemtypes. The problem is that each armor piece contains a list of supported modeltypes. However, if I am making a new race I need a new modeltype as I want new skins to be used. Now, currently, I must copy ALL the armor pieces for a new race, even when I want to use only the standard ones. Again, this will make it very hard for mods to interact with each other. If I introduce 3 races like this, then someone wants to change one armor value, he will need to change 4 itemtypes, instead of just 1. Solutions: Either allow us to modify itemtypes, like we do with improvementtypes (NOTE: it must be an OPTION! not always modify). Or, allow us to somehow link one modeltype so that it is nothing but a reference for other modeltypes. For example, I would declare that NewModelType == KingdomFemale. Then, any armor that contains a supportedunitmodeltype KingdomFemale would also support NewModelType.

Edit: Note that BOTH these fixes would be needed. On their own, they will provide very little benefit to improving how mods interact.

I would like <SpellResourceCost> to actually CHECK if I have the resources available in tactical combat. It loses half its functionality if it is just ignores the check in tactical combat. In strategic mode it works flawlessly.

Also, I would like a dev to take a look at Sion_Head in CoreFaces.xml and explain why it is getting applied to ALL custom modeltypes. If there's a reasoning behind it, please let us know. If there is no reasoning, please remove that functionality.

Requests.

First, I would like a way to demand, for an improvement, that another improvement has been built previously in the city.

For this we have

but this does NOT check world resources that have constructed buildings on them. The functionality should be, for example: If there is a FARM linked to one city in particular, then I can build a granary. The obvious solution is that you extend the functionality of the current tag (as above) to include resource buildings built "outside the city walls" but "inside the city influence", ie buildings that are linked to the city but not directly adjacent.

Secondly, it would be helpful if there was a tag to turn improvementtypes into mutually exclusive buildings. For example, I could have a CHOICE of building a War College, or building a Sion training facility. I would recommend that the tag be fairly simple, for example: <CityCannotHaveImprovement>. I would also like to see this tag be repeatable, so that we may choose between three or more buildings to be exclusive. Ps. Ideally this tag, too, should read from the resources linked to the city as well as the buildings within the city.