Mod Request Etiquette How to Ask So People Actually Help

Mod requests are how communities signal demand—but most threads die because nobody can understand what is being asked, how it would be used, or whether it is even legal to share. Good etiquette is not politeness theater; it is information design that gets you closer to a real outcome.

Whether you post on AC Supply request features or external forums, the same rules apply.

One clear title beats a novel in the body

Your title should name the object and the scope: car year and trim, track layout, or skin series. “Someone make this pls” is unsearchable and unmotivating. “Request: 20XX Model ABC Cup car (reference photos + BoP target)” invites the right readers.

Bring references creators can use

Link photo albums, onboard videos, technical sheets, or official livery PDFs when available. If licensing forbids certain logos, say so up front—creators hate redoing work because brands are sensitive.

Realistic scope wins

A full scratch-built car with interior animation, multiple liveries, and perfect physics is not a weekend favor. If you want something huge, consider commissioning with budget and timeline—not a vague public wish. Smaller asks (a livery pack for an existing model, a layout tweak for a track) get traction more often.

Respect time and credit

Creators owe you nothing. Demanding tone, repeated pings, or reposting the same thread across ten servers burns goodwill. If someone delivers a beta, test it and report bugs with reproducible steps instead of emotional venting.

Licensing and ripped content

Do not ask for ripped models from other games. Communities increasingly enforce rules against theft, and hosts may remove listings. If you want a lookalike, ask for inspired-by work that respects IP.

Tie requests to how you play

Say whether you need the mod for offline hotlap, public lobbies, or league racing with checksums. Those constraints change packaging and versioning. Mention CSP expectations if rain or advanced shaders matter to your group.

Close the loop when someone helps

If a creator ships a beta, test on schedule and report back with short clips or screenshots when visuals are wrong. Silence after receiving files trains contributors to ignore the next thread with your name on it. Public thank-you posts also help future searchers find working downloads.

Search before you post

Spend two minutes searching the same keywords you would put in a title. Duplicate requests fragment discussion and annoy moderators. If an old thread stalled, reply with new references instead of opening a third duplicate—continuity keeps context attached.

FAQ

Should I @ famous creators?
Only if they openly take requests. Otherwise it is spam.

What if nobody replies?
Your ask may be too broad, too legally gray, or simply low priority—refine and wait.

Can I bump threads?
Sparingly, with new information—not “bump” every day.

Requests are collaboration proposals. Treat them like mini design briefs—specific, sourced, scoped—and you will stand out in a sea of low-effort asks.

That mindset also helps you: writing a sharp request forces you to decide what you truly need before you waste anyone else’s weekend.