Help

What this site is

This is a tracker for the Game Compression Requests thread. The bot regularly checks the thread for new posts and keeps a live queue here so compressors can claim work without stepping on each other.

• Public queue (/queue) shows what's waiting, in progress, or recently finished.
• Request Queue (/requests) is where logged-in compressors claim and complete work.
• My Claims (/requests/my-claims) lists everything currently assigned to you.

What becomes a queue item

The bot tries to decide whether a post is a request or a delivery. Quoted content is always ignored — only the author's own text is parsed.

Request keywords (queues the item)

A post with a game thread link and any of the following phrases will be added to the queue:

• please compress / pls compress / plz compress
• compress please / compress pls / compress plz
• compress request / requesting compress
• need compressed / would like compressed
• can you compress / any chance compress

Creates a queued item (or duplicate if it matches something already active or finished).

Delivery / completion keywords (marks done)

Posts that look like a compression delivery are not added as new work. Common patterns include:

• COMPRESSED: Win/Linux/Mac with download hosts (PIXELDRAIN, WORKUPLOAD, etc.)
• Compressed post is located here
• Done : or Done ✅ with a game title or thread link
• Completed / Completed ✅ with a game title or thread link
• Compression done / Compression completed
• Compressed header followed by a list of game titles

Note: Even if someone has a "Compressor" badge, they can still post a request — those should still enter the queue.

Admins can add extra request or fulfillment phrases in Bot Settings → Keyword Overrides. Custom phrases supplement the built-in patterns; one phrase per line.

Auto-complete when someone else finishes it

Sometimes a request is still queued or even claimed, but a compressor posts a delivery in the thread anyway.

When the bot detects a delivery post, it will automatically mark matching active queue items as done. The request will show an event pointing to the forum post that triggered it.

Duplicate detection

• Already queued — the same game/version is already waiting or being worked on.
• Already fulfilled — the bot believes this version was already posted before.
• Needs review — the bot couldn't confidently tell what version is being requested.

Where the bot posts

The bot only replies in the compression request thread (the watch thread configured in Bot Settings). It never posts in game threads. When you mark a request complete, the bot notifies the requester there with a link to your compression post.

Before you start

You need a compressor account to use the request queue. If you don't have one yet, submit an access request from the Request access page. Once approved, log in at Compressor login.

Make sure your F95 profile URL is set on your account (admins can update this under Users). It appears in the bot's completion reply as a credit link.

Where to work

• Request Queue — browse all open requests, claim work, and open individual request pages.
• My Claims — everything you currently have claimed or in progress.
• Public queue — read-only overview; useful for checking what's busy before you claim.

Step-by-step workflow

1. Find a request
   Open the Request Queue and search or filter for the game and version you want to compress. Click a row to open the request detail page.
2. Claim it
   On the detail page, click Claim. This marks the item as claimed and assigns it to you so other compressors know it's taken. You can only hold a limited number of active claims at once (set by an admin on your account).
3. Start work
   When you're actually working on it, click Start work. Status changes to in progress. This step is optional but helps others see that work is underway, not just reserved.
4. Post your compression on the forum
   Open the game thread (linked on the request page) and post your compression using your own format — download links, sizes, notes, etc. The tracker does not post compressions for you in game threads.
5. Mark complete
   Back on the request detail page, use Mark complete. Paste the URL of your compression post in the game thread (must be a specific post link, e.g. …/threads/game-name.12345/post-67890). Confirm to finish.
6. Bot notifies the requester
   After you mark complete, the bot queues a reply in the compression request thread mentioning the original requester with a link to your post and credit for who completed it.

If you can't finish

Click Release claim on the request detail page to return it to the queue. Do this if you claimed by mistake, need to free a claim slot, or can't complete the work.

Claims also expire automatically after the configured number of hours if not completed (see Bot Settings → claim expiry).

Status reference

• queued — waiting for a compressor.
• claimed — someone reserved it but may not have started yet.
• in progress — actively being worked on.
• done — completed with a linked forum post.
• duplicate — same game/version already queued or fulfilled.
• rejected — not a valid request (reviewer/admin action).

What compressors can and can't do

• You can: claim, start work, release, and mark complete your own claims.
• Reviewers/admins can: reject requests, mark duplicates, and resolve edge cases from the queue.
• Trusted posters can: edit closed requests (update the post URL, notes, or reopen) after completion.

If something was marked complete with the wrong post URL, ask a trusted poster or admin to fix it on the request detail page under Edit closed request.

Tips

• Claim only what you plan to work on — expired or abandoned claims slow everyone down.
• Copy the post URL from your browser after posting in the game thread; thread-only links won't work for mark complete.
• Check Event history on a request if you're unsure what happened or who changed it.
• Use My Claims as your daily to-do list.