Age of mythology how to download mods

1) What is Proto Editing?

Proto editing is editing the proto(x).xml :D
In the proto(x).xml you will see a long list of tags that might make no sense to you at all. All you need to know for now is that in this list you can find all the units of AoM(TT). Each unit has a standard format, it starts with an opening tag <unit [data]> and ends with a closing tag </unit>. Everything in the Proto works with opening and closing tags and if one of the two is missing then the Proto will be invalid. Everything in the Techtree works with opening and closing tags and if one of the two is missing then the Techtree will be invalid. Between the <unit> tags there are a lot of other tags and most of them are important. Editing those tags or adding another Unit is what's called Proto editing.

2) What is possible with Proto editing?

A lot! Every unit in the game is defined in the Proto. That means that you can create a new unit or modify every existing unit! What you will achieve with this depends on how experienced you are. With this guide I will try to explain everything I know and that will make you atleast an intermediate Proto editor but first, what is possible with Proto editing? A lot and it would be impossible to write down everything that is possible, even I don't know everything! So instead I will tell you some things that are impossible with Proto editing:
- Everything is static in the Proto.
What I'm trying to say with this is that unit's can not change other units' data values. This has a few exceptions though, actions like Boost do modify other units stats but the only stats that can be modified are: speed, attack. The only action that can be modified is the RangedAttack just think of the docks in AoMTT they can only attack when something is garrisoned inside.
- The Proto can't effect other data types.
Unlike the Techtree, the Proto is unable to change anything outside the Proto. Things like Techs can't be modified by the Proto but the other way around is possible.
- There might be more eventually

3) When should I use the Proto?

If you want to create a new unit or modify an existing unit you will have to use the Proto. If you want to edit Technologies you will also have to use the Proto but you won't have to edit it in most cases.

If you're thinking like a noob Proto editor:
You can't think yet ;) only dream!

If you're thinking like an intermediate Proto editor:
What if I want to create a unit that becomes stronger every age up? Easy just combine the Proto and Techtree!

If you're thinking like an expert Proto editor:
What if I want to create a unit that changes the lightning of the map upon attacking? Throws bombs that cause the enemy to get stuck for a while? Archers and siege on walls? No problem! Just Combine the Proto and Techtree!

If you're thinking like a god Proto editor:
What if I want to create a unit that throws bombs that will knockup the units hit in an area? Raises the land upon command? Will be hard but with the combination of Triggers, Techtree and the Proto it will work!

Now if you understood everything so far (or almost everything) then I will start to explain what everything does in the Proto.

) The Variable Values

Every unit has atleast one variable value.

<EditorNameID>Number</EditorNameID>
Same as the <displaynameid> but then it will be the name in the editor list.
#Not modifiable by techs

<footprint>Unit Name</footprint>
The footprints a unit leaves behind when walking. Units spawned as footprints are visual only as they do not influence the game in any way. For this we thank microsoft because this makes certain things impossible or just really hard to do.
#Not modifiable by techs

<CreationFadeTimeFootprint>Number</CreationFadeTimeFootprint>
How long the fade in of the footprints are.
#Not modifiable by techs

InitialResourceExcludedBy maybe separated

<icon>File Name</icon>
This defines which texture is displayed when you train the unit. It also is the small icon when you select a unit.
There are a few similar tags:

<cultureicon civ="Culture Name">File Name</cultureicon>
This defines the same things as the <icon> tag does but it looks at the player's Culture to define what icon is displayed. Note that microsoft wasn't really consistent as it says "civ=" and "civ" stands for Civilization. A Civilization in AoM is a god and not a Culture, which is Greek, Egyptian, Norse, Atlantean, so don't get confused by their naming of tags.

<portraiticon>File Name</portraiticon>
This defines which textures is displayed when you select a unit. It's the big icon in that case. A more advanced version is:
<portraiticon civ="Culture Name">File Name</portraiticon>
Defines the same thing but now checks the Culture of the player (again civ = culture in this case) so you can have 4 different icons for one unit that change depending on what culture the player is.

