ACC [PC] Protests and Penalty Zone

Discussion in 'Assetto Corsa Competizione PC Monday Night' started by Anon666, Dec 14, 2019.

Thread Status:
Not open for further replies.
  1. Anon666

    Anon666 Destitute Gentleman Driver Team Raceonoz Super ROOZ

    Posts:
    5,014
    Likes:
    3,085
    PSN ID
    Anon666
    This isn't a place for discussions. If you want something looked at, read the info here and follow instructions.

    Updated (22/01/2022) - Protests to be submitted via Discord now!
    Current Stewards for the ACC Leagues consist of members of the Trusted Drivers Panel and the current Admin Team.
    Current Admin Team:
    @krunch, @nanlatt, @CornfordCaster, @Rolz

    If you are involved in an incident that you believe was another driver's fault, first contact the driver you are making a complaint against and attempt to resolve the issue via PM, chat or Discord.

    ACC - DRIVING STANDARDS ZONE
    Category Structure:

    For general users:
    ACC - DRIVING STANDARDS ZONE
    # help-and-info ← help channel
    # race-replay-links ← find race replay links here
    # tdp-review-list ← list of all incidents TDP have noticed this week
    # submit-report ← ticket system for drivers to submit something
    # review-outcomes ← all reviewed incident outcomes for the week get listed here

    For Admins and TDP:
    ACC - DRIVING STANDARDS ZONE
    # help-and-info
    #tdp-instructionsinstructions for TDP's incident review tasks
    # race-replay-links
    # tdp-review-list
    # submit-report
    #* start-a-reviewprivate ticket system for TDP to create review discussions
    # review-outcomes
    #* incident-historyadministrative archive of incident reviews
    #* tdp-chatprivate TDP text chat for general discussions
    @* TDP Voice Chatprivate TDP voice chat

    *private channels viewable only by TDP and Admins/Mods

    The Incident Review Process:
    (we are using a Monday night race for this example)

    • The TDP starts privately reviewing a race immediately after that race has finished using voice and text chat while reviewing the race replay. The TDP will then post an incident review list in the #tdp-review-list channel. TDP Incident reviews can continue to be added to the list anytime from the end of the race until 48 hours later (eg. midnight Wednesday).

    • Private TDP deliberation on both their own incident reviews as well as driver submitted reports can start immediately without needing to hear from drivers involved. The TDP does not require driver submissions in order to make conclusions and hand out penalties and warnings. However, any driver submissions received (before the deadline) will be fully considered by the TDP.

    • Drivers do not get notified of incident reviews. Drivers need to check the #tdp-review-list channel themselves as well as any submitted report tickets by fellow drivers to see if they are included in a review/protest/report. These may appear anytime from the end of the race until 48 hours later (eg. midnight Wednesday).

    • Drivers can submit any of the listed types of report via the #submit-report ticket channel as long as it is submitted before the deadline. The deadline varies depending on the type of report being submitted. See Report Types below for the permitted report types and their deadlines. Note that all submissions into this channel are viewable by all league members.

    • Drivers do not get notified of incident outcomes. Drivers need to check the #review-outcomes channel themselves to see all review outcomes.

    Report Types:
    • protesting another driver for an incident that you were involved in during the event
    (deadline: 48hrs after race - eg Midnight Wednesday)

    • reporting an incident that you witnessed and were not directly involved in during the event but that you feel warrants a review.
    (deadline: 48hrs after race - eg Midnight Wednesday)

    • reporting yourself for an incident that you were involved in during the event
    (deadline: 48hrs after race - eg Midnight Wednesday)

    • providing an explanation/admission/rebuttal for an incident that you were involved in during the event.
    (deadline: 72hrs after race - eg Midnight Thursday)
    • can be whether it was protested or not
    • can include evidence of network issues, game code/behaviour issues, etc.

    • requesting TDP feedback on any other type of incident or situation during the event.
    (deadline: 72hrs after race - eg Midnight Thursday)

    • requesting TDP feedback on any driving standards topic not directly related to the event.
    (deadline: none - ask anytime)

    • praising another driver's racing, sportsmanship or conduct during the event.
    (deadline: none - praise people anytime)

    Note that submissions into the #submit-report channel are viewable by all league members

    Report Requirements:
    • your report must include:
    • your race name, discord name and race number
    • other driver(s) race name, discord name and race number
    • lap number of incident/occurance
    • reason/description of incident/occurance
    • video of incident/occurance with the following requirements:
    • ACC Replay footage showing in-car camera angle for both cars
    • ACC Replay footage showing external chase camera of both cars
    • HUD must be visible in the replay footage

    ------------------------------------------------------
    Previous Info (pre September 2022)
    If a driver still wishes to submit a protest the following procedure is to be followed:
    • Go to discord channel #submit-protest under the PROTEST & PENALTY category. This will create a new channel specifically for that protest. A moderator will rename the protest.
    • The protesting driver will submit their protest in the format described in the newly created channel. The video evidence will be in the format stated in the paragraph below. This driver will then be removed from the channel.
    • The driver being protested will be added to the channel to see the footage and provide a defence. This driver will then be removed from the channel.
    • The stewards will determine who is at fault, the severity of any contact and the severity of any damage/outcome.
    • The stewards will determine the penalty to be issued.
    • Both drivers will be notified of the outcome.
    • The outcome will be posted to the forum.
    • A transcript of the protest decisions will be stored in channel #protest-history
    The following penalty table will be used in ACC as a general guide only, with penalties for grey areas being adjusted by the Admin Team where there may be a penalty required.

    RaceOnOz.com ACC League Penalty Table
    [​IMG]

    ------------------------------------------------------
    Previous Info (pre 2022)
    Updated (23/10/2020)
    Current Stewards for ACC are as follows
    @Flamebadger , @SteveDrivingSlowly , @nanlatt , @krunch ,@Rolz and @Anon666

    As per our COC, if you need to make a complaint against a driver you are expected to follow these procedures
    1: Contact the driver you are making a complaint against and attempt to resolve the issue via PM, chat or discord.
    2: If you are unable to do so, contact a mod via PM only using the heading "Racing Complaint"
    3: In the complaint message you are to supply the following information;
    a: Drivers name
    b: Time and date of the incident
    c: Car driven by driver
    d: Any details of the incident and what you think happened
    (Incidents are NOT to be discussed in the Racing League thread, they are to be done via PM ONLY)
    4: if a driver want to protest a race incident they must make us aware by PM before midnight on the Wednesday following the race
    5: we will request a video from the drivers involved
    6: we will make the driver being protested against aware of the protest so they can prepare a defence if they feel they need to
    7: Once the result is handed down, any appeal will be forwarded to KoAsTR and his decision will be final.
    8: the results will be posted in the stewards thread with the ruling as to why or why not there was any penalty applied.

    The following penalty table will be used in ACC as a general guide only, with penalties for grey areas being adjusted where there may be a penalty required.

    [​IMG]
    Last edited by a moderator: Sep 22, 2022
    pb1, Hatfield, Rolz and 2 others like this.
  2. Anon666

    Anon666 Destitute Gentleman Driver Team Raceonoz Super ROOZ

    Posts:
    5,014
    Likes:
    3,085
    PSN ID
    Anon666
    NB - Protest lodged by @tezpez85 against @Godzilla from race 2, Monday 9th Dec has been upheld by mods.
    Penalty - 10s to be added to race time. @Rolz or @marty or @SteveDrivingSlowly can you guys please update the race results, thanks.


    NB - I have modified the base procedures slightly to have all future protests to be lodged by midnight on the Wednesday following the race.
  3. tezpez85

    tezpez85 Professional Gold Member

    Posts:
    447
    Likes:
    694
    Here is a tutorial for anyone with an Nvidia graphics card on how to record video footage of a replay in case you need to post a video as part of this process:



    Don't forget to get both drivers viewpoints, and keep the HUD on (in ACC replay settings) so that the mods can see throttle / brake inputs.
  4. Wally

    Wally Team Driver

    Posts:
    334
    Likes:
    638
    Coanda, Rolz, tezpez85 and 1 other person like this.
  5. marty

    marty AC Server Legend

    Posts:
    1,631
    Likes:
    2,417
    From round 1 @Shawn Jacobs got penalised, with the stewards report being.
    For this incident.
    SteveDrivingSlowly and tezpez85 like this.
  6. Rolz

    Rolz ACC Nutter Team Raceonoz Gold Member

    Posts:
    1,853
    Likes:
    2,136
    ACC Season 2 Monday's rnd 10 Paul Ricard 90 minute Enduro
    @Daniel Benefield got penalised, with the stewards report being.
    @marty or @SteveDrivingSlowly can you guys please update the race results
  7. Hatfield

    Hatfield GT7 League & Teams Championship Organiser Team Raceonoz Gold Member Super ROOZ

    Posts:
    18,109
    Likes:
    17,585
    PSN ID
    DRZ-Hatfield
    FYI I updated my penalty table in the pit lines area if you want to relink the new table here instead of the old one you currently have
    Rolz and SteveDrivingSlowly like this.
  8. incey

    incey World Champion

    Posts:
    2,791
    Likes:
    2,311
    PSN ID
    incey
    your ongoing work to keep raceonoz functioning is appreciated
    UrsineSaturn9, Hatfield, Rolz and 3 others like this.
  9. Anon666

    Anon666 Destitute Gentleman Driver Team Raceonoz Super ROOZ

    Posts:
    5,014
    Likes:
    3,085
    PSN ID
    Anon666
    That would be great Hat, I think you deserve a little gift. Take 5 mins out of your day and watch some racing:
  10. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 4, Rnd 2, the stewards reviewed incidents that occurred on Lap 1 between turn 2, Crawthorne, and turn 5, Barbeque.

    T2 - No penalties or warnings are being issued in respect of this incident, and has been adjudged a racing incident. This commenced with a concertina on the inside line of T2 between cars 777, 197 and 114 amongst others, leading to contact between 114 into 197. Due to the nature of a race start, unfortunately others were also caught up. The admin team have reviewed this incident from multiple driver perspectives, chase cams and various other camera views, and taken into account driver control inputs.

    No one involved in the incident was being overly aggressive, piled into the corner with too much speed or was too late on the brakes. No driver or drivers were wholly or predominantly responsible.

    T5 - No Penalties and a single warning has been issued in respect of the incidents at this corner, the first of which was between cars 133 and 333, which has been deemed a racing incident with neither driver wholly or predominantly responsible.

    In respect of a second incident between Cars 75 @THE_UNDER_STUDY and Car 18 @Jeremy Talbot, @THE_UNDER_STUDY has been adjudged at fault for moderate avoidable contact that subsequently also severely impacted car 888, and has been hereby issued a warning for being at fault for avoidable contact.

    Video of incident:


    No change to the results of the Round are recorded in relation to these two incidents.
    Last edited: Oct 14, 2020
  11. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Final update: Season 4, Rnd 2.

    A 25 second time penalty has been issued to car 326, @isitactuallyphilippa for the following incident:



    A 25 second time penalty and a warning has been issued to car 888, @Dat Guy Tom for the following incident:



    The results for Round 2 will be updated today.

    This post concludes the Stewards' report for this round.
    krunch likes this.
  12. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 4, Rnd 3

    A 25 second time penalty has been issued to Car 26, @Radtaco, for the following incident:



    The results for Round 3 will be updated in due course.

    This post concludes the Stewards' report for this round.
    Radtaco likes this.
  13. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 4, Rnd 4

    A 25 second time penalty has been issued to car 2, @nanlatt, for the following incident.



    Round results will be updated shortly.

    This concludes the Stewards' report for this round.
    krunch and SteveDrivingSlowly like this.
  14. SteveDrivingSlowly

    SteveDrivingSlowly ACC Results Ste(ve)ward

    Posts:
    832
    Likes:
    1,333
    Season 4, Round 5

    An incident between cars 33 and 101 which also affected 191 on Lap 25 was reported and has been judged a racing incident, with no warnings or penalties issued.
  15. tezpez85

    tezpez85 Professional Gold Member

    Posts:
    447
    Likes:
    694
    Will just say, pretty bloody useful to have this zone eh? ;)
    krunch and SteveDrivingSlowly like this.
  16. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 4, Round 5
    A 25 second time penalty has been issued to Car 777, @Denis Strelnikov for the following non-redressed incident with Car 191 on lap 9:



    Round results will be updated and finalised shortly.

    This concludes the Stewards' report for this round.
  17. SteveDrivingSlowly

    SteveDrivingSlowly ACC Results Ste(ve)ward

    Posts:
    832
    Likes:
    1,333
    After more discussion the team has made a slight change to the ruling here. A warning will be issued to car #101 as this was a high risk move (going three wide at the kink). Coming from behind #101 had the best opportunity to control the risk that lead to the incident, even though it has not been deemed predominantly or fully any single driver's fault.
    krunch likes this.
  18. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 4, Round 6, Race 1

    A 25 second time penalty has been issued to car 31, @CornfordCaster, for the following incident with car 7 on lap 13 of race 1:



    The Race result has been updated to reflect this time penalty.
    krunch and CornfordCaster like this.
  19. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 5, Round 5, Race 1

    A 25 second time penalty has been issued to car 111, @jlynn777 for the following incident with car 802 on lap 2 of race 1:



    The race result will be updated shortly.

    This concludes the Stewards' report for this round.
    SteveDrivingSlowly likes this.
  20. Flamebadger

    Flamebadger ACC Server Legend

    Posts:
    180
    Likes:
    452
    Season 5, Round 7

    An 80 second time penalty has been imposed on car #888, @Dat Guy Tom, for the below starting infringement, being a jump / out of position start and exploitation of ACC's ghosted starting procedure.



    The race result will be updated shortly.

    All drivers are reminded that they must not gain advantage at the start by exploiting the ghosted start procedure.

    This concludes the Stewards' report for this round.
    tezpez85, jlynn777, Godzilla and 2 others like this.
Thread Status:
Not open for further replies.