SDK Modding Request Thread

• 10- DLL Access
• 9 - Greater access to the AI, especially in terms of combat/missions/pathing
• 8 - Allow for graphics/VFS/Database reloading in game
• 7 - Working associations/blocking in ModBuddy

• 9 - Ability to add custom landmarks/wonders/improvements
• 6 - Ability to add custom Font Icons - Needed when creating new yields/resources
• 5 - Ability to use flat images as custom leaderheads rather than copying existing leader animations
• 5 - Access to route graphic logic - to fix poorly connecting road graphics
• 4 - Ability to add custom Fonts

• 7 - Implementation of UIAddin content types for GameSetup/AdvancedSetup, NotificationPanel, InfoCorner, and DiploCorner
• 6 - Greater superglobal and cache functionality
• 5 - Ability to edit how Research Agreements work

• 7 - TurnStartLoopPlayers(pPlayer)
• 7 - TurnStartLoopCities(pCity)
• 7 - TurnStartLoopPlayerCities(pPlayer, pCity)
• 6 - TurnStartLoopPlots(pPlot)
• 6 - TechResearched(pPlayer, iTech)
• 6 - BuildingCreated(pCity, iBuilding)
• 6 - BuildingGained(pCity, iBuilding)
• 6 - BuildingDestroyed(pCity, iBuilding)
• 6 - BuildingLost(pCity, iBuilding)
• 4 - Fix (or better document) events Events.RunCombatSim and Events.EndCombatSim
• 4 - OnBuildingClassCreated(city, building) event

• 7 - Implement functions that allow for modders to control Culture and Happiness in the same manner as yields (adding to/from objects/tiles, altering rates)

1. This is a very generic request (but I have no sense of whether it will be very hard from the C++ side). I'd like to be able to change anything in the db "on the fly" (i.e., during a game via Lua) and know that it will "update" correctly (change map graphic or whatever) and "stick" in the gamesave file (i.e., not be reset to xml value or a value from cache generated by a different game). It's fine if the "update" part takes extra commands (for example, there could be separate updates for map graphics, city/building yields, trait effects, etc.).
   
   
2. If the generic solution in #1 is not possible, then here are some specific things that I would like to be able to do on the fly:
   • Change leader
   • Add/remove traits
   • (many more... which is why I would prefer a generic solution)
   
   
3. More flexible control of unit movement restrictions (1upt, rival borders, foreign cities, etc.). As a simple example, it would be nice to be able to remove 1upt for civilian units while keeping it for military units. More generally, I'd like to be able to control all such movement or "co-habitation" restrictions in the unit xml (or perhaps in the special unit xml). My spy or diplomat or fairy godmother unit should be able to enter rival territory and even enter a foreign city. [Interestingly, I've had units stop in a friendly city when moving through crowded and unrevealed territory. So the engine seems to allow it already, but the interface won't let me chose such movement if I can already see the terrain.]

1. A generic "unit action" system in xml. I'm thinking along the lines of the spell/ability system in FFH, which was an XML file that could do simple things by itself or call Python for more complex prereqs or effects. Any action would have a name, trigger (most commonly a button on the unit action panel), optional prerequisites (unit type, level, promotions, etc), and some optional effects (gives unit promotion, gives all nearby units a promotion, etc.). Most importantly, the prereques and effects would both include optional Lua calls. So there would be an optional LuaPrereq (calling a function that must be True) and an optional LuaEffect (calling a Lua function if the action happens).
   
   
2. Optional LuaPrereq and LuaEffect tags in XML for for buildings, policies, techs, and darn near everything else. The LuaPrereq would call a function that must return True in order to build building, adopt policy, research tech, etc. The LuaEffect would call a function when building built, policy adopted, tech researched, etc.

Gangler said:

This also basically prevents terrain or features that add happiness, or improvements or specialists that add happiness

Click to expand...

<Table name="MinorCiv_QuestWeights">
    <Column name="MinorCivType" type="MinorCiv_Types(Type)"/>
    <Column name="PersonalityType" type="MinorCiv_Personalities(Type)"/>
    <Column name="QuestType" type="MinorCiv_Quests(Type)"/>
    <Column name="Weight" type="integer" default="0"/>
</Table>
<MinorCiv_QuestWeights>
    <Row>
        <PersonalityType>MINORCIV_HOSTILE</PersonalityType>
        <QuestType>FIND_KILL_CITY_STATE</QuestType>
        <Weight>10</Weight>
    </Row>
</MinorCiv_QuestWeights>

1. Change minor civ quest weights to a table as seen above, instead of the present method of individual global variables for each cell of the table. The code simply checks if a citystate matches the type or personality, and if so, uses that weight for the quest.
2. Capability to increase city hitpoints with a building. So for example if a city starts at 20 hitpoints, building Walls might increase it +5 to 25.
3. Global define true/false to set if research agreements should give a free tech.

• Capability to define a unit's zone of control radius in XML and Lua.