NHRL Open Rules - 2026 - Revision history

RickyWillems: /* Appendix A: Judging Criteria */ Wording Improvements

2026-04-20T16:14:46Z

Appendix A: Judging Criteria: Wording Improvements

← Older revision		Revision as of 16:14, 20 April 2026
Line 762:		Line 762:

	== '''Appendix A: Judging Criteria''' ==		== '''Appendix A: Judging Criteria''' ==
	The following is the core of the 2026 Judging criteria. This is just the basics of how judges will score fights. Some minor details may change over the course of the season. We will cover more detailed, specific cases soon.

	===Overview===		===Overview===
	The 2026 Judging Criteria is ~~intended~~ to ~~inspire fights that are~~ exciting ~~and~~ ~~full of action~~. It is based on the following premises:		The 2026 Judging Criteria is designed to reward exciting, action-filled fights. It is based on the following premises:
	* Every robot must have an active weapon.		* Every robot must have an active weapon.
	* That weapon must be able to cause harm to its opponent.		* That weapon must be able to cause harm to its opponent.
	* '''Harm is not necessarily damage,''' but the weapon must clearly put the opponent in a worse place than before, without the attacking robot necessarily present.		* '''Harm is not necessarily damage,''' but the weapon must clearly put the opponent in a worse place than before, without the attacking robot necessarily present.
	* A reasonable spectator watching cageside should be able to tell when a weapon is being used, and how it can cause harm.		* A reasonable spectator watching cageside should be able to tell when a weapon is being used, and how it can cause harm.
	* Judges should measure both the intention to cause harm, and the effectiveness of that attempt, ~~weighing the~~ effectiveness more heavily ~~than the intention~~.		* Judges should measure both the intention to cause harm and the effectiveness of that attempt, weighting effectiveness more heavily.

	====Harm====		====Harm====
	Harm is achieved when an opponent is ~~put~~ in a clearly worse state than before the attack without requiring the ~~active~~ ~~robot’s~~ presence.		Harm is achieved when an opponent is left in a clearly worse state than before the attack, without requiring the attacking robot's continued presence. The following are examples of causing harm that judges will favor. This is not a complete list.
	The following are examples of causing harm. These will be favored by our judges. This is not a complete list.
	* Striking your opponent with a fast-spinning kinetic weapon.		* Striking your opponent with a fast-spinning kinetic weapon.
	* Torching your opponent for a significant amount of time with effective fire.		* Torching your opponent for a significant amount of time with effective fire.
Line 781:		Line 778:
	* Manipulating your opponent in a way that requires them to self-right, unstick themselves, or request an unstick.		* Manipulating your opponent in a way that requires them to self-right, unstick themselves, or request an unstick.

	The following are examples of not ~~causing~~ harm. These will ~~generally~~ not be favored by ~~our~~ judges, and if done too often, will ~~lose~~ points ~~for~~ ~~the~~ ~~competitor~~ ~~instead of gaining points~~. This is not a complete list.		The following are examples of actions that do not cause harm. These will not be favored by judges, and if done too often, will cost points rather than earn them. This is not a complete list.
	* Pinning your opponent without using an active weapon capable of causing harm. (Bots without working active weapons will get some credit for wall slams and brief pins.)		* Pinning your opponent without using an active weapon capable of causing harm. (Bots without working active weapons will get some credit for wall slams and brief pins.)
	* Lifting your opponent off the ground just enough so they cannot drive (through a lifting arm or passive bot geometry)		* Lifting your opponent off the ground just enough so they cannot drive (through a lifting arm or passive bot geometry)
	* Flipping your opponent a moderate ~~amount of~~ distance ~~in the air~~, so after they land, ~~they~~ drive away unharmed.		* Flipping your opponent a moderate distance, after which they land and drive away unharmed.
	* Tapping your opponent with an arm.		* Tapping your opponent with an arm.

