Penguin Colony Bug Reporting: Send a Useful Report

Where to Report a Penguin Colony Bug

Penguin Colony bug reporting starts with the dedicated Steam bug thread or an email to support@fellowtraveller.games. A clear description, your build number, and the right save files give the team something concrete to investigate when a crash or broken scene interrupts your exploration. For Penguin Colony bug reporting after a crash, zip your save folder before relaunching whenever possible.

The full game launched on October 16, 2026, and has its own bug reporting thread. The demo has a separate thread, so choose the destination that matches the version you were playing.

What you were playing or need to send	Where to report it	What to include
Full game	Penguin Colony - Bug Reporting Thread on Steam	Build number, description, screenshots or video
Demo	Penguin Colony DEMO - Bug Reporting Thread on Steam	Build number, actual behavior, expected behavior, supporting images or video
Save files for investigation	support@fellowtraveller.games	Description, build number, and a zipped copy of the save folder

Open Penguin Colony’s Steam discussions and look for the matching thread. Keep your post focused on the bug; broader feedback belongs in a separate discussion.

Use email when sending the requested save archive. You can also mention that you emailed supporting files when adding details to your Steam post. Keep the description consistent across both messages so the same incident is easy to recognize.

Put the symptom in your subject or opening line. “Act 2 crash near the Outskirts” gives the team more to work with than “Game broken.” If the issue prevents progress, say that immediately.

Official page: Penguin Colony (store.steampowered.com)

What to Include in Your Bug Report

Start with the build number displayed at the bottom-left corner of the main menu. Copy it exactly, and identify whether you were playing the demo or full game.

Image: Steam / ORIGAME DIGITAL

That distinction matters. Demo reports include versions 0.21 and 0.22, while the launch discussion includes v1.5 issues. Combining those experiences without their version numbers makes the problem harder to pin down.

The next part of Penguin Colony bug reporting is describing the sequence clearly: where you were, what you did, and what happened afterward.

Detail	What to write
Build number	The version shown at the bottom-left of the main menu
Game edition	Demo or full game
Location	Act, chapter, area name, or a recognizable nearby landmark
Actual behavior	The crash, missing prompt, frozen scene, visual problem, or other symptom
Expected behavior	What you expected the action or scene to do
Reproduction steps	The actions immediately before the problem
Frequency	Whether it happened once or returned during another attempt
Documentation	Screenshots or a video capturing the issue
Relevant setup	Controller type, PC specifications, or selected language when relevant

Describe visible behavior precisely. Did the application close completely? Did the picture freeze while audio continued? Could you still open a menu? Those are different symptoms, even when each stops you from playing.

For controller problems, name the device and say whether it was connected by cable. Include whether the buttons worked despite incorrect prompts. For a localization problem, give the selected language, the affected text, and the screen or scene where it appears.

Record the steps you remember without filling gaps. If you cannot reproduce the issue, say how it happened during that session. A useful report does not require a perfectly repeatable bug.

A compact format keeps everything readable:

• Build and edition:
• Area or scene:
• What I did:
• What happened:
• What I expected:
• Does it happen again?:
• Screenshots, video, or emailed save archive:

Keep separate symptoms distinct. A controller prompt problem and an unrelated crash should each have their own description, even if you encountered both during the same session.

Find and Send Your Save Folder

For Windows, the Penguin Colony save folder is:

Image: Steam / ORIGAME DIGITAL

Platform	Save folder
Windows	%USERPROFILE%/AppData/LocalLow/ORIGAME DIGITAL/Penguin Colony

Open File Explorer and paste that path into the address bar. %USERPROFILE% points to your Windows user folder, so you do not need to replace it with your account name manually.

For Penguin Colony bug reporting by email, send a zipped copy of the entire folder alongside the build number and your explanation. The support request is for the folder, rather than an individually selected save file.

Follow this sequence:

1. After a crash, leave the game closed while you collect the folder.
2. Open the save location above.
3. Create a ZIP archive containing a copy of the Penguin Colony folder.
4. Email the archive to support@fellowtraveller.games.
5. Include the location, actions before the crash, and whether it has happened repeatedly.

The timing matters: support specifically requests the archive immediately after a crash, before another launch, when possible. If you already restarted, send the folder anyway and mention that you relaunched.

Leave the original folder in place while making the archive. The email attachment should be a copy; moving your working folder is unnecessary for the report.

Penguin Colony saves automatically when various actions occur. If a crash sends you backward, describe both where the crash happened and where you resumed afterward. That gives the team a clearer picture of the interruption and its effect on your progress.