Icons are:
#Not modifiable by techs

<containedattack></containedattack>
This defines the attack that is added when this unit garrisons into another unit.
#Not modifiable by techs

<MaxContained>Number</MaxContained>
The maximum number of units that can garrison inside.
#Never tried to modify this, it might be possible.

<ContainedSpeedBonus>Number</ContainedSpeedBonus>
How much speed the unit will add to the unit it garrisons inside.
#Not modifiable by techs

<ContainedAttack>Number</ContainedAttack>
How much Attack the unit will add to the unit it garrisons inside.
#Not modifiable by techs

<BirthReplacement>Unit Name</BirthReplacement>
This one is interesting and I use it quite often. It tells the game to spawn another unit on creation of this unit. Be careful tho do not create infinite loops like a hoplite with a hoplite birthreplacement. If you really want something like that do it with a connector (A unit in between) or use the Techtree.
#Not modifiable by techs

<DeadReplacement>Unit Name</DeadReplacement>
Similar to the <BirthReplacement> tag but instead of spawning a unit on creation this will tell the game to spawn a unit on the death of this unit.
#Not modifiable by techs

<AllowedCulture>Culture</AllowedCulture>
The tag name is what it does. Only the culture define will be able to built this unit. A somewhat special tag if you think about the structure of the data.
#Not modifiable by techs

<initialhitpoints>Number</initialhitpoints>
<maxhitpoints>Number</maxhitpoints>
Example:
<initialhitpoints></initialhitpoints>
<maxhitpoints></maxhitpoints>
These define the hitpoints of a unit. Initialhitpoints is the hp the unit will have upon creation and maxhitpoints is what it says, the max hitpoints a unit can have. If you set the initialhitpoints to 15 the unit will start with 15 of 20 hp.
<initialhitpoints></initialhitpoints>
<maxhitpoints></maxhitpoints>
#Modifiable by techs

<los>Number</los>
This defines the LoS (Line of Sight) of a unit. Not really special or something just know that if you set it to 0 the game will take that as a no LoS and techs won't be able to modify it.
#Modifiable by techs

<SocketProtoUnit>Unit Name</SocketProtoUnit>
This tells the game that it requires a Socket unit to be built on. An example of this is the settlement. Cool things can be done with this but I think some stuff here is buggy but I'm not sure what it was because it was too long ago.
#Not modifiable by techs

<ProjectileProtoUnit>Unit Name</ProjectileProtoUnit>
This defines the projectile the unit will firing when using a Rangedattack or ChargedRangedAttack
#Not modifiable by techs

<obstructionradiusx>Number</obstructionradiusx>
<obstructionradiusz>Number</obstructionradiusz>
The obstruction radius of a unit. I'm not % but if a unit is a building the obstruction is a square and if it is a unit it is round. You have to know that the y and z are swapped in AoM and the x is width and z is length.
#Not modifiable by techs

<ObstructionRadius>Number</ObstructionRadius>
Another obstruction rad
#Not modifiable by techs

<soundvariant>SoundType</soundvariant>
This determines which sound will be used if the units hits a target with a projectile.
#Not modifiable by techs

<ballisticsplashproto>Unit Name</ballisticsplashproto>
This defines the unit that is spawned upon impact on the ground. Most of the it's a small dust cloud. Again thanks microsoft for this visual only unit :S
#Not modifiable by techs

<ballisticbounceproto>Unit Name</ballisticbounceproto>
Same as the one above but then the unit will appear when the projectile bounces.
#Not modifiable by techs

<formationcategory>Protected, Body and some others</formationcategory>
This has to do something with the formations of Age of Mythology.
<maxvelocity>Number</maxvelocity>
This defines the speed of the unit. Same as with LoS if you set it to 0 the game will take that as no Speed and techs won't be able to modify it.
#Modifiable by techs

<movementtype>Land, Water, Air</movementtype>
This tells the game on what type of land a unit can move. The types are obvious. Land = only on land, Water = only on water and Air = Terrain is ignored. Note that there is no amphibious movementtype or terrain type and thus it has been impossible for anyone to make a full amphibious unit.
#Not modifiable by techs