Line 794:		Line 791:

	===Attack===		===Attack===
	The Attack category ~~quantifies~~ how ~~significantly~~ each bot initiated attacks ~~using~~ their active weapon ~~with~~ intent to cause harm, and ~~successfully~~ ~~attacked~~ in ~~a way that~~ caused ~~harm at a significant magnitude~~.		The Attack category measures how effectively each bot initiated attacks with their active weapon, weighing both intent to cause harm and the magnitude of harm caused.

	Judges will score Attack on the following scale.		Judges will score Attack on the following scale.
Line 805:		Line 802:
	* Bot B initiated and won almost all attacks. (0-5)		* Bot B initiated and won almost all attacks. (0-5)

	Judges will base this ~~decision~~ on the ~~amount of~~ harm each bot attempted ~~to inflict,~~ and successfully inflicted~~, on their opponent~~. We ~~expect~~ ~~competitors~~ to attack consistently throughout the fight ~~at a reasonable pace.~~ If a competitor spends a significant amount of time avoiding contact and running away from the opponent, they will lose points in this category.		Judges will base this on the harm each bot attempted and successfully inflicted. Competitors are expected to attack consistently throughout the fight. If a competitor spends a significant amount of time avoiding contact and running away from the opponent, they will lose points in this category.

	If scoring is close, judges will consider magnitude of successful attacks first, number of successful attacks second, and number of attacks initiated third. Consider a hammersaw that spends most of the match lining up a good hit, versus a shell spinner that is poised to deliver hits frequently. If shell spinner’s attacks frequently but with attacks that don’t do a lot of damage, and the hammersaw attacks only a few times but with massive hits that change the flow of the fight, the hammersaw should win Attack, as the magnitude of its hits were higher and it spent most of the fight intending to attack.

			When scoring is close, judges will consider magnitude of successful attacks first, number of successful attacks second, and number of attacks initiated third. For example, a hammer-saw that attacks only a few times but lands massive, fight-changing hits should win Attack over a shell spinner that attacks frequently but with little effect.
	Exact details on how each bot type scores Attack are beyond the scope of this core document, but will come soon.

	====Effect vs. Intent====		====Effect vs. Intent====
	Judges should consider whether a bot is ~~using their~~ active weapon ~~to make an attack,~~ and whether the attack was effective. ~~This~~ is how ~~they~~ should ~~score~~, from highest~~-scoring~~ to lowest~~-scoring~~. This is not a specific scoring rubric ~~(it does not necessarily map to the 5 points of Attack given out), but it is an illustration of how judges should prioritize different levels of attack~~.		Judges should consider both whether a bot used its active weapon and whether the attack was effective. The following illustrates how judges should prioritize different levels of attack, from highest to lowest. This is not a specific scoring rubric.

	* (Highest-scoring) A bot that attacked very effectively using its active weapon, to a degree of great magnitude. This should have a higher Attack score than…		* (Highest-scoring) A bot that attacked very effectively using its active weapon, to a degree of great magnitude. This should have a higher Attack score than…
Line 949:		Line 944:
	\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]		\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]
	\|}		\|}
	[[Category:Information]]		[[index.php?title=Category:Information]]

Paxmorningstar at 16:45, 10 April 2026

2026-04-10T16:45:57Z

← Older revision		Revision as of 16:45, 10 April 2026
Line 949:		Line 949:
	\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]		\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]
	\|}		\|}
	[[~~index.php?title=~~Category:Information]]		[[Category:Information]]

RickyWillems: /* Hazardous robots and behavior */

2026-03-07T15:14:19Z

Hazardous robots and behavior

← Older revision		Revision as of 15:14, 7 March 2026
Line 615:		Line 615:
	Note that, generally, if a robot becomes entangled, high centered, or otherwise affected by parts or materials torn off of its opponent, this will not be considered entanglement.		Note that, generally, if a robot becomes entangled, high centered, or otherwise affected by parts or materials torn off of its opponent, this will not be considered entanglement.

	=== '''Hazardous ~~robots~~ and ~~behavior~~''' ===		=== '''Hazardous Robots and Behavior''' ===
	If the Referee or Tournament Stewards deem a robot to be a hazard to the crowd, crew or competitors, or if a robot is inflicting considerable damage to the arena, the Referee may elect to end the fight early. In this case, the winner is determined by judges’ decision.		If the Referee or Tournament Stewards deem a robot to be a hazard to the crowd, crew or competitors, or if a robot is inflicting considerable damage to the arena, the Referee may elect to end the fight early. In this case, the winner is determined by judges’ decision.

