Fencing Draft notes:Rules For Managing Incidents
Jump to navigation
Jump to search
Changes for v6.0
- Chapter 4 - Rules for managing incidents is now Chapter 13
- Was 4.1 General
- Removed
- Reason
- Chapter intro added. Only one useful rule in this section, and it has been moved to the next section as 13.1.1, and subsequent rules renumbered.
- 13.2.2
- Insert new rule
- Fencers should discourage their opponent from taking a blow the fencer feels was excessive.
- Subsequent rule renumbered.
- Functional change
- None
- Reason
- There is constant discussion as to if an excessive blow is illegal. I do not believe that it strictly is, but this rule encourages both safety and sportsmanship.
- For notes
- June 2023 - If you think you accidentally hit your opponent too hard, tell your opponent not to take it.
- Was 4.4 Injuries, now 13.3 Injuries, and 13.4 Reporting
- Substantively rewritten to include similar rules from armoured combat for dealing with injuries, information about returning to the field, with particular attention to concussion
- Section added on reporting of injuries and near-misses.
- For notes
- June 2023 - Please note the new rules with regards to concussion, where the injured person must leave the field and cannot participate in combat or training until assessed medically, even if symptoms resolve. New rules in 13.3 and 13.4 have been added about managing injuries and other incidents, and reporting requirements.
- Was, now 13.4 in Weapons failure
- Was 4.6 and 4.7, now 13.5 Other action
- This section has been substantively rewritten.
4.7.2.5
- Was
- The test might be:
- a verbal test to confirm that the person understands the rule in question
- a combat test, where the fencer fights under the supervision of the impartial marshal to confirm that the issue has been resolved.
- Now
- The test might be:
- a verbal test to confirm that the person understands the rule in question
- a practical combat test, where the fencer fights under the supervision of the impartial marshal to confirm that the issue has been resolved.
- Functional change
- None - applying consistent terminology
- Reason
- The handbook currently has two phrases meaning the same component of the authorising process. This combines them.
- For notes section
- No notes required.