<turnrate>Number</turnrate>
This defines the speed of the rotation of the unit. If it is too low and the speed too high units are able to walk off the map.
#Not modifiable by techs

<TurnRadius>Number</TurnRadius>
This defines the radius of the rotation of the unit. Another way to make sure you unit walks off the map.
#Not modifiable by techs

<UnitAIType>AI Type</UnitAIType>
Defines the AI the unit will be using. If you do not use it then it will default to Passive. You can define your own AI types in the vtigerxabier.esy.es
#Not modifiable by techs

<ProjectileSpinPeriod>Number</ProjectileSpinPeriod>
This defines how long the projectile needs to make a single rotation.
#Not modifiable by techs

<ResourceSubType>Number?<ResourceSubType>
I'm not sure, never used it, never saw it being used and I'm not sure if it works but if it does it might define the second resource type a unit is carrying.
#Dunno if it is possible to modify this with techs.

<AutoAttackRange>Number</AutoAttackRange>
Normally the auto attack range is defined by the LoS of the unit. If you add this tag to the unit, this will define it.
#Not modifiable by techs

<ResourceDecay>Number</ResourceDecay>
This tag tells the game how much of the resources are lost per second when for example a deer is killed.
#Not modifiable by techs

<buttonpos row="x" page="x" column="x"></buttonpos>
Should not have an effect anymore, maybe it did in the beta.
#Not modifiable by techs

<MinimapSize>Number</MinimapSize>
The size of the unit on the minimap.
#Not modifiable by techs

<MinimapShape>A shape<MinimapShape>
The shape of the unit on the minimap. Dunno what shapes are allowed
#Not modifiable by techs

<BoredTimeout>Number</BoredTimeout>
Never used it
#Not modifiable by techs

<IdleTimeout>Number</IdleTimeout>
Same as above
#Not modifiable by techs

) More Variable Values

<WanderDistance>Number</WanderDistance>
This tells the game how far a unit can wander. When a unit Wanders it moves around like a wild animals do.

<AllowedHeightVariance>Number</AllowedHeightVariance>
This tells the game to check how rough the ground is before you can place a building.
#Not modifiable by techs

<initialunitaistance>Aggressive, Defensive, Passive</initialunitaistance>
This defines the unit's initial AI stance.
#Never tried to modify it

<lifespan>Number</lifespan>
This tag defines the lifespan of a unit. There is one problem with transforming units that have a lifespan. If you transform a unit that has a lifespan it will be transferred to the transformed unit in other words, there is no escaping from this tag.
#Modifiable by techs

<buildingworkrate>Number</buildingworkrate>
The rate at which trainpoints, researchpoints are points? dunno how to say it really haha, just know that the way to calculate the times is points/buildingworkrate

<trainpoints>Number</trainpoints>
This tag defines the trainpoints of a unit. Most of the time Trainpoints are 1 per sec but this depends on the buildingworkrate tag.
<cost resourcetype="Food, Wood, Gold and Favor">Number</cost>
This defines the cost of a unit. First value is the resourse type and the second is the amount.
#Modifiable by techs

<RolloverUpgradeAtID>String number</RolloverUpgradeAtID>
Info about where you can upgrade the unit. This is shown when you rightclick the portrait of the unit.
#Not modifiable by techs

<RolloverCounterWithID>String number</RolloverCounterWithID>
Info about the counters of the unit. This is shown when you rightclick the portrait of the unit.
#Not modifiable by techs

<RolloverUseAgainstID>String number</RolloverUseAgainstID>
Info about what the unit counters. This is shown when you rightclick the portrait of the unit.
#Not modifiable by techs

<RolloverBonusDamageID>String number</RolloverBonusDamageID>
Info about the bonus damage the unit has against certain units. This is shown when you rightclick the portrait of the unit.
#Not modifiable by techs