RickyWillems: /* Introduction and Notes */

2026-03-06T20:45:22Z

Introduction and Notes

← Older revision		Revision as of 20:45, 6 March 2026
Line 9:		Line 9:
	* Improved competitor experience		* Improved competitor experience
	* Writing for the majority of builders, allowing flexibility to address outlying issues		* Writing for the majority of builders, allowing flexibility to address outlying issues
	The posted Spirit of the Rules, Bot Design Rules, and Tournament Format sections are complete and final in scope and intent, but may have wording changes in the coming weeks. Other sections, including Judging Criteria and Event Procedures are still being worded, but the changes being made are described [https://docs.google.com/document/d/14OYesIgwHHfaJb3aGbDr8YHLzMYVp2nX9tY4q2q4Br8/edit?usp=sharing in this document,] along with highlighted comparisons changes made to the Bot Design Rules between 2025 and 2026.

	Any changes to these rules will be noted in the [[2026 Rules Change Log]].		Any changes to these rules will be noted in the [[2026 Rules Change Log]].
	== '''The Spirit of The Rules''' ==		== '''The Spirit of The Rules''' ==
Line 951:		Line 949:
	\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]		\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]
	\|}		\|}
	[[Category:Information]]		[[index.php?title=Category:Information]]

Paxmorningstar: Fix broken category tag

2026-02-20T15:41:01Z

Fix broken category tag

← Older revision		Revision as of 15:41, 20 February 2026
Line 951:		Line 951:
	\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]		\|[[File:Division v4 with Weapon Lock.jpg\|center\|500x500px]]
	\|}		\|}
	[[~~index.php?title=~~Category:Information]]		[[Category:Information]]

RickyWillems: /* Size Limitations */

2026-02-19T06:25:31Z

Size Limitations

← Older revision		Revision as of 06:25, 19 February 2026
Line 263:		Line 263:

	==== '''Size Limitations''' ====		==== '''Size Limitations''' ====
	Robots must ~~easily~~ fit within the NHRL fire safety cart ~~for fire or safety emergencies. The cart's~~ approximate ~~inside dimensions are~~ 23" x 23" x 44".		Robots must fit within the NHRL fire safety cart (approximate interior: 23" x 23" x 44").

	Larger robots may be approved if they can be easily and immediately modified to fit into the cart. For example, if a portion of the robot can be bent or removed so the robot fits within the cart. Pre-event approval is required and subject to change if NHRL staff feels the robot cannot be safely enclosed during an emergency.		Larger robots may be approved if they can be easily and immediately modified to fit into the cart. For example, if a portion of the robot can be bent or removed so the robot fits within the cart. Pre-event approval is required and subject to change if NHRL staff feels the robot cannot be safely enclosed during an emergency.

RickyWillems: /* Modular Weapon Systems */

2026-02-19T06:24:09Z

Modular Weapon Systems

← Older revision		Revision as of 06:24, 19 February 2026
Line 229:		Line 229:
	Modular '''''weapon''''' systems are defined as component assemblies that drastically change a robot's weapon type and are interchangeable between fights. For example, a modular weapon system may allow a competitor to choose between horizontal and vertical spinner configurations.		Modular '''''weapon''''' systems are defined as component assemblies that drastically change a robot's weapon type and are interchangeable between fights. For example, a modular weapon system may allow a competitor to choose between horizontal and vertical spinner configurations.

	Modular weapons should be designed as modules, meaning they can be bolted or otherwise attached to a chassis as a unit. ~~Builders~~ may be required to demonstrate effective module swaps within the minimum repair time for their weight class ~~during Safety Inspection~~. A ~~modular design~~ may be required to complete the NHRL ~~DUMMY~~ Test ~~separately for each module~~.		Modular weapons should be designed as modules, meaning they can be bolted or otherwise attached to a chassis as a unit. During inspection, builders may be required to demonstrate effective module swaps within the minimum repair time for their weight class. Each module may be required to separately complete the NHRL Functionality Test.

	All weapon modules must be declared during Safety Inspection at an event's start. Alternative modules must be presented during Safety Inspection, though they need not be installed unless requested by an Inspector. Competitors may be required to demonstrate any applicable weapon locks for the module. Questionable modularity will be assessed by the Tournament Stewards. Modules may be added event-to-event, but must be inspected at a qualifying event to be eligible for use during Championship events.		All weapon modules must be declared during Safety Inspection at an event's start. Alternative modules must be presented during Safety Inspection, though they need not be installed unless requested by an Inspector. Competitors may be required to demonstrate any applicable weapon locks for the module. Questionable modularity will be assessed by the Tournament Stewards. Modules may be added event-to-event, but must be inspected at a qualifying event to be eligible for use during Championship events.

