Pers -> Achae

[wowgetoffyourcellphone]

Will changing all files from 'Pers' (templates, actors, text, civ.json, textures, portraits, etc.) to 'Achae' screw up the AI? Eventually I want to include the Sassanid Persians (civ: sass), so I think changing the 'Persians' to Achaemenid Persians now would be a good thing. I thought about this when thinking of eventually adding the Gupta Indians (civ: gupt) and how that's possible since the Maurya Indian assets don't monopolize the generic "indi" prefix as the current Achaemenid Persians do with the "pers" prefix. 

Edited February 21, 2021 by wowgetoffyourcellphone

[Freagarach]

You'll need to edit petra/config.js also. Perhaps you can convince someone to make this change in vanilla 0 A.D.?

[Nescio]

7 hours ago, wowgetoffyourcellphone said:

Will changing all files from 'Pers' (templates, actors, text, civ.json, textures, portraits, etc.) to 'Achae' screw up the AI?

No. As @Freagarach already pointed out, the only occurrence is in the `simulation/ai/petra/config.js` file, and you probably want to edit that file anyway (it's for adding non-standard structures). You could also consider keeping the `pers.json` file but setting "SelectableInGameSetup" to false.

The map files could be fix with:

find maps/ \( -name '*.js' -o -name '*.json' -o -name '*.xml' \) -print0 | xargs -0 sed -i 's,pers/,acha/,g'

 

7 hours ago, wowgetoffyourcellphone said:

Sassanid Persians

‘Sasanian’ is the preferred spelling nowadays.

7 hours ago, wowgetoffyourcellphone said:

Achaemenid Persians

Just Achaemenids would be sufficient. We don't have Mauryan Indians, Ptolemaic Egyptians, or Seleucid Syrians either.

 

If you go down that route, though, you might want to consider replacing the Macedonians with the Argead and Antigonid dynasties.