<RolloverAbilitiesID>String number</RolloverAbilitiesID>
Info about the abilities of the unit. Never used I think.
#Not modifiable by techs

<RolloverTextID>String number</RolloverTextID>
Info that shows when you hover over an icon of a unit.
#Not modifiable by techs


<decay delay="Number" duration="Number"></decay>
The first value tells the game how long a unit will be above the ground when death and the second then how long it takes to disappear.
#Not modifiable by techs

<CorpseDecayDelay>Number</CorpseDecayDelay>
Probably a second tag that allows you to change the decay delay
#Not modifiable by techs

<CorpseDecalTime>Number</CorpseDecalTime>
How long the Decal animation takes. Or in other words, how long it will take before the corps disappears below the ground surface
#Not modifiable by techs

<PartisanCount>Number</PartisanCount>
This tag is a poseidon only tag and tells the game how many Partisans will be spawned upon the death of the unit. In AoM(TT) Partisans are militia. Don't ask me why ensemble did not just add a culture option and replacement count to the death replacement
#Not modifiable by techs

<PartisanType>Unit Name</PartisanType>
Almost the same as the <deathreplacement> tag beside the fact that it is hardcoded and thus only available for Poseidon! Thanks ES
#Not modifiable by techs

<bountyfactor resourcetype="Favor or Gold">Number</bountyfactor>
Not % about this one never modified it.
This tag has two values. One defines the resourcetype and the other how much is granted. The tag itself tells the game to grant it on unit kill when playing Norse
#Modifiable by techs

<bountyfactor resourcetype="Favor"></bountyfactor>
This tells the game to grant a Norse unit Favor generation while it is fighting.
#Modifiable by techs

<minimapcolor red="Number" blue="Number" green="Number"></minimapcolor>
This tag defines the colour the unit will have on the minimap. Quite useful for gaia units but otherwise it wouldn't really work out. Note that it is not but
#Not modifiable by techs

<heightbob period="Number" magnitude="Number"></heightbob>
Probably only for flying units. This tag defines the up and down movement of certain flying units. The first value is the period of the movement and the second is the height difference.
#Not modifiable by techs

That were all the variable values :D

) The Constant Values

There are a lot of constant values in the Proto and that's why I'm going to divide this area division into two smaller subdivisions.
-UnitTypes
-Flags

) Constant Type: UnitTypes

