I have no idea for now how to make capturing enemy spies more frequent. I can nullyfy current value of spy rate but it would be also not so good.
Maybe something in the "Double agent" order tenet can help you.
I have no idea for now how to make capturing enemy spies more frequent. I can nullyfy current value of spy rate but it would be also not so good.
Probably not so much because it is coded from dll to policies table. From lua I can get value of that modifier but not set it.
Let's give it a try. What would be new categories then? We can start with:
- To "others" I planned put all civilian promotions (GG, GA, worker etc.). We can call it "civilian" as well
- About diplomatic: remember that there are few promotions from buildings like Wire Service or Literacy. I think there are at least 10 of them.
- I thought also about making "Siege" category" for some specific Siege promotion divided from Ranged category.
I need to learn it first.If I may, I would like to post a suggestion. Your project is really huge. 900+ files. It will be equally huge pain to maintain it later and keep the changes in sync with VP. My suggestion is: put it ASAP to GitHub. This will ease your work considerably and allow others to contribute. Plus some more benefits like issue management.
What about 2nd idea for Barbican? Probably too complicated.
I would just add some yield-based bonus, because what we have for now is bonus XP, supply cap, crime reduction, bonus to units and bonus to cities.
- Or we can add BlockScienceTheft or BlockUDestrictionSpies?
- Or +XX
to range and siege units.
Yup, GitHub is overwhelming at first especially if you want to use text interface (i.e. git function from command prompt). I am not at that level yet.I need to learn it first.I will try to upload all files today. How it works? You just edit the files I uploaded or you make your own copy of that files and then edit them?
I will upload second project with promotion rework.
Code:<!-- Civilopedia more categories for Unit Promotions --> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_MELEE"> <Text>Melee Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_RANGED"> <Text>Ranged Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_NAVAL"> <Text>Naval Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_HEAL"> <Text>Healing Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_SCOUTING"> <Text>Scouting Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_AIR"> <Text>Air Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_SHARED"> <Text>Shared Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_ATTRIBUTES"> <Text>Unit Attributes</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_SIEGE"> <Text>Siege Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_DIPLO"> <Text>Diplomacy Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_CIVILIAN"> <Text>Civilian Promotions</Text> </Row> <Row Tag="TXT_KEY_PROMOTIONS_PEDIA_CARSUB"> <Text>Carriers and Submarines</Text> </Row>
Seems ok. CongratulationsI added this small Promotion Overhaul to Github. You can look there. I managed to connect ModBuddy files and Github directory somehow.
If you want to use the new categories then yes. Until it will appear in VP.Ok. Thank for help. Do I need to put all the Civilopedia Screen file into modpack for now?
You need to create a Pull Request and compare Beta to Master (master on the left, beta on the right). It will show you diffs. Accept them and merge into master.
- How can you know when I publish something to Github?
- I just added new Branch and your files but something is wrong and it doesn;t show me new Diplo category (I changed Ambassador promotion to put it there).
I took a look at that code. My propositions:
Oppidum: if you build Oppidum in city A, the city A will get bonus 20 HP. But the city B has the same Oppidum in its range and tae that tile from city A and starts working it. Bonus 20 HP is still tied to city A. If you now decide to remove that Oppidum 20 HP will be taken from city B(!) not A.
Reason: there's no event triggered on moving tile from one city to another.
Possible solution: make Oppidum permament.