How to correctly implement new civs to the game?

[PyrrhicVictoryGuy]

So the mod file goes into the mods directory, done. From what I think all the thing are in the correct place but when i go in game and try to do anything I get error messages and blank gray menus.

I wanted to ask if any of the prominent modders had these problems before and if so how did you get pass them.

When I try to open the structure tree:

 

 

When I try to play a match:

 

Civ Json file:

bact.json

Unique techs:

cavalry_tradition.jsonbudhist_evangelism.jsonbactrian_camels.json

Civ bonus:

bact_cavalry.json

 

The whole thing:

Bactrians-mod.rar

 

 

 

 

[Yekaterina]

I think you are missing a double quotation somewhere in your civ.json file. 

[Yekaterina]

Here is my version, which does work. Bactrians.zip

[PyrrhicVictoryGuy]

4 hours ago, Yekaterina said:

I think you are missing a double quotation somewhere in your civ.json file. 

Yup already solved it now my problem is that the structure tree still doesn't work and in game I can't build anything.

 

 

Edited August 11, 2021 by PyrrhicVictoryGuy

[s0600204]

Quote

JSON.parse: expected ':' after property name in object at line 5 column 2 of the JSON data
ERROR: Failed to parse 'simulation/data/technologies/budhist_evangelism.json'

JSON.parse: unexpected character at line 18 column 5 of the JSON data
ERROR: Failed to parse 'simulation/data/technologies/cavalry_tradition.json'

JSON.parse: expected ',' or '}' after property value in object at line 9 column 2 of the JSON data
ERROR: Failed to parse 'simulation/data/auras/units/heroes/bact_hero_menander_3.json'

Pretty self-explanatory.

 

Quote

WARNING: The "structures/bact/storehouse" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/bact/sentry_tower" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/bact/wallset_stone" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/bact/wonder" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/sele/wall_gate" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/sele/wall_tower" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/sele/wall_long" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/sele/wall_medium" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/sele/wall_short" template has a defined civ of "sele". This does not match the currently selected civ "bact".
WARNING: The "structures/bact/wall_gate" template has a defined civ of "sele". This does not match the currently selected civ "bact".

Please specify the correct civ within your structure templates.

 

Quote

ERROR: CCacheLoader failed to find archived or source file for: "simulation/templates/units/bact/infantry_javelineer_b.xml"
ERROR: Failed to load entity template 'units/bact/infantry_javelineer_b'

Either provide the missing template, or provide a suitable alternative under SkirmishReplacements in simulation/data/civs/bact.json.

[PyrrhicVictoryGuy]

@s0600204 Thank you, you're a life saver really. But there is still something I gotta figure out:

50 minutes ago, s0600204 said:

JSON.parse: expected ':' after property name in object at line 5 column 2 of the JSON data
ERROR: Failed to parse 'simulation/data/technologies/budhist_evangelism.json'

 

It can't be this right?

[hyperion]

"Buddhist Evangelism" isn't a { key : value } pair, so no braces around it, like for genericName.

[s0600204]

(@hyperion if you did that, you would get the following: WARNING: specificName should be an object of civ->name mappings in budhist_evangelism.json)

@PyrrhicVictoryGuy It should read something like:

	...
	"specificName": {
		"bact": "Buddhist Evangelism"
	},
	...

 

[hyperion]

Oh, thanks. At least it makes it valid json ...