The Rocket League recordings

I have described a collection of 120 Rocket League recordings. On November 1, 2026, nine videos were visible on the Schweickart Media channel; the larger collection is not yet reconciled to public video links. That presents an opportunity, but also a problem: a folder full of videos is not the same thing as a useful channel.

YouTube carries the playable footage; Schweickart Media gives it some context. That makes each platform do a job it is suited for. Someone who wants to watch a match can do that on YouTube. Someone who wants to understand the story—why we played, how a setup worked, or how much time we have put into a game—can find that on the website.

Watch the published recordings

Direct links checked on November 1, 2026. Titles and duration labels are retained from YouTube.

All Schweickart Media videos →

Not every capture needs its own upload

A good Rocket League clip might show a surprising save, a goal worth remembering, a mistake worth learning from or a comparison between attempts at a skill. A longer gaming session might be worth publishing because it tells a complete story. Another capture might only contain a short moment worth cutting out.

There is no reason to force every file into the same format. We can have full sessions, edited highlights and short clips, all tied back to the same original capture. A gameplay segment showing a console or cloud gaming test may belong with a technology story rather than a game review.

The first step is recording the source honestly: title, game, platform, capture date, recording duration, who appears or can be heard, and the status of review. A file's upload date is not necessarily the day we played it.

An archive should help us discover stories

Over time, the captures can answer interesting questions: which games we return to most; whether our play style changes; whether a certain device works during travel; and which games are more fun to watch than to play. The purchase history adds another dimension, but an invoice alone cannot prove a session happened.

For Rocket League in particular, the connection between verified rank, gameplay footage and hours played could produce useful progress stories. The same framework works for sports games, simulations, exploration and multiplayer games—each with its own reasons to pay attention.

Publishing without giving away family information

A capture can contain more information than the game itself: real names, voices, notifications, account IDs, live chat, messages from friends, location details or copyrighted music. These need review before a video goes public. Children should not be identified, profiled or recruited for sponsorships by default. Any family participation needs explicit, separate review.

The video should also stand on its own. A title and description should tell viewers exactly which game they are watching and what is interesting about this particular clip, not promise a spectacular event we have not verified in the recording.

The goal now is to make the collection easier to use: an index of full matches and selected clips, linked to the original videos, with enough context to make each one worth watching.

Part of Gaming and Entertainment on Schweickart Media. Data and player details are included only where they can be supported by saved records.

Give each selected recording a reason to be watched

The website description can do a different job from the video title. It can establish the question behind the selection: a particular match decision, an equipment experiment or a moment that changes the rhythm of a session. A viewer should understand that reason before committing to a long capture.

For an edited highlight, the connection to the longer recording also matters. The surrounding play may explain what happened, while the shorter version makes the moment easy to find. Keeping those versions associated would let a story grow without confusing an edit with a separate event. This approach can be used beyond Rocket League as other game captures enter the collection. The reported upload count establishes the scale of the organizing task; it does not establish that each recording has been individually reviewed.