Rollout Inline A Personal Note From The Dev

On September 14, 2026, the day before Steam Early Access, solo developer Michel (MLMEDIA) posted a Steam news item titled “A Personal Note From The Dev.” The tone is not a feature dump. It is a one-person studio asking players to treat launch as the start of a conversation. Rollout Inline then entered Early Access on September 15, 2026. This page restates that note in plain language and turns it into practical guidance: how to report bugs without noise, what a solo-dev Early Access actually means, and which wiki pages save you from filing a “broken game” ticket that is really a pad or FPS problem.

For the day-one ship list, use Early Access Launch. For Discord and socials, use Official Links rather than random invite URLs. Parent index: Updates Hub.

What Michel actually said

Paraphrased from the official Steam post, without turning it into marketing copy:

• He is excited to share the project after about 1.5 years of intense work.
• Early Access means the game is still in development.
• You may encounter bugs, crashes, or things that do not work as they should. He hopes for smooth sailing, and he is honest that you never know.
• If you hit issues, do not panic. The official Discord has dedicated bug-report and feedback channels, opened at launch for people who support the project early.
• He asked for constructive criticism, feedback, and ideas, and said he would work around the clock to fix issues as soon as possible.
• The project is personal. He knows players have waited a long time for a modern aggressive inline game. This is only the beginning.
• If you have a great time, a positive Steam review and word of mouth help more than most players assume.

That is the whole letter. Everything below is player hygiene built on top of it—not extra promises Michel did not make.

What Early Access means on a solo project

A live-service team can absorb a chaotic launch week with shifts. A solo developer cannot. Michel built Rollout Inline himself. Features that shipped on September 15—three maps, dual-stick skating, challenges, progression, customization, replay editor, music/radio, difficulty options, Steam Deck Verified play—can still be tuned. A planned fuller exit around Q3/Q4 2027 can still move.

Expectations that stay honest:

• Patches may arrive as focused drops, not a weekly content calendar.
• One person reading Discord cannot reply to every thread in real time, even when they are working long hours.
• A crash on map three does not mean the studio abandoned the game overnight.
• “ASAP” in a solo-dev note means priority, not a service-level agreement.

If you needed a finished 1.0 skating anthology, wait. If you wanted to skate the launch trio and help shape the next year, you are the audience the note was written for.

Bug reporting hygiene (do this before you post)

Most “unplayable” reports on skating games are input or frame-time problems. Spend ten minutes on setup so Michel is not hunting ghosts:

1. Confirm the controller was connected or woken before launch. Keyboard and mouse are unsupported.
2. Confirm Steam Input is a simple gamepad layout, not a leftover community overlay from another skating title. Recovery: Controller Setup.
3. Confirm you are holding about 60 FPS. Dual-stick corrections feel late when frames hitch. Triage: System Requirements.
4. On Deck, confirm you did not treat the Verified badge as a max-settings trophy. Handheld notes live on Steam Deck.
5. Reproduce once. Note which of the three launch maps you were on, what you were trying to do (grind, jump, challenge pin), and whether it happens every time.
6. If the fail is mechanical rather than a crash, film it in the replay editor. A clip of a foot leaving a rail is worth more than “grinds feel weird.”

Then post. Prefer the official Discord bug channels once you have the invite from Official Links. Steam discussions on app 4464990 are a backup. Do not paste random discord.gg links you found in a comment section; invites get spoofed.

A useful report looks like: hardware, pad model, wired or wireless, Steam Input yes/no, FPS overlay reading, map (describe the park language—rails, vert, pool—without inventing names), steps, expected result, actual result, crash or not. A less useful report looks like a one-line insult.

How to give feedback Michel can use

The note asked for constructive criticism. That is not the same as silence, and it is not the same as a pile-on.

Helpful:

• “This rail on the long-rail park dumps me when both sticks sit slightly off-center at high speed. Replay attached.”
• “Challenge text is easy to miss on Deck at default UI scale.”
• “I would love a fourth park later; here is the feature language I am missing: more pools.”

Less helpful:

• Demanding multiplayer, keyboard support, or console SKUs that were not in the launch claim set.
• Review-bombing a crash before you verified the pad and FPS.
• Inventing patch dates and then being angry when they do not happen.

You can still leave a negative Steam review if the game is not for you. Be specific. “Solo Early Access with three maps and dual-stick feet is not what I wanted” is honest. “Scam” is not a bug report.

How this wiki helps during the same week

Use wiki pages as the first filter so Discord stays about real defects:

• Getting Started — first-hour plan so you are not filing tickets about challenges you have not learned to read.
• Controller Setup and System Requirements — the two pages that prevent false physics reports.
• Early Access Launch — what actually shipped, including single-player only and controller required.
• Updates Hub — where later patch pages will land.
• Official Links — Steam news, @rolloutinline socials, and how to find Discord from official bios instead of a hardcoded invite.

This wiki is unofficial. If Steam news and a wiki sentence disagree, Steam wins. When a patch changes feel, we update the matching guide rather than leaving stale drills online.

Reviews, word of mouth, and pressure

Michel asked players who have a great time to leave a positive review and tell people about the game. That request is normal for a solo Steam title in a tiny genre. It is not a requirement, and it is not a reason to hide bugs. Play first. If the dual-stick model clicks, a written Steam review with hardware notes helps the next buyer more than a one-line social post.

If you are miserable because you expected Tony Hawk scoring or a skateboard flick game, say that clearly instead of calling the build unfinished in a vacuum. Comparison context lives on vs Other Games.

A calm first-week checklist

1. Read this note once so bugs do not feel like a betrayal.
2. Set up the pad and FPS.
3. Skate a short free-ride using Getting Started.
4. When something breaks, isolate setup versus a true defect, then report it through official channels from Official Links.
5. Watch Updates and Steam news rather than rumor screenshots.

Early Access after a year and a half of solo work is a handoff, not a finish line. Do not panic. Report cleanly. Skate the parks that shipped. Let Michel keep building.