The Blazin' Pedals Online Racing League is a sanctioning body for simulated auto racing using the NASCAR® Racing 2003 Season software by Papyrus Design Group.
The purpose of Blazin' Pedals Online Racing League is to create and promote a clean, friendly and competitive environment for simulated auto racing. We encourage all competitors in Blazin' Pedals to keep FUN the number one objective. If you lose sight of this goal, it is highly suggested that you locate a new hobby.
A copy of the NASCAR Racing 2003 Season simulation and the official 184.108.40.206 patch as provided on our downloads page.
Registration with the forum boards.
Driver Registration through our website by clicking "Register" at the top of the home page.
Steering wheel and pedals accessory.
Broadband high speed internet connection.
Real full name displayed while in race server. Your screen name ID from the PLAYER INFO screen must have nothing in the FIRST NAME field and your entire name (first and last) in the LAST NAME field.
Up to date uploading/downloading of all necessary car/truck files from our car file manager (CFM). When uploading new files to CFM, use required file naming convention. No person is allowed more than three (3) car files per series, per segment.
Select an available number from the “Available Numbers List” thread in the forums. This number must be used across all participating series. See forums for detailed rules regarding keeping numbers.
All drivers will be expected to maintain control of their race vehicle under all conditions and at all times, including caution periods. Drivers who drive erratically or are unable to hold a suitable line may be asked to leave the event and may be subject to disciplinary action by administration.
Prepare adequately for the announced events. This includes downloads of car files and tracks, offline practice at said tracks, joining TeamSpeak, autochat text checks, and so forth.
Spotters may not always provide completely accurate information. Drivers are strongly encouraged to fully utilize the F2 window and their mirrors to maintain complete awareness of the drivers around them.
All drivers are REQUIRED to respect all other competitors regardless of experience level or speed. Drivers who choose to not respect their competitors will be removed from the league. Respect all drivers as to how you want to be respected.
Handle all problems and disagreements between your fellow competitiors outside of the racing environment through private chat or email. Drivers who choose to debate guilt or fault through in-game chat or TeamSpeak DURING AN EVENT may be subject to suspension regardless of where fault is found to lie in the racing incident in question.
Retaliating in any fashion against another driver will result in sanctions ranging from indefinite suspension to expulsion from the league, based on the incident and BP administrators' discretion.
In-Game Chat Systems
Use Autochat messages to notify fellow drivers of your on-track activities.
Use chat system to warn drivers that you are missing gears for a restart, are damaged, or to pass low or high.
Use chat system to notify administration that you are claiming a caution you caused or were involved in one.
DO NOT use in-game chat for carrying on non-race related conversation, not even during caution periods.
Use TeamSpeak to work out race related situations such as where you're supposed to line up for a restart, whether you are EOLL, etc.
DO NOT use TeamSpeak open channels for carrying on excessive non-race related conversations, especially during caution periods. Drivers need to be able to hear their spotters.
All drivers in TeamSpeak are required to be in the same channel as everyone else. It is your responsibility to setup whisper keys, mute other drivers you want, etc.
Pre-qualifying practice is a time for practice, not goofing off or horseplay. The Drivers' Meeting on TeamSpeak will begin roughly 5-10 minutes before this practice session is complete.
All drivers MUST be present for the Drivers' Meeting in TeamSpeak to go over any important information. Any driver that misses the meeting must forgo qualifying and start the race in the back.
At the conclusion of the practice session, the race server may be reset to allow drivers to get their proper car/truck number and for last second calibrating.
No chatter (TeamSpeak or in-game chat) whatsoever shall occur during the qualifying session.
When the qualifying session begins, all drivers are expected to proceed as soon as possible and complete their qualifying lap(s). Any driver who does not complete qualifying will be positioned wherever scored by the simulation software. If you choose not to qualify, enter the qualifying stage and click “Abort Qualifying Run”.
In some instances and series, qualifying will not be included in the event or guidelines for what part of the track is deemed acceptable as a racing surface will be issued. The rules for qualifying will be determined prior to an event or right before qualifying in TeamSpeak. Administrators reserve the right to ask drivers to save their replays to confirm that they were within qualifying guidelines.
Happy Hour Procedures:
Happy Hour Warmup Session will not be utilized by any racing series.
In the case of broadcast events in which the Warmup Happy Hour Session is required, all racing etiquette that is expected of our members while on the track is to be maintained. Absolutely no careless driving will be tolerated.
For most series here at BP, once the green flag on an event has been displayed, THE RACE CANNOT BE RESTARTED FOR ANY REASON WHATSOEVER. Only the Michigan Circle Track Series and Whelen Modified Series allow a race to be restarted only if the leader has not completed the first lap before a yellow waves.
Drivers being lapped have the right to race to stay on the lead lap. THIS DOES NOT EXCUSE a driver taking aggressive action to wreck the leader if the leader is passing that person to place him/her a lap down. Once a driver is one or more laps down, that driver is expected to give way for other drivers still on the lead lap to pass. If a lapped driver is racing another lapped driver for position, he/she should still be mindful of the leader’s position relative to his/her own, but it becomes more the leader’s responsibility to navigate a safe path around the lapped vehicles.
If a restart will occur with 10 or less laps remaining, ALL LAPPED DRIVERS are required to drive through pit road on the second lap of caution, but stopping in the pit stalls for service is not required. Lapped drivers must still obey all in-game rules regarding the pit road speed limit, heeding to the stop-sign official at the end of pit road, and merging legally onto the racing surface.
Blocking is not allowed until the leader takes 5 to go. Blocking is defined as a driver altering or changing his/her racing line to inhibit or prevent passing, particularly in response to a move made by a driver in behind. A driver who is found guilty of excessive blocking may be forced to serve a "drive through" penalty, issued at the administrators discretion.
Lowlining at superspeedway tracks is not allowed until the leader takes 5 to go. The low line at superspeedway restrictor plate-style tracks is defined as the line that separates the normal racing groove from the apron of the race track, usually yellow or white in color. The leader of a pack must leave at least one lane open between his vehicle and the low line on the frontstretch and backstretch, as well as any other parts of the track that do not require significant turning.
Going below the low line (yellow/white line) at superspeedways to gain inside position on another driver is not allowed at any point in the race. Any driver that goes below this line to gain inside position on the driver in front must lift and allow the driver being passed the opportunity to get back in line. If the passing driver doesn't allow that driver back in line or lift at some point later in the lap to give that spot back, then that driver will be issued a drive through penalty under green or an EOLL penalty if the race is under caution. That driver may serve that penalty during the race if he knows or is made aware that a passing-below-the line violation was committed, but the EOLL penalty can also be enforced after the race is complete if the administrator deems it necessary.
Caution Is Displayed:
There is no racing back to the caution flag until the leader takes 5 to go.
When a caution flag is displayed, drivers MUST HOLD THEIR POSITIONS ON THE TRACK (assuming the race-back-window is not open). Pay attention to your F2 window to observe where you were at the moment the caution lights came on. Arguing over a position as to who was ahead when the caution lights came on can usually be settled by a “Gentleman’s Agreement”. DO NOT expect series administrators to do the impossible when determining who had which position.
After the yellow flag has been displayed, all drivers should begin slowing gradually until reaching pace speed. There shall be no contact between vehicles on the track during a caution or coming to take the caution. This may be construed as a retaliatory act and the offending driver can be penalized accordingly.
There are cases where accidents happen on the track, but the sim does not throw the caution. In any case, administration will never throw a caution to make up for the sim not throwing one.
If you cause a caution, claim it over TeamSpeak and/or by typing in “mine”. If you're not sure if you were the cause of a caution, notify us that you were involved and/or type in “inv”.
If none of the involved parties will claim a caution, then it is strongly suggested that both drivers line up EOLL (end of the longest line) for the next restart. When the incident is reviewed after the race, and it is noted that the driver determined to be at fault for the caution did not line up EOLL for that restart, that driver will be penalized accordingly. This includes penalties for drivers who cause cautions that result in the race ending under yellow who do not go EOLL.
If you cause a caution or are found to be the cause of a caution, you must be EOLL for the next restart. Failure to do so will result in penalties after the race. If you cause a caution that ends the race under yellow, you must get EOLL penalty under that yellow or you will be scored at the end of your last completed lap once it has been reviewed after the race.
A driver who causes a caution will not be credited with leading any laps under that caution should he stay out on the track when everyone else in front of him pits. If a driver does lead a lap under a caution that he caused, any laps that driver led will be credited to the next eligible driver (usually 2nd place) in the running order on a lap by lap basis.
Two-Caution Rule – If you cause or are found to be the cause of two cautions, you must park your vehicle and retire from the event. Any driver who refuses to park his vehicle will be subject to ejection from the race server and further disciplinary action. Any driver who is found to have caused two cautions through post-race replay reviewing but did not park their car after causing the second caution will have his/her lap scoring stopped immediately after the second incident was caused.
Open discussions regarding who caused a caution will not be tolerated and will be looked at in the replay by administration after the race has concluded.
Any driver who does not admit involvement in a caution who was found to have caused it may be asked to serve a drive-through penalty at the start of that series' next race. This is up to the series administrator's discretion.
Any amendments to the Two-Caution Rule is up to each head administrator for a series. Refer to the forums for any series specific modifications to this rule.
Conduct Under Caution:
Under pace laps and caution laps, drivers should maintain an interval of 0.2 to 0.4 second between one another to prevent incidental contact.
Drivers MUST maintain a constant speed while driving under pace conditions after they have caught up to the end of the field or the pace car. This speed will always be the pace car's speed under caution.
Stagger your formation while under caution. ANY DRIVER who inflicts damage on another driver’s vehicle during a pace lap or under caution will be subject to a pass-though penalty the next time by.
Any driver who causes a wreck after the caution is displayed must be EOLL for the ensuing restart. If a driver causes a wreck under a caution that will end the race, even if the race back window is open, that driver may be placed at EOLL in the final results.
Lucky Dogs will not be awarded if the caution comes out with 10 or less laps remaining.
The Lucky Dog will only be awarded to the first driver not on the lead lap at the moment the caution is displayed.
If the driver that would be the Lucky Dog was involved in the caution, fault or not, there is no Lucky Dog and it does not pass on to the next eligible driver.
The Lucky Dog driver must speed down pit road the second time by and restart at EOLL to have administration award a lap back.
All drivers are required to maintain a speed close to the pace car's speed under caution up to the drop of the green flag. There is no need for the driver in charge of leading the field to “catch up” to the pace car as it peels off the track and speeds ahead of the field on pit lane.
The sim will restart the race, not the leader. The leader does NOT have the choice of accelerating when he wants. The Michigan Circle Track Series and the Whelen Modified Tour Series are the only series where the leader can dictate when he wants to go.
Being more than 0.2 seconds behind the driver in front of you is considered lagging back to make a run on the field for a start/restart. Jumping the restart will NOT be tolerated.
Pulling alongside on someone's inside before the start/finish line is allowed, but the sim will determine whether the move was legal or not if a pass was made. Expect to serve any black flags issued by the sim for illegally passing before the line.
If a driver passed on the inside in order to avoid a wreck ahead and received a sim-issued black flag, it will be up to administration to determine whether it will be cleared.
Indicate your intention to pit to those racing around you on the track by utilizing in-game Autochat, then carefully move to the preferred groove for access to pit lane.
Use access roads for entering and leaving the pits whenever the sim enforces them. However, administration reserves the right to change the location as to where drivers must go to enter the pits and where drivers will be allowed to merge in order to ensure a safe and competitive atmosphere.
It is legal to pass on pit road on either side after crossing the pit road entry line. It is up to you to travel at the pit road speed limit. If you are going slower than the speed limit, expect to be passed. If someone gets to your inside, you may have to lift to let him by if he has a pit stall further down pit road than yours.
A driver is not allowed to speed down pit road in an attempt to lead a lap while in the process of breaking the pit road speed limit. Credit for any lap led this way will instead go to the driver who would have led the lap under legal circumstances, and any driver caught doing this will be issued a warning after the race. If it occurs a second time after the driver has been warned, the penalty escalates to a black flag that will be served.
A set number of provisional points will be awarded to anyone who misses an event, regardless of the number of drivers who participated in the missed race. The number of provisional points awarded to a driver for missing a race is different based on the series.
Administration reserves the right to change the number of provisional points that a driver would receive for any series at any time.
Any driver who flames another, through in game chat or TeamSpeak will be ejected from the race server and TeamSpeak.
If you are being disruptive on TeamSpeak, you may be ejected from TeamSpeak. This includes excessive discussions regarging claiming cautions and non-race related chat.
If administration feels a driver is acting in an unsportsmanlike manner for any reason, that driver may be ejected at administrations' discretion.
Be aware of your connection quality during an event by utilizing the Ctrl+C function.
If you have been notified by multiple drivers that you are severely warping, you must do one of the following:
Pull into the pit to wait and see if your connection quality improves.
Drop to the rear of the field by moving way out of the preferred groove and allowing others to pass without contesting them.
Enter the pit and exiting from the event. Any driver who does not conform will be ejected from the server and be charged with any cautions as a result of accidents that happened from the warp.
A driver who spontaneously disconnects from the race server may reconnect to resume racing. Repeated disconnects and reconnects may result in an administrator using discretion in refusing further reconnections from that driver.
Laps that a driver loses as a result of being out of the server while he tries to reconnect will not be given back when the driver returns to the race.
If a race is being broadcasted, no reconnects will be allowed if a driver falls out of the race server. Anyone attempting to reconnect will be ejected from the race server.
Any driver who races under a name who is not his own is considered to be cheating and will not be tolerated. No fake names or substitute drivers are allowed.
Any use whatsoever of performance enhancing aids outside those available in the sim is considered intentional cheating. This will not be tolerated, period. If it is determined that a driver is found guilty of this, a discussion among administration will be held and that driver will be indefinitely suspended from the league. If expulsion from the league is deemed necessary, that action will be taken for that driver.
Protest & Grievance Policy:
A driver involved with any incident where they feel circumstances are questionable, whether it be with another driver or with sim scoring, may file a protest with administration. That protest must be filed with the Series Head Administrator by within 24 hours of the conclusion of the event. All protests must include the following:
The driver’s name and car/truck number filing the protest or grievance
The driver’s name and car/truck number whom the protest or grievance is being filed against, if the incident involved another driver
The date and/or event name in which the incident occurred
The approximate lap of when the incident occurred
A brief synopsis of the incident from the plaintiff’s perspective
A replay of the incident that includes two laps before and two laps after the incident. Drivers must zip up their replay clips of the incident before uploading them to the website under the "Members" section of the front page.
IF YOU DO NOT HAVE A REPLAY TO SUPPORT YOUR ARGUMENT, your protest or grievance is instantaneously null and void. No exceptions, no questions asked.
Once a protest or grievance is filed, if another driver is involved, the defendant will be notified via email and given two (2) days to respond and submit a replay in his defense, along with a testimony of the event from their perspective. If the defendant cannot produce a replay, his reference replay will be, by default, the replay saved by the head administrator.
Keep in mind, while reviewing the race footage, if the driver filing the protest or grievance is observed to be in violation of league rules, that driver may be levied penalties outside of the final ruling from the original protest. The moral of this story is to choose your battles carefully. Objectivity and fairness will rule supreme.
Drivers who choose to abuse the Protest and Grievance Policy by filing complaints over and over numerous times every week will find their complaints falling on a deaf ear once this trend is observed. Let’s all be mature here and make sure we are dealing with a true violation of Series policy before taking action.
ALL RULINGS BY ADMINISTRATION WILL BE BINDING AND FINAL. There is no appeals process, and no debates or arguments will be entertained after the final ruling for a protest.
Administration reserves the right to amend and/or edit the official rulebook as the need arises with the goal of continuing to provide and promote the best online racing environment possible and will notify all drivers of any amendments or additions to the official rulebook as they are made.
Visit the forums for series specific protocols and points structures, as well as any other rules that certain series have in place for that night of racing.
As of 2010, blazinpedals.net is a driver owned online racing league. The league will be governed by the Racing Administrators and League President. There are guidelines as to how decisions shall be made in the league as far as leadership, rule changes, mod and night changes, etc. This is defined here and may not be changed without going through the League Board.
The League shall be governed by a League President. The President shall be chosen by vote by the league's Administration and Board.
The League Board shall be chosen by the League President, provided they fit the guidelines for being a Board member.
If there are any changes the League President wants to see happen, the President must take his proposed changed to the Board for vote. If the board votes yes, the change can be put into place. No changes may be made without going before the Board. Changes must be approved by a majority vote.
To be an administrator at Blazin' Pedals, you must race at BP full time. While being a Blazin' Pedals admin, you may not run in other leagues without the expressed permission of the League President.
A Board Member is a voting member of the Blazin' Pedals administration. To be considered for a spot on the League Board, you must race full time at Blazin' Pedals and be willing to put forth extra time into the league development if asked to do so.
The criteria for League President criteria is the league President must run at Blazin' Pedals full time, help the league financially on a monthly basis, and put extra time into the development of Blazin' Pedals.
Extra time for league development is defined as assistance with special league events, updating the website, or any other duties that would not be considered "regular administrator duties".
Administrators are encouraged to run their race nights as they would like with the exception of any rule changes, mod changes, or night changes without the approval of the League President and Board.
Voting on League President may happen at the end of the season annually. On November 1st, the current League President will put a poll up for the admins to vote on as to whether they would like a Presidential vote for the next year. If all of the admins feel that the current President is doing everything to satisfaction, they may choose to not hold a vote, allowing the current League President to automatically serve another term. If one administrator votes "yes" to have a Presidential vote, then nominations will be accepted for voting. The vote shall be finalized for the following years leadership no later than November 30th. All administrators are required to cast a vote. It is their obligation as an administrator at Blazin' Pedals. The new League President will Take over January 1st.
Promoting a member to administrator status must be done through a vote by the League President and Board. This vote must be unanimous. Any league administrator can also be removed from duty the same way.
At the conclusion of each league event, the the administrator may ask the event's winner and up to three other participating drivers chosen at his discretion to upload a replay of his/her entire recorded event to the website.
Any driver failing to upload a replay upon an administrator's request after the race may be subject to penalties in the form of the loss of championship points or finishing position of the replay-requested race.
Any driver who fails to upload requested replays on three separate occasions will be further penalized by the league, including but not limited to indefinite suspension from all league sanctioned events to expulsion from the league.
Drivers must zip up their replays before uploading them to the website under the "Members" section of the front page.
Modifications to your Core.ini file located in your Papyrus\NASCAR Racing 2003 Season\core.ini must be made in order for league admins to view all aspects of your car's telemetry in your replay.
Open the Core.ini file and scroll down until you see the following lines of code, then change the lines to match what is here.
Register for Blazin Pedals NASCAR 2003 League - Loaded in 0.093 seconds
5/21/2013 1:02:35 AM Copyright 2013 - Blazin' Pedals
All Rights Reserved - No part of this site may be reproduced
or used without express written permission of the entire Blazin' Pedals Staff
Blazin' Pedals is not endorsed by or affiliated with iRacing Motorsport Simulations, LLC or any of its
licensors. Trademarks are the property of their respective owners.
Game content and materials copyright iRacing Motorsport Simulations, LLC and its licensors. All Rights Reserved.