If the game cannot reach the main menu, explain that you could not read the build number. Send the description and relevant files you can collect without guessing the version.

Recognize the Launch Issues Before Troubleshooting

Penguin Colony bug reporting is more useful when you identify the exact symptom instead of grouping every problem under “controls” or “graphics.”

Image: Steam / ORIGAME DIGITAL

At launch, the team identified several issues it was investigating or adjusting. Use these descriptions to make your own report specific.

Issue identified at launch	What it looks like	Relevant action or detail
Overlapping control layouts	Controller and keyboard layouts appear together in the pause menu	Describe the connected input device and what happened before opening the menu
Localization problems	Problems with translated text	Include the language, affected text, and screenshot
Resolution mismatch	The game does not automatically match the monitor’s resolution	Set the matching resolution manually in the game’s visual settings
Startup cursor visibility	The mouse cursor appears in startup menus when it should be hidden	Identify the menu where it remains visible

The resolution issue has a stated workaround: select your monitor’s resolution manually in the visual settings. If you report a display problem, include whether you have already made that adjustment and what still looks wrong.

Keep overlapping pause-menu layouts separate from incorrect tutorial prompts. In v1.5, an Xbox controller case involved keyboard instructions appearing during the opening red-light tutorial. The prompts switched to Xbox after the stare action was performed. That sequence gives the team a more specific symptom than a general complaint about controller support.

Penguin Colony supports English, Japanese, Simplified Chinese, Brazilian Portuguese, te reo Māori, and Arabic. For text problems, identify the selected language and capture the surrounding screen. Explain whether the issue concerns readability, overlapping text, or wording.

Do not carry old demo problems into a full-game report automatically. If you encounter a similar symptom in the released game, document the build you are actually running and the actions that triggered it there.

Document Crashes, Stuck Scenes, and Progress Blockers

For Penguin Colony bug reporting involving a progression blocker, lead with the point where you can no longer continue. Then explain the last action that worked.

A crash in an area, a stalled cutscene, and a character passing through scenery need different descriptions. Give each problem its own sequence.

Crashes during exploration

The v1.5 discussion includes crashes in Act 2 near the area identified as the Outskirts. Support asked whether the crash occurred at the same exact location each time and requested the save folder.

Answer that location question directly in your own report. Describe the route, nearby landmark, and action immediately before the crash. If another attempt ends elsewhere, preserve that distinction.

A separate chapter 5 crash case involved an external GPU enclosure containing an RTX4070. Include an eGPU setup if you use one, along with your other PC details. That hardware detail belongs in the report; it does not by itself identify the cause.

A cutscene that stops advancing

A v1.5 “Apotheosis” case stopped partway through the cutscene. Skipping afterward left the character passing through scenery, while reloading from the main menu restored play in that case.

If the same sequence happens to you, document both stages: the initial stall and the behavior after skipping. Note the last line or scene event before the interruption, and mark story details as spoilers in a public post.

After recording the problem, try returning to the main menu and reloading. Include whether it restored progress in your report.

Persistent interface elements and map boundaries

A v1.5 stamina-circle case stopped fading while controlling a particular penguin; switching penguins restored the fade behavior in that case. If you encounter it, record which penguin you controlled and whether switching changes the display.

For an out-of-bounds issue, capture the route that took you outside the playable space. The v1.5 discussion includes an Act 3 boundary escape, making the approach and terrain useful details to preserve.

Finish your Penguin Colony bug reporting follow-up with any recovery steps you tried and their results. Keep the original symptom visible, then add whether reloading, switching penguins, or another action changed it.

FAQ

Where do I start with Penguin Colony bug reporting?

Use the full-game bug reporting thread in Penguin Colony’s Steam discussions, or email support@fellowtraveller.games. Use the separate demo thread for demo issues. Include your build number, a clear description, and screenshots or video when available.

Where is the Penguin Colony build number?

Look at the bottom-left corner of the main menu. Copy the number exactly and specify whether the issue happened in the demo or full game.

Where are Penguin Colony save files on Windows?

They are in %USERPROFILE%/AppData/LocalLow/ORIGAME DIGITAL/Penguin Colony. For an emailed report, attach a zipped copy of the folder. After a crash, collect it before relaunching whenever possible.

How do I fix a resolution that does not match my monitor?

Open the game’s visual settings and manually select your monitor’s resolution. Automatic matching was an identified launch issue. If the display problem continues, describe what remains wrong and include the selected resolution in your report.