trigger · num_of_career_profile_points

Hands-On Usage

num_of_career_profile_points is commonly used in career mode-related mods to unlock special events, focuses, or rewards based on the player's accumulated career points. For example, to trigger a specific event option only after the player reaches a certain point threshold:

available = {
    num_of_career_profile_points > 50
}

Synergy

• [career_profile_check_points](/wiki/trigger/career_profile_check_points): Another career profile checking trigger that can be combined to distinguish between "total points" and "points checked under specific conditions," enabling multi-layered career progress gates.
• [career_profile_check_value](/wiki/trigger/career_profile_check_value): Used to check specific numeric variables in the career profile. When paired with point checks, it enables compound conditions like "points sufficient AND specific milestone completed."
• [career_profile_has_player_flag](/wiki/trigger/career_profile_has_player_flag): Checks player career flags. When combined with point checks, it prevents the same reward from being triggered repeatedly.
• [count_triggers](/wiki/trigger/count_triggers): When you need to count how many career conditions are simultaneously satisfied, you can nest num_of_career_profile_points as one of the sub-conditions.

Common Pitfalls

1. Misusing comparison operators: Beginners often forget that this trigger requires comparison operators (such as >, <, >=). Writing num_of_career_profile_points = 50 directly means "exactly 50," not "at least 50 points" as intended. Use >= 50 instead.
2. Scope confusion: Although any scope is supported, this trigger reads the current player's career profile data. When called within looping scopes like every_country, the result always reflects the player's profile rather than the iterated country, which can cause logical misunderstandings.