LogicalTypeGates
LogicalTypeHouses
LogicalTypeAbstractVillNotHero
LogicalTypeShipNotFishinghip
LogicalTypeMythUnitNotTitan
LogicalTypeEscapesFrostOnTransform
LogicalTypeNoFlailOnThrow
LogicalTypeBuildingsNotWalls
LogicalTypeBuildingNotTitanGate
LogicalTypeEasySelectAvoid
LogicalTypeInvulnerableToGaia
LogicalTypeTimeshift
LogicalTypeScreamsOnSpiderPull
LogicalTypeMummyMinionTarget
LogicalTypePerseusCanStone
LogicalTypeAffectedByFrostGiant
LogicalTypeCanBeStoned
LogicalTypeImplodeAttack
LogicalTypeValidSpiderTarget
LogicalTypeAffectedByHeroize
LogicalTypeDoesNotCreateLush
LogicalTypeAffectedByVortex
LogicalTypeTartarianGateValidOverlapPlacement
LogicalTypeCanBeThrown
LogicalTypeValidReverseWonderTarget
LogicalTypeAffectedByChaos
LogicalTypeValidTremorAttack
LogicalTypeValidDeconstructionTarget
LogicalTypeVolcanoAttack
LogicalTypeSuperPredatorsAutoAttack
LogicalTypeSuperPredatorsAttack
LogicalTypeValidTraitorsTarget
LogicalTypeOdinRegenerates
LogicalTypeMilitaryUnitsAndBuildings
LogicalTypeGreekHeroes
LogicalTypeValidFlamingWeaponsTarget
LogicalTypeAffectedByTownBell
LogicalTypeValidSPCUnitsDeadCondition
LogicalTypeLandMilitary WalkingWood
LogicalTypeAutoattackTargetsBuildings
LogicalTypeValidForestFireTarget
LogicalTypeFimbulWinterTCEvalType
LogicalTypeVillagersRespondToAttack
LogicalTypeRamAttack
LogicalTypeBuildingsThatTrainMilitary
LogicalTypeParticipatesInBattlecries
LogicalTypeValidShiftingSandsTarget
LogicalTypeValidLocustSwarmTarget
LogicalTypeConvertsHerds
LogicalTypeFavoriteMythUnit
LogicalTypeFavoriteUnit
LogicalTypeSeaSerpentAttack
LogicalTypeValidMeteorTarget
LogicalTypeValidFrostTarget
LogicalTypeNavalMilitary
LogicalTypeValidSpyTarget
LogicalTypeMinimapFilterMilitary
LogicalTypeMinimapFilterEconomic
LogicalTypeCanBeHealed
LogicalTypeSiegeAutoAttack
LogicalTypeEarthquakeAttack
LogicalTypeVillagersAttack
LogicalTypeNonGreekUnit
LogicalTypeCavalryAndScout
LogicalTypeGarrisonOnBoats
LogicalTypeAffectedByRestoration
LogicalTypeAffectedByHealingSpring
LogicalTypeValidBoltTarget
LogicalTypeIdleHero
LogicalTypeNeededForVictory
LogicalTypeTornadoAttack
LogicalTypeIdleMilitary
LogicalTypeIdleCivilian
LogicalTypeDangerousAnimals
LogicalTypeUnitsNotBuildings
LogicalTypeRangedUnitsAutoAttack
LogicalTypeRangedUnitsAttack
LogicalTypeBuildingsNotHouses
LogicalTypeScoutsRespondToAttack
LogicalTypePredatorsAttack
LogicalTypeHandUnitsAutoAttack
LogicalTypeMeanPredatorsAutoAttack
LogicalTypePredatorsAutoAttack
LogicalTypeHandUnitsAttack
TransportShip
Teleporter
SetAnimal
AutoupgradedUnit
AbstractScout
AbstractCart
SiegeShip
HammerShip
ArcherShip
AbstractArmory
UtilityShip
MythUnitSiege
MythUnitArcher
MythUnitCavalry
MythUnitInfantry
AbstractPharaoh
AnimalPredator
AnimalReactive
AnimalPrey
ConvertableBuilding
EarlyGoldDropsite
EarlyFoodDropsite
EarlyWoodDropsite
AbstractArcheryRange
AbstractBarracks
AbstractFortress
AbstractStable
SharedBuilding
Pierce
Crush
Hack
SettlementsThatTrainVillagers
AbstractMonumentHuntable
HumanSoldier
GoldDropsite
WoodDropsite
FoodDropsite
Age1Building
WildCrops
Wood
Gold
Food
Favor
Age1Temple
Age3Building
Age2Building

LokiHero
AbstractTradeUnit
AbstractTitan
MythUnit
GodPower
BuildingsThatShoot
Herdable
AbstractWall

Unit class

All
E3Class
TestClass
EmbellishmentClass
NatureClass
BuildingClass
UnitClass

) Constant Type: Flags

RotateReplacement
UseTitanGateMinimap
Forces the game to use the titan gate minimap icon.

ForceBattleMusic
Forces the game to play the battle music when the unit gets attacked.

PlaySoundOnConversion
Forces the game to play the creation sound of the unit on conversion instead of the normal conversion sound. Plenty vault is an example of this.

SummonWorkersButton
Adds a button that allows you to call all your villagers to start working on the building.

ArmoredFoundation
Normally foundations do not have armor but this flag will force the game to apply the armor of the building to the foundation.

HasDummyTargetPoints
UseAlternateGarrisonFlag
This tag tells the game to use the garrison flag of the sky passage what looks like a beam of light.

ShakesCameraOnMoveAndAttack
Used by the titans

DoNotAutoAttack
Does exactly what it is called.

