Make Your Voice Heard
Palia’s developers actively listen to the community. Whether you have a bug report, a feature request, or general feedback, this guide shows you exactly how to submit it through the official channels – and how to write feedback that gets noticed and acted upon.
🎮 In‑Game Feedback Tool (Most Direct)
- How to access: Press Esc (PC) or + (Switch) → select “Feedback” or “Submit a Bug”.
- What you can submit: Bug reports, feature suggestions, general feedback, or compliments.
- Automatic metadata: The tool automatically includes your game version, platform, and rough location, which helps developers reproduce issues.
- Attachments: You can attach up to 3 screenshots or short videos (max 30 seconds) to illustrate the problem.
💡 This is the best channel for bugs because the tool collects technical data automatically. For complex issues, include a step‑by‑step description.
💬 Official Discord (Community & Direct Channels)
- Invite link: discord.gg/palia
- Channels for feedback:
#feedback-and-suggestions– post feature ideas and general feedback. Upvote others’ ideas.#bug-reports– report in‑game bugs. Follow the template (platform, description, reproduction steps).#help– for player‑to‑player support (not direct developer feedback).
- Developer presence: S6 staff read these channels daily and occasionally reply. They also use upvote count to prioritize features.
🌐 Palia Support Website
- URL: support.palia.com
- Best for: Account issues, purchase problems, technical support, and detailed bug reports that need file attachments.
- Process: Submit a ticket → choose category → fill in form (includes fields for device specs, screenshot uploads, and logs).
- Response time: Usually 24–72 hours for account/billing issues; longer for feature suggestions (which are forwarded to design team).
🐦 Social Media (X @PlayPalia)
While you can tag @PlayPalia with feedback, this is not the most effective channel for detailed reports. Best used for sharing appreciation, short suggestions, or reporting widespread issues. The team does monitor but directs detailed reports to other channels.
✍️ Writing Effective Feedback – Best Practices
For bug reports:
- Title: Short and specific (e.g., “Fishing rod animation stuck after casting in Bahari Lake”).
- Description: What happened, where, and when (in‑game time if relevant).
- Reproduction steps: Numbered list of exact steps to make the bug happen.
- Expected result: What should have happened.
- Actual result: What happened instead.
- Screenshot / video: A picture is worth a thousand words. Use in‑game screenshot (F12 on PC, Capture button on Switch).
- Platform & specs: PC or Switch, graphics settings, and any unusual hardware.
For feature suggestions:
- Explain the “why” – not just what you want, but how it improves the game (e.g., “More soil plots would allow players to experiment with crop rotations without reducing other farm space”).
- Be constructive – avoid “the game is broken”. Instead, say “I think the mining XP rate feels low compared to fishing, could it be rebalanced?”
- Check if it already exists – use Discord search to see if your idea has been suggested before. Upvote existing instead of creating duplicate.
- One suggestion per post – makes it easier to vote and track.
⏱️ What Happens to Your Feedback?
- Bugs: Triage team verifies and assigns priority. Critical bugs (crashes, lost progress) are addressed within days. Minor bugs may be queued for later patches.
- Feature suggestions: Monthly review by design team. Popular ideas on Discord are logged in a public Trello board (viewable).
- You may not get a personal reply – but every submission is read. If a bug is fixed, it will appear in patch notes.
- Duplicate reports: They help gauge frequency – don’t worry if you post the same bug as someone else.
✅ DOs and DON'Ts of Submitting Feedback
DO:
- Be specific and polite
- Include screenshots/videos
- Search before posting duplicates
- Use the in‑game tool for bugs
- Upvote others’ ideas you like
DON'T:
- Post the same feedback in multiple channels
- Demand immediate fixes
- Use aggressive language
- Submit feedback about gameplay mechanics without explaining why it’s problematic
- Send private messages to developers (they won’t reply)