trigger · career_profile_check_ribbon

Hands-On Usage

career_profile_check_ribbon is commonly used in career mode-related mods to check whether the player has obtained and claimed a specific ribbon, thereby unlocking subsequent rewards, special events, or achievement paths. Typical scenarios involve using it within the available or trigger block of a career profile interface, determining whether an option is selectable based on the player's ribbon collection status.

# Example: Allow a special event option to trigger only after the player has collected the specified ribbon
country_event = {
    id = my_career.1
    option = {
        name = my_career.1.a
        trigger = {
            career_profile_check_ribbon = {
                ribbon = my_mod_ribbon_first_victory
            }
        }
        # Execute subsequent effects...
    }
}

Synergy

• [career_profile_check_medal](/wiki/trigger/career_profile_check_medal): Works in parallel with ribbon checking logic to simultaneously verify whether the player has obtained the corresponding medal. These two are often combined within and blocks to form composite unlock conditions.
• [career_profile_check_points](/wiki/trigger/career_profile_check_points): Checks career point thresholds while evaluating ribbon collection status, ensuring the player meets multidimensional conditions before triggering content.
• [and](/wiki/trigger/and) / [or](/wiki/trigger/or): Ribbon checks are almost always nested within logical operator blocks, freely combinable with other career conditions to achieve flexible "any one of" or "all conditions met" evaluations.
• [career_profile_has_player_flag](/wiki/trigger/career_profile_has_player_flag): Tracks whether the player has already processed a specific ribbon reward to prevent duplicate triggers. Works with ribbon checks to implement state machine control.

Common Pitfalls

1. Mixing ribbon key names with medal key names: career_profile_check_ribbon and career_profile_check_medal are two independent systems. Directly inserting a medal-defined key into the ribbon field will cause the condition to always return false without error, making it extremely difficult to debug.
2. Treating collected-but-unclaimed as true: This trigger requires the ribbon to be "claimed" to return true. Meeting the achievement condition alone is insufficient if the player has not manually claimed it in the career profile interface. Do not use it as a simple progress check for "whether an achievement is unlocked."