Changes you need to follow as Modder

[Stratego (dev)]

new image for unit stat template
under gfx folder create a folder called "templates" and this image into it

[Stratego (dev)]

in about a month i will remove the "catModifierRels" usage (in consts.json)

so you (as a main modder of the variant) need to
1. ask for me for a build so in dev version the new logics are available (AOS/AOF/AOW/AOG is updated today - done)
2. set all effect affect jsons (where abilities/spells changes unit properties like -2 speed) this

Code: Select all

"trnSpecUnitActions":["IS_EFFECT_AFFECT"]

3. set all techs that are property changers (where the tech changes unit properties like +1 armor) this

Code: Select all

"trnSpecUnitActions":["TECH_IS_PROP_CHANGER"],

4. change all IS_EFFECT_AFFECT and TECH_IS_PROP_CHANGER to use the new "trnValidTargets" settings to set the target of the given effect/ptopchanger tech

i strongly advise using notepad++ multi update tool (updating multiple files in one run) - i just made the above things in AOF that has the biggest assetpack (using that tool and saved me hours)

[Stratego (dev)]

new button and image TEXTURE_HUD_PASS_OWNERSHIP, i placed it there:

Code: Select all

		{
			"idString": "TEXTURE_HUD_BUTT_OBJECTIVES",
			"imgColumns": 1,
			"imgName": "hud/hud_button_objectives.png",
			"withColoring": false
		},
		{
			"idString": "TEXTURE_HUD_PASS_OWNERSHIP",
			"imgColumns": 1,
			"imgName": "hud/hud_button_pass.png",
			"withColoring": false
		},    
                {
			"idString": "TEXTURE_STANCE_INDICATOR_STAND_GROUND",
			"imgColumns": 1,
			"imgName": "indicators/stance_indicator_standground.png",
			"withColoring": false
		},

also my image in AOS

[Stratego (dev)]

oh, i have playced these in AOS/AOF/AOW (in my assetpack) - all other variants needs their modders to put in.
thanks.

[makazuwr32]

so this option allows to pass ownership to neutral player of target unit?

[Stratego (dev)]

no, only empty TCs

[makazuwr32]

i see. anyway that is good way to share at least them with ally.

[Stratego (dev)]

yep

[makazuwr32]

Actually here is a question:
Is this option exclusive to tc or i can share any capturable unit/building?

For example in aof we have ruined fortress, ruined castle and flag as capturable buildings. Can these be shared with ally?

[Stratego (dev)]

only TC

[Stratego (dev)]

in initialisation.json remove all lines that start with "IMG_HUD_MAPEDIT_GREY"
all those settings gott obsolete

and a new line in same file:
{"key":"IMG_UI_TEAMCOLOR_CHOOSER", "val":"ui/teamcolor_chooser.png"},

see attached image i use in aow:

[Stratego (dev)]

also in AOW i use these images for the mapeditor unit type selector
{"key":"IMG_HUD_MAPEDIT_RANGED", "val":"ui/mapeditor_ranged.png"},
{"key":"IMG_HUD_MAPEDIT_BUILDING", "val":"ui/mapeditor_buildings.png"},
{"key":"IMG_HUD_MAPEDIT_CLOSECOMBAT", "val":"ui/mapeditor_ground.png"},
{"key":"IMG_HUD_MAPEDIT_SHIPS", "val":"ui/mapeditor_ship.png"},

[Midonik]

Can I have an empty box or a file for gimp with layers so I can adapt this to Aog?

[Stratego (dev)]

also i use these in AOS and AOF for type selector (team selector is the same as above in AOW)

would be more fancy to be like in AOW (units oveflowing the border on the image) but i am lack of time hassleing with it (would need smaller image canvas and the border is being smaller so the non-scaled 32px unit is a little overflow the border - @Endru1241 @Savra if u feel it nicer please try)

[Stratego (dev)]

ok i could not resist to make an overflowing version instead.
but feel free to make better.

also here is the small border if u want to play with it,.

[Stratego (dev)]

new items in graphics.json
put them right after "TEXTURE_WAYPOINT_ENTRY"

Code: Select all

		{
			"idString": "TEXTURE_MOVE_PATH_CORNER",
			"imgColumns": 1,
			"imgName": "hud/move_path_corner.png",
			"withColoring": false
		},     
		{
			"idString": "TEXTURE_MOVE_PATH_END",
			"imgColumns": 1,
			"imgName": "hud/move_path_arrow.png",
			"withColoring": false
		},  

with these files

[Stratego (dev)]

oh images for 64px based games

[Stratego (dev)]

In all alternatives please remove old/obsolete 2 frame animation occupacy images.
so if a building had 2 images in one image file than that is not good you need to cut it in half and make a normal image and an occupied image and set image defintion accordignly.

So all alternatives (except AOS/AOF/AOW) need to use this new setting, othervise occupacy display will not work anymore!
(Midonik said AOG is already ready with this)

[makazuwr32]

@Savra.

[L4cus]

in initialisation.json remove all lines that start with "IMG_HUD_MAPEDIT_GREY"
all those settings gott obsolete

and a new line in same file:
{"key":"IMG_UI_TEAMCOLOR_CHOOSER", "val":"ui/teamcolor_chooser.png"},

see attached image i use in aow:

Does this include those who have no "grey"?
Like "IMG_HUD_MAPEDIT_RANGED"
I haveto delete those too?

[Stratego (dev)]

grayed verisons are not used anymore as i remember (u select them from list)

[Stratego (dev)]

new features in unit statsheet
- here is a new template file (for 64 px based games)
- here are 3 image names to be placed under assets/gfx/templates folder
-- damage_vs_armor_default.png
-- damage_vs_armor_second.png
-- damage_vs_armor_none.png

also here are my images i used in AOS/AOF/AOW/AOG (in these alternatives i made these)

[Stratego (dev)]

the template file to be put under assets/templates (i can not upload so ask me in email for it.)

[L4cus]

oh this one is new...

[Stratego (dev)]

PLEASE all modders!

please avoid using trnInvalidTargets and trnCanNotCarryThese
istead use trnValidTargets and trnCanCarryThese options

(we have a little trouble showing these in helpfile and also probably the negative parts is not even needed. - maybe sometime i will make them obsolete and after remove from game)

[makazuwr32]

Can we in "cancarrythese" and "validtargets" use NOT operators excluding thus some categories?

[Midonik]

Yes all logical operators can be used in those.

[Stratego (dev)]

yes but basically set the ones it "can"

eg. if you dont want something to hit flying than set to hit "u_ground" + "u_naval" instead of setting "not u_flying".


naturally you can say "u_ground" + "u_naval" except u_orcs or something.

[makazuwr32]

I want for one planned in future carrier unit to be able to carry «u_foot, u_land, NOT(u_melee)» since that unit is planned to be able to carry land foot non-melee units.
Will this setting be valid?

[Stratego (dev)]

sure, however it is weird why a swordsman can not go in