Chargement de la page...
Know the rules. Race with respect. A practical guide for every rider, from qualifying to the final flag.
Your account, your UID. Join the correct server before UID grab.
Keep it predictable. Rejoin safely and give back any advantage.
Save the full demo. Report the exact session, rider and incident time.
Account, licence, sign-up and attendance.
Use your own RaceMeUp account and verified game UID, with your real first and last name, nationality and correct race number. Impersonating another rider, organizer, team or staff member is forbidden and results in a ban.
Sharing, borrowing, selling or racing with another rider’s UID or account is forbidden. The EMF penalty schedule applies: first offense, suspension for six rounds; second offense, a one-year ban; third offense, a permanent ban.
Check the required licence, class, bike and race number before entering. Additional series or race rules apply only to that event and cannot weaken this general rulebook. The MX Simulator class and 250/450 eligibility restrictions below apply to the relevant competitions. Permanent-number and exceptional-entry rules must be published for the series.
Be present for UID grab, qualifying, the start and admin checks. Missing the announced window is your responsibility; a late addition is not guaranteed. Ask the listed host about their event.
The right server, clean laps and respect for hotlaps.
Qualify on the server and during the time window assigned to your class and licence. A lap on another server or outside that window may not count.
After a crash or a spoiled lap, give riders on a timed lap room to pass. This applies regardless of pace or position. Do not deliberately block or punt another rider.
Do not request or trigger a restart during active qualifying unless race control authorizes it. Another rider may already be on a timed lap, and a restart can prevent times from being saved.
Missing a timing gate makes a lap invalid, even by a small margin. Times can take a few minutes to appear after a session finishes. A missing time does not guarantee manual restoration; set another valid lap when possible.
Hold your gate position and brake for the riders ahead.
For MX Simulator gate starts, do not move closer to the gate, back up or spin the rear wheel before it drops. Body movement and suspension compression are allowed. If you move accidentally, restore your position or clearly surrender the advantage before joining the race.
Brake in time for the first corner and the riders in front. A crowded start is not permission to deliberately hit or drive through another rider.
Only race control can authorize an event restart. Do not demand a restart because of your own crash or bad start. Follow the host’s instructions if a start is stopped.
Close racing is welcome. Deliberate contact and shortcuts are not.
Firm racing and incidental contact can happen, but leave racing room. Intentional punting, T-boning, brake-checking, retaliation, targeting a rider, deliberate blocking and riding backwards are punishable.
Do not cut inside track markers, abuse resets or bypass timing gates. If avoiding a crash takes you off track, do not cross the whole circuit or gain time or positions. Give back a clear advantage as soon as it is safe.
Check the track and map, wait for a safe opening and yield to riders already racing. Rejoin predictably without crossing their line. The same rule applies to leaders and lapped riders.
If facing the wrong way, use reverse and turn carefully before accelerating in the race direction. Do not accelerate across the track or into approaching riders. Unsafe riding can be penalized even without a collision.
Give way early, without sudden changes of direction.
During a race, when a leader is within about two seconds, prepare a safe place to let them pass. Do not keep blocking once the gap is under one second. A blue flag is a signal to make room, not to stop abruptly in the racing line.
Hold a clear line and move away from the main line when safe. Avoid jumping sideways or making a last-second change as the leader commits to passing. Leaders must pass lapped riders with care.
You may pass a crashed leader if it is safe. Do not force your way past a leader who is already getting up and accelerating. Qualifying follows hotlap priority rather than race position.
Understand the format before entering. The published event settings are the reference.
EMF reference · standard SX
40
timed qualifiers
2 × 20
heats
18 + 4
heats + LCQ
22
finalists
The EMF standard reference is 40 timed qualifiers → two heats of 20 → nine transfers from each heat plus four from the last-chance qualifier (LCQ) → 22 finalists. Heat, LCQ and final durations are published for the event.
The EMF standard reference is 40 qualifiers and two motos. Their combined results determine the event overall. Under this format, a tie in the overall is decided by the better second-moto finish.
The EMF Triple Crown reference takes 18 riders directly from qualifying, then four from an LCQ of the next 22, for three races with a 22-rider gate. The WSX reference uses 22 riders per class, two heats for gate selection, a 450 Superpole for the top five of each heat, and three main races. Use these only when announced for the event.
Under the EMF reference scales, SX awards 26, 23, 21, 19 and 18 points for the top five, then 17 down to 1 for places 6–22. MX and WSX award 25, 22, 20, 18 and 16, then 15 down to 1 for places 6–20. Olympic scoring uses finishing positions, with the lowest total winning. The event must announce its scoring system.
When a series adopts the EMF reference, SX championship ties use main-event wins, then second places; MX uses overall wins, then moto wins. The class restrictions below apply to MX Simulator competitions; career-number and exceptional-entry rules must be published by the series. These references do not override a different format or scoring system shown for a RaceMeUp event.
In MX Simulator Supercross, a 250 champion may defend the title for one additional season, then must move to the 450 class.
A rider who finishes in the top three of a 450 Supercross championship is not eligible for the 250 class. A rider who scores at least 700 points in 450 over the last three seasons is also no longer eligible for 250.
A rider becomes eligible to return to the 250 class after four years without scoring points in the 450 class.
The 450 class (MX1, MXGP, SX1 or WSX) allows bikes from 250 cc two-strokes to 450 cc four-strokes. The 250 class (MX2, Lites or SX2) allows bikes from 125 cc two-strokes to 250 cc four-strokes. Official MX Simulator events use 2013–2018 bikes. A 450 Open event may allow all bike capacities while retaining that year restriction for official events.
Know what is your responsibility and when race control intervenes.
Your connection, computer, game crashes and missed timing gates are normally your responsibility. They do not guarantee a rerun, a late entry or manual lap restoration.
For severe server lag, attack symptoms or data loss, follow the host’s announcements. Race control decides whether to continue, restart, postpone or validate partial results. Decisions must be consistent, documented and reviewable.
Under the EMF penalty schedule, proven cheating or an MX Simulator key ban by JLV results in a three-year racing ban for a first offense and a permanent ban for a second offense.
A proven DDoS attack results in a permanent racing ban and account suspension. Tampering with servers, distributing exploits, fabricating logs or bypassing RaceMeUp validation are also punishable and can lead to a permanent ban.
Report facts through the race page. Save the complete session whenever possible.
Open Protest from the race results and select the actual moto or session, class and rider. Overall is a combined result, not a raced session. Enter the lap or precise timestamps and a clear description. You can report an incident you witnessed, even if you were not directly involved.
Save your own full demo as a backup; a server download is not guaranteed. Full demos are preferred for checking context. GIF, JPEG, PNG, video uploads and evidence links can support the report, but a short clip or screenshot may be insufficient on its own. Race control may request the full demo.
Check the race, session, rider and times before submitting. A report with incorrect details or insufficient evidence may not be reviewable. Include each relevant incident time and follow any protest window published for the event.
Possible penalties include warnings, points or position penalties, disqualification, licence downgrade, suspension, bans, account restrictions or exclusion from a series. Only authorized race control can apply decisions; an accusation does not change a result automatically.
Keep disputes factual, on and off the server.
Chat, voice, protests and public pages must remain respectful. Harassment, threats, hate speech, racist or discriminatory language, and encouragement of self-harm are forbidden.
Follow admins, race directors, marshals and hosts during the event. Raise disagreements through the protest process or contact the organizer after the session. Do not retaliate on track.
If you insult or threaten a rider in the same incident you protest, your protest may be rejected and your own conduct may be penalized.
Respect ownership and permissions when sharing files.
Tracks, skins, models, images, setups and other files must belong to you or be uploaded with the real creator’s permission.
Creators and uploaders remain responsible for copyright, trademarks, licences and redistribution rights. RaceMeUp can remove disputed content and freeze payouts while reviewing claims.
Technical files are protected by default on the Market. The creator must explicitly choose to expose them when the product allows it.
Ready to race?
Read and accept this version before taking part. Event rules also apply: check your series and race page before signing up. Breaking the rules can restrict your access to RaceMeUp.