Hands-On Usage
custom_override_tooltip is ideal for consolidating multiple scattered game state modifications (such as variable operations, flag assignments, unit spawning) into a single player-readable tooltip within complex effect blocks, preventing the UI from being cluttered with numerous internal details. Common scenarios include: hiding the specific steps of behind-the-scenes mathematical calculations, and summarizing an entire chain of triggered consequences with a single localization string.
custom_override_tooltip = {
tooltip = FOCUS_REWARD_INDUSTRY_TOOLTIP
set_variable = { var = industrial_output value = 10 }
add_to_variable = { var = global_prestige value = 5 }
set_global_flag = industry_modernized
}
Synergy
[hidden_effect](/wiki/effect/hidden_effect): Nest side effects that truly don't need to be shown to the player inside hidden_effect, then wrap the entire block in custom_override_tooltip to achieve two-tier control: "display a friendly description while hiding all implementation details."
[custom_effect_tooltip](/wiki/effect/custom_effect_tooltip): When you only need to append an additional description to the normal tooltip flow (rather than completely replace it), use custom_effect_tooltip. The two commands form a complementary relationship of "complete override" versus "supplementary addition."
[effect_tooltip](/wiki/effect/effect_tooltip): Used outside of custom_override_tooltip to selectively simulate the tooltip display of a specific effect block. Combined with this command, you can precisely control which content is visible and which is suppressed.
[if](/wiki/effect/if): When nesting conditional branches inside custom_override_tooltip, the individual tooltips from each branch in the if statement are all covered by the unified outer tooltip, making it ideal for clean presentation of multi-condition reward logic.
Common Pitfalls
- Forgetting the
tooltip field: If tooltip = ... is omitted in a custom_override_tooltip block, all effects within that block will display with no tooltip in the UI, leaving players with no feedback. The game may not even report an error, making this extremely difficult to troubleshoot.
- Mistakenly assuming it controls trigger-side tooltips:
custom_override_tooltip only suppresses tooltips within effect blocks. If you want to achieve similar effects on the trigger/condition side, use [custom_override_tooltip](/wiki/trigger/custom_override_tooltip) instead. Mixing the two will result in unexpected tooltip behavior.