CK3 DatabaseCrusader Kings III · 1.20.1.2 “Crozier” · unofficial
Silk & Silverout Tue, Nov 17What's free, what needs the DLC, price →

Scripted effect

remove_board_game_variables_effect

remove_board_game_variables_effect = yes

game/common/scripted_effects/00_board_game_effects.txt, line 266 (19 lines). No parameters.

remove_board_game_variables_effect is a scripted effect in Crusader Kings III, written at line 266 of its file. It takes no parameters: remove_board_game_variables_effect = yes. The game's script calls it in 2 places, among them configure_start_board_game_effect (scripted effect) and remove_board_game_info_effect (scripted effect). Patch 1.20.1.2, from game/common/scripted_effects/00_board_game_effects.txt.

The comment above it in the file

Clean up all variables resulting from playing a board game.

What it does

Every line of it is script with no tooltip text: the script is below.

The script as written (19 lines of game script)
remove_board_game_variables_effect = {
	# Player-side variables.
	remove_variable = bg_current_round
	remove_variable = bg_current_score
	remove_variable = bg_move_result
	# If there are any wagering counties, clear the blockers on their being wagered.
	if = {
		limit = { exists = scope:bg_stake_land_recipient }
		scope:bg_stake_land_recipient = { remove_variable = wagered_county }
	}
	if = {
		limit = { exists = scope:bg_stake_land_actor }
		scope:bg_stake_land_actor = { remove_variable = wagered_county }
	}
	# Remove any debug variables.
	remove_variable = bg_gib_only_losing_locs
	remove_variable = bg_gib_only_winning_locs
	# Note, we don't remove var:engaged_in_board_game here, as we run this effect at the start of games for clean-up also.
}

As written in game/common/scripted_effects/00_board_game_effects.txt.

Where it is used

Every place in common/, events/ and history/ that calls remove_board_game_variables_effect.

Source: game/common/scripted_effects/00_board_game_effects.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.

Spotted a mistake on this page?