Contest definition - Revision history

Sm7iun: /* Other keys */

2026-03-30T04:47:21Z

Other keys

← Older revision		Revision as of 04:47, 30 March 2026
Line 2,268:		Line 2,268:
	\|-		\|-
	\| '''WARNING_FILE'''		\| '''WARNING_FILE'''
	\| Name of a frequency range warning file located in <tt>%appdata%\DXLog\Database</tt>. The format of each line in the warning file is:<br><tt>Mode regular expression;frequency range;Message</tt><br>Example:<br><tt><nowiki>CW;3400-3520;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>CW;3550-3900;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>SSB;3400-3600;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>SB;3675-3700;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>SSB;3725-3900;Warning: Operation not allowed on this frequency</nowiki></tt><br>'''Important:~~'''~~ File name casing must be correct for online update to work.		\| Name of a frequency range warning file located in <tt>%appdata%\DXLog\Database</tt>. The format of each line in the warning file is:<br><tt>Mode regular expression;frequency range;Message</tt><br>Example:<br><tt><nowiki>CW;3400-3520;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>CW;3550-3900;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>SSB;3400-3600;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>SSB;3675-3700;Warning: Operation not allowed on this frequency</nowiki><br><nowiki>SSB;3725-3900;Warning: Operation not allowed on this frequency</nowiki></tt><br>'''Important: File name casing must be correct for online update to work.'''
	\| No default value		\| No default value
	\|-		\|-

Sm7iun: /* Other keys */

2026-03-30T04:46:30Z

Other keys

← Older revision		Revision as of 04:46, 30 March 2026
Line 2,240:		Line 2,240:
	\|-		\|-
	\| '''OVERRIDE_INVALID_QSO_MESSAGE'''		\| '''OVERRIDE_INVALID_QSO_MESSAGE'''
	\| Suppress invalid QSO message for selected cases. Syntax is <tt>OVERRIDE_INVALID_QSO_MESSAGE=</tt>''IncaseRegex;AndRegex'' Example: <tt>OVERRIDE_INVALID_QSO_MESSAGE=DEST->DXCC:^K$;DEST->RCVD:^$</tt> will suppress complaints about invalid QSO when the RCVD field is empty US stations. This is a legacy function with limited usefulness. To ensure stations without valid exchanges are correctly displayed in the bandmap you typically need to add zero-points dummy rules that will prevent error messages anyway.		\| Suppress invalid QSO message for selected cases. Syntax is <tt>OVERRIDE_INVALID_QSO_MESSAGE=</tt>''IncaseRegex;AndRegex'' Example: <tt>OVERRIDE_INVALID_QSO_MESSAGE=DEST->DXCC:^K$;DEST->RCVD:^$</tt> will suppress complaints about invalid QSO when the RCVD field is empty US stations. '''This is however a legacy function with limited usefulness.''' To ensure stations without valid exchanges are correctly displayed in the bandmap you typically need to add zero-points dummy rules that will prevent error messages anyway.
	\| style="white-space: nowrap;" \| Default value: None		\| style="white-space: nowrap;" \| Default value: None
	\|-		\|-

Sm7iun: /* Other keys */

2026-03-30T04:46:02Z

Other keys

← Older revision		Revision as of 04:46, 30 March 2026
Line 2,240:		Line 2,240:
	\|-		\|-
	\| '''OVERRIDE_INVALID_QSO_MESSAGE'''		\| '''OVERRIDE_INVALID_QSO_MESSAGE'''
	\| Suppress invalid QSO message for selected cases. Syntax is <tt>OVERRIDE_INVALID_QSO_MESSAGE=</tt>''IncaseRegex;AndRegex'' Example: <tt>OVERRIDE_INVALID_QSO_MESSAGE=DEST->DXCC:^K$;DEST->RCVD:^$</tt> will suppress complaints about invalid QSO when the RCVD field is empty US stations. ~~Note that this~~ is a legacy function with limited usefulness. To ~~make sure~~ stations ~~show up~~ correctly in the bandmap ~~without valid exchanges~~ you typically need to add dummy rules that will prevent ~~errors to show~~ anyway.		\| Suppress invalid QSO message for selected cases. Syntax is <tt>OVERRIDE_INVALID_QSO_MESSAGE=</tt>''IncaseRegex;AndRegex'' Example: <tt>OVERRIDE_INVALID_QSO_MESSAGE=DEST->DXCC:^K$;DEST->RCVD:^$</tt> will suppress complaints about invalid QSO when the RCVD field is empty US stations. This is a legacy function with limited usefulness. To ensure stations without valid exchanges are correctly displayed in the bandmap you typically need to add zero-points dummy rules that will prevent error messages anyway.
	\| style="white-space: nowrap;" \| Default value: None		\| style="white-space: nowrap;" \| Default value: None
	\|-		\|-