RickyWillems: /* Weapon Systems */

2026-02-19T06:22:04Z

Weapon Systems

← Older revision		Revision as of 06:22, 19 February 2026
Line 222:		Line 222:
	NHRL strongly encourages competitors designing non-conventional weapons to share plans in advance for confirmation. If a ruling is required at a tournament, the robot must complete the "Weapon" portion of the [[Functionality Tests\|NHRL Functionality Test]].		NHRL strongly encourages competitors designing non-conventional weapons to share plans in advance for confirmation. If a ruling is required at a tournament, the robot must complete the "Weapon" portion of the [[Functionality Tests\|NHRL Functionality Test]].

	~~Builders~~ ~~are~~ ~~prohibited~~ ~~from~~ ~~making~~ ~~modifications~~ to a robot that prevent or ~~restrict~~ ~~the~~ ~~robot~~ ~~from harming an opponent~~ as ~~compared~~ to ~~what they~~ described ~~or demonstrated~~ during ~~Safety Inspection~~. Drivers must ~~also~~ ~~consistently~~ ~~attempt~~ to use their ~~robot's~~ weapon ~~in good faith, in accordance with~~ ~~the~~ ~~functionality~~ ~~displayed~~ during inspection. If a robot passes ~~the weapon test~~ but is not driven to ~~consistently,~~ ~~visibly,~~ and ~~obviously harm~~ opponents, Tournament Stewards will be ~~notified and will review~~ footage.		After passing Safety Inspection, builders may not modify their robot in ways that prevent its ability to damage opponents as was demonstrated or described during inspection. Drivers must make consistent good-faith efforts to use their weapon as it was presented during inspection. If a robot passes inspection but is not driven to actively engage and damage opponents, Tournament Stewards will review match footage.

	Builders will be warned for intentionally skirting weapon functionality requirements and may be disqualified or barred from subsequent events.		Builders will be warned for intentionally skirting weapon functionality requirements and may be disqualified or barred from subsequent events.

RickyWillems: /* Weight Exemptions */

2026-02-19T06:18:57Z

Weight Exemptions

← Older revision		Revision as of 06:18, 19 February 2026
Line 190:		Line 190:
	Competitors with hydraulic systems must pre-declare the fluid amount and weight. Fluid weight is subtracted from scale weight. These robots may be subject to random inspections where the hydraulic fluid will be removed and measured.		Competitors with hydraulic systems must pre-declare the fluid amount and weight. Fluid weight is subtracted from scale weight. These robots may be subject to random inspections where the hydraulic fluid will be removed and measured.

	Electronic components ~~like computer systems and sensors~~ dedicated solely to discrete autonomous ~~systems~~ (weapon, drive, self-righting) do not count toward robot weight. Stability control and meltybrain directional processing do not qualify. ~~These~~ ~~systems~~ must be easily removable ~~for~~ ~~weight~~ ~~and~~ ~~inspection~~, or ~~competitors~~ ~~must~~ ~~show~~ components during inspection and bring identical ~~spares~~ ~~for~~ ~~weigh-~~in. ~~These~~ ~~components~~ require NHRL approval before an event.		Electronic components dedicated solely to discrete autonomous functions (weapon, drive, or self-righting) do not count toward robot weight. Stability control and meltybrain directional processing do not qualify for this exemption. To verify exempted weight, competitors must either: (a) make the autonomous components easily removable so they can be excluded during weigh-in, or (b) highlight the components during inspection and bring identical spare components that can be placed on the scale in their stead. Autonomous system weight exemptions require NHRL approval before an event.

	Active cameras or recording equipment do not count toward robot weight but require approval during Safety Inspection. Camera systems conferring competitive advantage via additional weight will not be approved, at NHRL's sole discretion.		Active cameras or recording equipment do not count toward robot weight but require approval during Safety Inspection. Camera systems conferring competitive advantage via additional weight will not be approved, at NHRL's sole discretion.