KillsTargetAfterPickupAction
Does exactly what it is called.

DamageToBuildPercent
Used by the titan gate. If it gets damaged the build process gets set back too.

ShowCounterForBuildProgress
Also used by the titan gate. Shows the percentage of completion of a unit.

DestroyWhenCompleted
Another thing used by the titan gate. Destroys the unit on completion. Apparently this does not trigger the AnnounceDestruction flag. I think ES has a few different ways to destroy a unit. Kill ,destroy and destroyed. Kill = removing a unit without leaving anything behind. Death counters can't count this kill. Destroy = destroying a unit without destructing it. Destroyed = when a unit gets slaughtered it is destroyed. ES logics :D

DiesAfterDoingPickupAction
Gets killed after pickup. Sometimes Dies = kill. Again ES logics.

GatherDirectToPlayer
Does what ES called it. A unit with this tag gathers the resources to the player instead of having to drop it off at a dropsite.

GodPowerExclusionHesperides
Gives the unit the Hesperides Tree god power block. This is similar to the Isis monument god power block.

HideOnGodPickerScreens
Hides the unit on the GodPicker screen.

SuperDeathReplacement
When combined with a <deathreplacement> tag it will make two units spawn instead of 1.

SharedGarrison
Used by the sky passages and allows the units to enter one unit and ungarrison at another.

PreventsWallBuilding
Does what ES called it.

HideCostFromDetailHelp
Not sure where it hides the cost of the unit but it does it somewhere :D

HeroName2
Norse hero names

HeroName1
Egyptian pharaoh names.

AdjustPositionOnTerrain

CollisionForce
Sounds awesome but does not seem to do anything :S

Rotateable
BattleMusicTrigger
Triggers the battle music when attacked.

AnnounceDestruction
Does what ES called it.

FadeOutDecalOnDeath
Does what ES called it.

ExperienceUnit
This one is awesome and is used by the hydra and defines when the hydra grows another head. Normally 3 units are required but I think this can be modified (I saw the code somewhere). Every 3 units the attack of the unit gets dealt one time more.

VariationLocked

TrainOnceHealableDeath
Automatons use this to have a healable death.

RMCanRotate

VisibleUnderFogOnlyAfterSeen
Does what ES called it.

DontMarkExtraFog

DontSortAlphaPolys

RenderAfterWater
Does what ES called it. Skybox seems to love this and added it to certain things causing some of those things to become nearly invisible at the water.

UseAlignedObstructionOnMinimap

UseObstructionOnMinimap

InvalidTownBellLocation

MutateDopples
Create a doppleganger when a unit gets mutated?

BurnablePaintTextureWhenPlacing

VictoryBuilding
Wonder countdown trigger

AnnounceFoundationStarted
Does what ES called it.

FlareOnFullyBuilt
Does what ES called it.

HideHitpointsIfGaia
Does what ES called it.

NeverShowButton

CorpseDecays
Does what ES called it.

InvulnerableIfGaia
Does what ES called it.

SingleGatherer
Allows one gatherer. Farms and fish are an example of resources that have this effect.

DeadReplaceOnlyOnTimeout
Spawns the death

Invulnerable
Does what ES called it.

GodPowerExclusion
God power block area effect.

NotScalable
Does what ES called it.

DestroyUnderBuilding

NotRotateable

HideResourceInventory
Does what ES called it.

HideFromHelp

NavalUnit

VisibleOwnerOnly
Does what ES called it. Spy god power uses this has some odd side effects when making the targetable. Units that try to attack it won't be able to land an attack but will still attempt to.

Tracked
Forces the game to track this unit so it can be targetted by certain effects.

ApplyHandicapTraining

DamageToUpgrade

ColorTransformNonGaia

RevealFoundation
Makes the foundation visible for everyone when the construction of it has started. This does not give LOS.

MeteredGarrison

TownBellButton
Adds a town bell button to the unit.

OverrideInitialGarrison

AllowAutoGarrison

DecalStickToWaterSurface

ResourceLimitedAttack

