Home › Native functions › Rules

Engine internals. No scripting access today. Listed for contributors and for understanding the game; using it needs a change to the game library.

Rules

Function	Signature (Linux)	Symbol	Current	From Lua	Notes
Appeal::Instance::UpdateOnly	`void Rules::Appeal::Instance::UpdateOnly(Rules::Appeal::Instance* this, Map::Plot::Instance* pkPlot)`	`0x35ff20`	`0x362420`	no	signal, event, writes
Cities::Shared::Instance::RelocateBuildingGreatWorks ★	`void Rules::Cities::Shared::Instance::RelocateBuildingGreatWorks(const Rules::Cities::Shared::Instance* this, City::Instance& kCity, const eastl::vector<GreatWorkListIndex, eastl::allocator>& aGreatWorkIndices)`	`0x64d150`	`0x64d980`	no	analysed
Economic::Instance::DoCultureBombAt	`void Rules::Economic::Instance::DoCultureBombAt(Rules::Economic::Instance* this, PlotCoord kLocation, bool bCaptureOwnedTerritory)`	`0x36e380`	`0x370870`	no	notification, writes
Espionage::Instance::CaptureSpy	`void Rules::Espionage::Instance::CaptureSpy(Rules::Espionage::Instance* this, UnitOperationTypes eOperation, Unit::Instance* pkSpy, Unit::Instance* pkCounterSpy)`	`0x370200`	`0x3726e0`	no	signal, notification, event, writes; called by EFFECT_KILL_EMERGENCY_TARGET_SPIES_IN_CITY
Espionage::Instance::KillSpy	`void Rules::Espionage::Instance::KillSpy(Rules::Espionage::Instance* this, UnitOperationTypes eOperation, Unit::Instance* pkSpy, Unit::Instance* pkCounterSpy)`	`0x372240`	`0x374720`	no	notification, event, writes
Espionage::Instance::ResetFailedSpy	`void Rules::Espionage::Instance::ResetFailedSpy(Rules::Espionage::Instance* this, UnitOperationTypes eOperation, Unit::Instance* pkSpy)`	`0x3728e0`	`0x374dc0`	no	notification, event, writes
Espionage::Instance::ResetSpyData	`void Rules::Espionage::Instance::ResetSpyData(Rules::Espionage::Instance* this, Unit::Instance* pkSpy)`	`0x372bb0`	`0x375090`	no	edit_call, writes
Espionage::Shared::Instance::AwardCounterYield	`void Rules::Espionage::Shared::Instance::AwardCounterYield(Rules::Espionage::Shared::Instance* this, Unit::Instance* pkUnit, PlayerTypes ePlayer)`	`0x64e0c0`	`0x64e8e0`	no	event, writes

Notes (★)

Rules::Cities::Shared::Instance::RelocateBuildingGreatWorks

Re-homes a list of great works after a building replacement changes a city's slots.

For each work in the list: if the city's own Buildings can take it (CanAddGreatWork), it adds it there via edit() + AddGreatWork. [verified; evidence: static-analysis — decompilation read in Ghidra]
Otherwise it walks the player's other cities and, for every other city where CanAddGreatWork is true, calls AddGreatWork. [verified; evidence: static-analysis — decompilation read in Ghidra]
If no city can take it, nothing happens: no notification, no record, no fallback. The work simply ends up in no slot. [verified; evidence: static-analysis — decompilation read in Ghidra]
The loop over other cities has no break/return after a successful add. [verified; evidence: static-analysis — decompilation read in Ghidra]
A work that fits nowhere is silently dropped from all slots (it probably still exists in the game-wide great work list). (Medium.) [inferred; evidence: static-analysis — decompilation read in Ghidra]
Because the loop does not stop after the first successful add, the same work could be added to more than one other city if CanAddGreatWork only checks the target city and not other cities. Possible duplication bug. (Low: depends on what CanAddGreatWork checks, not yet read.) [inferred; evidence: static-analysis — decompilation read in Ghidra]
One concrete way works "get lost": a building replacement with no spare slots elsewhere. The work is neither archived nor reported. [inferred; evidence: static-analysis — decompilation read in Ghidra]
Relevant to any 'great works archive' idea: this is a point where a work could be saved instead of dropped. [inferred; evidence: static-analysis — decompilation read in Ghidra]