Line 218:		Line 218:
	Other inventive weapon systems may be approved on a case by case basis.		Other inventive weapon systems may be approved on a case by case basis.

	~~"Thwackbots,”~~ (robots ~~which~~ use momentum ~~created~~ by ~~the robot’s drive-train to~~ ~~‘actuate’~~ an otherwise unpowered weapon) do not qualify as having an active weapon.		“Thwackbots” (robots that use drivetrain momentum to swing or actuate an otherwise unpowered weapon) do not qualify as having an active weapon.

	NHRL strongly encourages competitors designing non-conventional weapons to share plans in advance for confirmation. If a ruling is required at a tournament, the robot must complete the "Weapon" portion of the [[Functionality Tests\|NHRL Functionality Test]].		NHRL strongly encourages competitors designing non-conventional weapons to share plans in advance for confirmation. If a ruling is required at a tournament, the robot must complete the "Weapon" portion of the [[Functionality Tests\|NHRL Functionality Test]].

RickyWillems: /* Locomotion Based Weight Bonuses */

2026-02-19T06:13:40Z

Locomotion Based Weight Bonuses

← Older revision		Revision as of 06:13, 19 February 2026
Line 89:		Line 89:

	=== '''Weight Requirements''' ===		=== '''Weight Requirements''' ===
	NHRL offers three weight classes: 3lb, 12lb, and 30lb. Robots must weigh at or below their class maximum at the start of each fight. Weight bonuses and exemptions may be available per criteria in this document. A ~~robot~~ ~~may~~ ~~only~~ ~~use~~ one weight ~~bonus~~ at a ~~time~~. Weight bonuses and weight exemptions are independent and may be used simultaneously. Builders must declare weight bonus usage before an event begins. Weight bonuses are tied to the robot's archetype, cannot change during an event, and may only change between events per archetype rules.		NHRL offers three weight classes: 3lb, 12lb, and 30lb. Robots must weigh at or below their class maximum at the start of each fight. Weight bonuses and exemptions may be available per criteria in this document. Robots qualifying for both a locomotion and multibot bonus must choose one bonus or the other - weight bonuses cannot be combined. Weight bonuses and weight exemptions are independent and may be used simultaneously. Builders must declare weight bonus usage before an event begins. Weight bonuses are tied to the robot's archetype, cannot change during an event, and may only change between events per archetype rules.

	==== '''Locomotion Based Weight Bonuses''' ====		==== '''Locomotion Based Weight Bonuses''' ====
Line 112:		Line 112:
	\|30 lb		\|30 lb
	\|}		\|}
	~~Robots qualifying for both a locomotion and multibot bonus must choose one bonus or the other.~~ For multibots to qualify for a Non-Traditional Locomotion bonus, all segments must use Non-Traditional or True Walker Locomotion. To qualify for True Walker Locomotion bonuses, all segments must use True Walker Locomotion.		For multibots to qualify for a Non-Traditional Locomotion bonus, all segments must use Non-Traditional or True Walker Locomotion. To qualify for True Walker Locomotion bonuses, all segments must use True Walker Locomotion.

	NHRL has sole and final discretion on locomotion weight bonus awards. True Walker bonuses require pre-registration approval. Older approved True Walker designs may be grandfathered as requirements evolve.		NHRL has sole and final discretion on locomotion weight bonus awards. True Walker bonuses require pre-registration approval. Older approved True Walker designs may be grandfathered as requirements evolve.