ChargedAttacks

DontDestroyAfterUsed

ForceBuildingData
Only works when you add this to a non-building unit. Enables the unit to train and research units.

DirectProjectile

RevertToSocketAtZeroHitpoints
Does what ES called it. Used by the settlement level 1 (AKA Town center)

UpgradeSocket
Used by the settlement unit so it can be upgraded as a socket.

DoppleOnlyWhenDead
Creates a doppleganger when the unit dies in FOW

HideGarrisonFlag
Does what ES called it.

SolidFoundation

ExcludeFromPlaytest

MakeUnbuiltAtZeroHitpoints
Does what ES called it.

ConvertToGaiaAtZeroHitpoints
Does what ES called it.

PlaceAsFoundation
Editor only I think, forces to place the unit as it's foundation(unbuilt).

ConvertOnStartBuild
Does what ES called it.

SelectWithObstruction
Does what ES called it.

AnnounceConversion
Does what ES called it.

RequiresMaintenance
Dunno what this does, might be obsolete.

DeadReplacementDuringDeathAction
Does what ES called it.

StartOnNoUpdate
This will force the unit to start when there is no update. Not exactly sure but most of the time (if not every) it forces the unit to be active immediately.

StartOnAnimationUpdate
This will force the unit to start on an animation update. If the unit has a birth animation it will start after the animation.

PrayableTo
Does what ES called it.

PlaceSocketWhenPlacing
Editor only but it might not be limited to. Forces the game to place the socketunit underneath the unit when placing it in the editor. Never tested it but it might also work outside the editor.

PlayerOwnsObstruction
Awesome effect used by gates. Allows the allies to walk through the unit and denies enemies to do that. (Water elemtal unit hint hint)

ProjectileTerrainOnly

PlaceAnywhere
Forces the game to skip the placement check when placing a unit.

DestroySocket
Destroys the socket when it is used.

NoProjectileDamage

FieldAbilityLimited

FireDamage

NoIdleActions

AreaDamageConstant

AlwaysCheckCollisions
KillOnAnimLoop
NotCommandable
ShowGarrisonButton
WallBuild
InitialGarrisonOnly
ConstrainOrientation
AlwaysFullColorAsCursor
OrientUnitWithGround

) Constant Type: Moar Flags

AlwaysShowButton

CannotAttackDisabledUnits
Does what its name says if it actually works

StartDormant
No one knows what this does :(

OnlyInEditor
DestroyProjectile

GarrisonSpeedBonus
Gets a speed bonus when units are garissoned

GarrisonBonus
Enables the bonus

GarrisonAttack
Attack bonus

NotDeleteable
Can't be deleted

Doppled
Creates a doppleganger unit that can be seen by other players in FOW thanks to Callistonian for figuring out this mystery.

GivesLOSToAll
Does what it is called

MarketAbility
Dunno, either enables the buttons and or enables to start a trade route with this unit

DoNotYawDuringMovement

ForceToGaia
Does what it's called

FadeOutDuringDeathAnimation
Does what it's called, note that this can cause some lag because AoM's transparency engine sucks

SplitAtMaxInventory
Deprecated I think

SnapPlacement
Docks use this

FaceOutwards
Don't know if it works

UnlimitedSupply
Farms?

HasRuins
Deprecated?

NotSearchable
Makes it so that it won't show up in the editor.

DontFadeInOnBuild

CollidesWithProjectiles

Wanders
Gives the unit some AI logic that makes it wander around it's last position.

AlphaFadeLifespan
The speed of the fade out?

VisibleUnderFogIfGaia

VisibleUnderFog

DoNotCreateUnitGroupAutomatically

DontRotateObstruction

NonAutoFormedUnit
DoNotShowOnMinimap
ObscuredByUnits
Unit outlines behind units that obscure others.

ObscuresUnits
Gives units behind this unit outlines.

FadeInOnCreation

FlattenGround

NotSelectable

SelectableNonSolid
Selecting units is normally done by clicking on the model but things like farms do not have that and this allows it to be selected on the ground texture.

PlayerPlaceable

HasGatherPoint

DoesNotHaveGatherPoint

BloodOnDeath

NoBloodOnDeath

DoNotValidateResourceInventory

ValidateResourceInventory

DoNotDieAtZeroResources
Either deprecated or the unit becomes invinsible with 1 resource.

DieAtZeroResources
Unit dies when it doesn't have any resources anymore.

DoNotDieAtZeroHitpoints
Doesn't die at zero hitpoints. Like animals and I think settlements.

DieAtZeroHitpoints
Either deprecated or it has to do something with the difference between being killed through deletion or dying.

NoHPBar
Does not show an HP Bar

Immoveable
Can't move

1) What is Techtree Editing?