Sm7iun: /* Livescore keys */

2026-03-30T04:42:36Z

Livescore keys

← Older revision		Revision as of 04:42, 30 March 2026
Line 2,188:		Line 2,188:
	\|-		\|-
	\| '''LIVESCORE_RTC_SENT_EXCHANGE'''		\| '''LIVESCORE_RTC_SENT_EXCHANGE'''
	\| List of the exchange elements sent by own station. Accepts *RGX conditionals like CABRILLO_LINE. Valid keywords are NR, OPNAME, EXCHANGE, POWER, MYCQZONE, MYITUZONE, MYDXCC, STATE, GRID4, GRID, and NOTHING. A literal string must be preceded by a single quote '. '''Important~~'''~~: This key is required in contest definition file to enable Real Time Contest QSO upload.		\| List of the exchange elements sent by own station. Accepts *RGX conditionals like CABRILLO_LINE. Valid keywords are NR, OPNAME, EXCHANGE, POWER, MYCQZONE, MYITUZONE, MYDXCC, STATE, GRID4, GRID, and NOTHING. A literal string must be preceded by a single quote '. '''Important: This key is required in contest definition file to enable Real Time Contest QSO upload.'''
	\| Default value: None		\| Default value: None
	\|-		\|-

Sm7iun: /* Contest score keys */

2026-03-30T04:41:35Z

Contest score keys

← Older revision		Revision as of 04:41, 30 March 2026
Line 1,998:		Line 1,998:
	\|+style="text-align:Left;"\|		\|+style="text-align:Left;"\|
	\| '''SCORE'''		\| '''SCORE'''
	\| Scoring principle. Valid values: BY_BAND, BY_BAND_MODE, BY_PERIOD, BY_PERIOD_BAND, and BY_PERIOD_BAND_MODE. Additional values are BY_MODE_GROUP and BY_BAND_GROUP. Their function is unknown. '''Important:~~'''~~ BY_MODE does not exist.		\| Scoring principle. Valid values: BY_BAND, BY_BAND_MODE, BY_PERIOD, BY_PERIOD_BAND, and BY_PERIOD_BAND_MODE. Additional values are BY_MODE_GROUP and BY_BAND_GROUP. Their function is unknown. '''Important: BY_MODE does not exist.'''
	\| Default value: BY_BAND		\| Default value: BY_BAND
	\|-		\|-

Sm7iun: /* Multiplier keys */

2026-03-30T04:40:52Z

Multiplier keys

← Older revision		Revision as of 04:40, 30 March 2026
Line 1,832:		Line 1,832:
	'''Multiplier field considerations'''		'''Multiplier field considerations'''

	<tt>CALLSIGN</tt>		<tt>CALLSIGN</tt><br>
			Ignores multiplier type for processing but a MULT#_FX key is always honored.<br>
	Ignores multiplier type for processing but a MULT#_FX key is always honored.		Multiplier type can still be used for creating a list of valid multiplier values so<br>
			CUSTOM can be useful for a derived multiplier (such as the last letter of a callsign).<br>
	Multiplier type can still be used for creating a list of valid multiplier values so CUSTOM can be useful
	for a derived multiplier (such as the last letter of a callsign).

	A dummy multiplier type CALLSIGN can be used for clarity.		A dummy multiplier type CALLSIGN can be used for clarity.

	<tt>FROM_DXCC</tt>		<tt>FROM_DXCC</tt><br>
			Valid multiplier types are DXCC and FX. With DXCC, worked multipliers are displayed in the<br>
			Worked DXCC window. With FX, the list of workable multipliers need to be defined, e.g., <br>
			using <code>WINDOWS_CML_LIST_FX=GetList_...</code>.

	~~Valid multiplier types are DXCC and FX. With DXCC, worked multipliers are displayed in the Worked DXCC window. With FX, the~~		<tt>FROM_WPX</tt><br>
	~~list of workable multipliers need to be defined, e.g., using~~ <~~code~~>~~WINDOWS_CML_LIST_FX=GetList_...~~</~~code>.~~		The multiplier type is ignored but a dummy type WPX can be used for clarity. Worked multipliers are <br>
			displayed in a growing window.
	<tt>~~FROM_WPX~~<~~/tt~~>

	The multiplier type is ignored but a dummy type WPX can be used for clarity. Worked multipliers are displayed in a growing window.

	'''Multiplier type considerations'''		'''Multiplier type considerations'''

	<tt>HQ</tt>		<tt>HQ</tt><br>
			Like FIELD but with the exception that the multiplier will only be valid if the QSO does not <br>
	Like FIELD but with the exception that the multiplier will only be valid if the QSO does not represent a multiplier with lower number.		represent a multiplier with lower number. For instance, if MULT3 is HQ, it will only be valid <br>
	For instance, if MULT3 is HQ, it will only be valid if neither MULT1 nor MULT2 are valid.		if neither MULT1 nor MULT2 are valid. A DXCC entity qualifier can be added using the <br>
			<tt>MULT#_ADD_DXCC</tt> key, making sure the same multiplier is valid once per country. <br>
	A DXCC entity qualifier can be added using the <tt>MULT#_ADD_DXCC</tt> key, making sure the same multiplier is valid once per country.		For example if you receive ARRL from W1AW, the multiplier's value will be "ARRL*K". <br>
	For example if you receive ARRL from W1AW, the multiplier's value will be "ARRL*K". Worked multipliers are displayed in a growing window.		Worked multipliers are displayed in a growing window.

	~~<tt>CQZONE</tt> and <tt>ITUZONE</tt>~~

	~~Can be used with the RCVD, RECINFO, RECINFO2, and RECINFO3 fields. The set of workable multipliers is created automatically.~~

	~~<tt>FX</tt>~~

	~~Can be used with the CALLSIGN, RCVD, RECINFO, RECINFO2, and RECINFO3 fields. The set of workable multipliers need to be defined, e.g., using~~
	~~<tt>WINDOWS_CML_LIST_FX=GetList_...</tt>.~~

	~~<tt>FIELD</tt>~~

	~~Can be used with the RCVD, RECINFO, RECINFO2, and RECINFO3 fields. This is typically used for multipliers with too many possible values~~
	~~that visual tracking is infeasible. But it is still possible,~~

	~~The set of valid multiplier values is undefined by default and typically created using <tt>WINDOWS_CML_LIST_FX=GetList_...</tt>~~.

	<tt>~~CUSTOM~~</tt>		<tt>CQZONE</tt> and <tt>ITUZONE</tt><br>
			Can be used with the RCVD, RECINFO, RECINFO2, and RECINFO3 fields. <br>
			The set of workable multipliers is created automatically.

	Can be used with the RCVD, RECINFO, RECINFO2, RECINFO3~~, and CALLSIGN~~ fields. The ~~list~~ of ~~valid multiplier values is created by a~~		<tt>FX</tt><br>
	~~values listed between~~ <~~code~~>~~[MULTIPLIERS START]</code> and <code>[MULTIPLIERS END]~~</~~code~~>.		Can be used with the CALLSIGN, RCVD, RECINFO, RECINFO2, and RECINFO3 fields. <br>
			The set of workable multipliers need to be defined, e.g., using <tt>WINDOWS_CML_LIST_FX=GetList_...</tt>.

	<tt>~~NUM~~</tt>		<tt>FIELD</tt><br>
			Can be used with the RCVD, RECINFO, RECINFO2, and RECINFO3 fields. <br>
			This is typically used for multipliers with too many possible values <br>
			that visual tracking is infeasible. But it is still possible, <br>
			The set of valid multiplier values is undefined by default and <br>
			typically created using <tt>WINDOWS_CML_LIST_FX=GetList_...</tt>.

	Can be used with the ~~CALLSIGN,~~ RCVD, RECINFO, RECINFO2, and ~~RECINFO3~~ fields. ~~Like FIELD but strips leading zeroes~~.		<tt>CUSTOM</tt><br>
			Can be used with the RCVD, RECINFO, RECINFO2, RECINFO3, and CALLSIGN fields. <br>
			The list of valid multiplier values is created by a values listed between <br>
			<code>[MULTIPLIERS START]</code> and <code>[MULTIPLIERS END]</code>.

	<tt>~~LASTLETTER~~</tt> ~~and~~ <tt>~~LETTER1~~<~~/tt~~>		<tt>NUM</tt><br>
			Can be used with the CALLSIGN, RCVD, RECINFO, RECINFO2, and RECINFO3 fields. <br>
			Like FIELD but strips leading zeroes.

	Can be used with the CALLSIGN, RCVD, RECINFO, RECINFO2, and RECINFO3 fields. The list of workable multipliers is automatically created.		<tt>LASTLETTER</tt> and <tt>LETTER1</tt><br>
			Can be used with the CALLSIGN, RCVD, RECINFO, RECINFO2, and RECINFO3 fields. <br>
			The list of workable multipliers is automatically created.

	'''Multiplier exception considerations'''		'''Multiplier exception considerations'''

Sm7iun: /* Multiplier keys */

2026-03-30T04:38:11Z

Multiplier keys

← Older revision		Revision as of 04:38, 30 March 2026
Line 1,909:		Line 1,909:
	\|-		\|-
	\| <tt>REMOVE_DXCC</tt>		\| <tt>REMOVE_DXCC</tt>
	\| The value of the multiplier with a "*BBB" suffix stripped.		\| The value of the multiplier with a "*BBB" suffix stripped. Only meaningful for HQ multiplier.
	\|-		\|-
	\| <tt>LETTER1</tt>		\| <tt>LETTER1</tt>

Sm7iun: /* Multiplier keys */

2026-03-30T04:34:25Z

Multiplier keys

← Older revision		Revision as of 04:34, 30 March 2026
Line 1,797:		Line 1,797:
	\|-		\|-
	\| '''MULT1_DISPLAY''' '''MULT2_DISPLAY''' '''MULT3_DISPLAY'''		\| '''MULT1_DISPLAY''' '''MULT2_DISPLAY''' '''MULT3_DISPLAY'''
	\| Text to show in MULT column. Syntax: MULT1_DISPLAY=''regex;string''. The ''regex'' can be omitted. Example: <tt><nowiki>MULT1_DISPLAY=DEST->DXCC:^(K\|KL\|KH6)$;S</nowiki></tt> Example: <tt>MULT1_DISPLAY=FN</tt>		\| Text to show in MULT column. Syntax: MULT1_DISPLAY=''regex;string''. The ''regex'' can be omitted. Example:<br><tt><nowiki>MULT1_DISPLAY=DEST->DXCC:^(K\|KL\|KH6)$;S</nowiki></tt><br>Example:<br><tt>MULT1_DISPLAY=FN</tt>
	\| Default value: None		\| Default value: None
	\|-		\|-

Sm7iun: /* Multiplier keys */

2026-03-30T04:33:48Z

Multiplier keys

← Older revision		Revision as of 04:33, 30 March 2026
Line 1,821:		Line 1,821:
	\|-		\|-
	\| '''MULT1_CONT_LIST''' '''MULT2_CONT_LIST''' '''MULT3_CONT_LIST'''		\| '''MULT1_CONT_LIST''' '''MULT2_CONT_LIST''' '''MULT3_CONT_LIST'''
	\| List used when MULT is of type CONT. '''Important:~~'''~~ Antarctica is not included by default.		\| List used when MULT is of type CONT. '''Important: Antarctica is not included by default.'''
	\| Default value: EU;NA;SA;AS;AF;OC		\| Default value: EU;NA;SA;AS;AF;OC
	\|-		\|-

Sm7iun: /* Multiplier keys */

2026-03-30T04:32:34Z

Multiplier keys

← Older revision		Revision as of 04:32, 30 March 2026
Line 1,781:		Line 1,781:
	\|-		\|-
	\| '''MULT1_FX''' '''MULT2_FX''' '''MULT3_FX'''		\| '''MULT1_FX''' '''MULT2_FX''' '''MULT3_FX'''
	\| A C# expression used to create the effective value of an <tt>FX</tt> type multiplier. The entered string is available in the object <tt>$FIELDVALUE</tt>. For example <tt>MULT1_FX=$FIELDVALUE.Substring(0,$FIELDVALUE.IndexOf('/'))</tt> will make the characters before the slash the actual multiplier.		\| A C# expression used to create the effective value of an <tt>FX</tt> type multiplier. The entered string is available in the object <tt>$FIELDVALUE</tt>. For example<br><tt>MULT1_FX=$FIELDVALUE.Substring(0,$FIELDVALUE.IndexOf('/'))</tt><br>will make the characters before the slash the actual multiplier.
	\|		\|
	\|-		\|-
Line 1,789:		Line 1,789:
	\|-		\|-
	\| '''MULT1_ADD_DXCC''' '''MULT2_ADD_DXCC''' '''MULT3_ADD_DXCC'''		\| '''MULT1_ADD_DXCC''' '''MULT2_ADD_DXCC''' '''MULT3_ADD_DXCC'''
	\| Only used with multiplier type <tt>HQ</tt>. Adds an asterisk and the DXCC entities main prefix to the entered string. Can be reversed using the multiplier exception <tt>REMOVE_DXCC</tt>. Example: <tt>MULT2_EXCEPTION=DEST->RCVD:^R[1-3]$;REMOVE_DXCC</tt> means that HQ stations sending R1, R2, or R3 as exchange will not count for DXCC multipliers. Valid values: YES and NO.		\| Only used with multiplier type <tt>HQ</tt>. Adds an asterisk and the DXCC entities main prefix to the entered string. Can be reversed using the multiplier exception <tt>REMOVE_DXCC</tt>. Example:<br><tt>MULT2_EXCEPTION=DEST->RCVD:^R[1-3]$;REMOVE_DXCC</tt><br>means that HQ stations sending R1, R2, or R3 as exchange will not count for DXCC multipliers. Valid values: YES and NO.
	\| Default value: NO		\| Default value: NO
	\|-		\|-
Line 1,797:		Line 1,797:
	\|-		\|-
	\| '''MULT1_DISPLAY''' '''MULT2_DISPLAY''' '''MULT3_DISPLAY'''		\| '''MULT1_DISPLAY''' '''MULT2_DISPLAY''' '''MULT3_DISPLAY'''
	\| Text to show in MULT column. Syntax: MULT1_DISPLAY=''regex;string''. The ''regex'' can be omitted. Example: <tt><nowiki>MULT1_DISPLAY=DEST->DXCC:^K$\|^KL$\|^KH6$;S</nowiki></tt> Example: <tt>MULT1_DISPLAY=FN</tt>		\| Text to show in MULT column. Syntax: MULT1_DISPLAY=''regex;string''. The ''regex'' can be omitted. Example: <tt><nowiki>MULT1_DISPLAY=DEST->DXCC:^(K\|KL\|KH6)$;S</nowiki></tt> Example: <tt>MULT1_DISPLAY=FN</tt>
	\| Default value: None		\| Default value: None
	\|-		\|-