function get_scoreboard_slot() {
	if (round.used_keyboard) {
		// keyboard is the most like cheating, so it goes first
		return "with_keyboard";
	} else if (round.used_manual_click_touch) {
		// next easiest is clicking with touch (it's an absolute input method, and you can see exactly where you're clicking; you could even line up multiple fingers with targets... actually that might even make it more powerful than the keyboard...)
		return "with_touch";
	} else if (round.used_manual_click_pen) {
		// next easiest is clicking with a pen (it's an absolute input method, but you have to look at the cursor to see where you're clicking)
		return "with_pen";
	} else if (round.used_manual_click) {
		// next easiest is clicking with a mouse (it's relative, but precise and familiar)
		return "with_mouse";
	} else if (round.used_manual_movement_touch) {
		// next easiest is moving the mouse but using the dwell clicker (it's precise but slower)
		// not sure about touch vs pen/mouse in this case, as I don't have a touch screen supporting hover
		return "with_dwell_clicker_touch";
	} else if (round.used_manual_movement_pen) {
		// (see previous comment)
		return "with_dwell_clicker_pen";
	} else if (round.used_manual_movement) {
		// (see previous comment)
		return "with_dwell_clicker";
	} else if (round.used_unknown_input) {
		// this last one is a wild card; it's hard to say whether this condition should be last or first
		// I imagine some other accessibility feature might trigger this
		// Can simulate with:
		// for (const archeryTarget of document.querySelectorAll(".archery-target")) {
		// 	archeryTarget.dispatchEvent(new PointerEvent("click", { bubbles: true }));
		// }
		// Of course, that example is completely cheating, which makes it feel like it should be first,
		// but I suspect if this occurs outside of a test, it won't be due to cheating.
		// Of course, the ranking by "easiness" is only in case you mix input methods in a single round.
		// It might not be the best way to detect a different (unknown) input method.
		// That is to say, there's a different argument for giving this priority.
		return "with_unknown_input";
	} else {
		return "with_head_tracker";
	}
}
@returns {keyof typeof best_times} scoreboard_slot - the slot in the scoreboard for the current input method (the most powerful, if it's ambiguous)

If you for example use the head tracker for one target and then mash Tab+Enter for the rest, that should count as using the keyboard.

Note that pointerType may be "mouse" when using a pen, under some circumstances.
It seems I need to enable "Windows Ink" in the Wacom settings (and re-open the tab, not just reload) to get "pen" as the pointerType.