Techtree editing is editing the techtree(x).xml :D
In the techtree(x).xml you will see a long list of tags that might make no sense to you at all. All you need to know for now is that in this list you can find all the technologies of AoM(TT). Each technology has a standard format, it starts with a opening tag and <tech [data]> and ends with a closing tag </tech>. Everything in the Techtree works with opening and closing tags and if one of the two is missing then the Techtree will be invalid. Between the <tech> tags there are a lot of other tags and most of them are important. Editing those tags or adding another Technology is what's called Techtree editing or by some people Technology editing (Both are correct I guess)

2) What is possible with Techtree editing?

Probably more than we know :) This really depends on what you know and how experienced you are. With this guide I will try to explain everything I know and that will make you atleast an intermediate Techtree editor. Now what is possible with Techtree editing on its own? Quite a lot, you could for example change the costs of other technologies and units, stats of units, granting godpowers and even enabling and disabling shared LOS. Listing everything you could do with Techtree editing on its own would be stupid, not to mention the things you could do when you combine Techtree editing with other data editing, but I will tell you what is impossible with Techtree editing.
-You cannot change certain stats of a unit
This is microsofts fault and it's one of the biggest limitations of the Engine, besides not having an amphibious movementtype. You cannot simply add something that is not there. Example: A unit that has no rangedattack (hoplite) cannot get a rangedattack without Proto editing. The closest you can get to adding something is enabling and disabling special attacks, just look at the ra priests.
-Changing other technologies is limited
I guess we'll have to live with this because it is not really necesary as far as I know The only three thing you can change about other Technologies are the cost and the status of the technology. The third one is excluding. Example: Isis reduces all the technology costs, this is a technology. When you research a second age minor god a minor god tech's status will be set to obtainable and the other option will be excluded.
-Changing bla bla bla is impossible
More will come but for now just think: Changing something else than data is not possible.

3) When should I use the Techtree?

If you want to do anything of the stuff I told you in the last chapter, when you want to create a new unit/tech, when you want create a unit or research a tech if x amount of units are on the map etc What people tend to forget (or don't know) is that the effects of some triggers that can cause lag (or just some regular triggers) can be replicated by lagless technologies that can be looped every ms (or 10ms who cares). For example +1 of any stat, enabling and disabling an attack, changing the appearance of a unit or just kill all of the (or a certain type of) units on the map. These effects are all doable through technologies.

If you're thinking like a noob Techtree editor:
You can't think yet ;) you're still dazed by the rest of the guide!

If you're thinking like an intermediate Techtree editor:
What if you want to use console commands? That's no problem since Magnum Pi found out how to trigger console commands with technologies. Things like transform all (or a certain type of) units on the map or set lightning.

As a expert Techtree editor:
How can I make a infinite researchable tech? Easy peasy just use the proto(x) and some requirements a delay and a few technologies with a few statuses.

And as a Data editor god:
How can I make a unit cast godpowers, transform without using a transform, convert enemy units into something else than minions and be unique?
As I'm probably the first that tried this and even I do not control this properly I won't give a short summary here to give you an idea of how it would work.

Now if you're still following me (or partly), here comes the editing part.

) The General Info Area

I divide this area into three smaller sections because it is big.
-The General stuff
-The Variable Values
-The Constant Values