Lurking GiantsLurking Giants is developed by a small team (ULTRA works, owned by Redie\J), which means community bug reports are essential for maintaining game quality. Unlike large studios with dedicated QA teams, ULTRA works relies on players to identify and report bugs, exploits, and rule-breaking behavior. This guide explains how to effectively report bugs through the official Discord, what information to include, and how to report exploiters who harm the game experience.
Why Bug Reports Matter
Every bug you report helps ULTRA works improve Lurking Giants for all players. Common bugs in Roblox games include:
| Bug Category | Examples | Impact |
|---|---|---|
| Gameplay bugs | Giant abilities not working correctly, survivors stuck in walls | Directly affects round outcomes |
| Map bugs | Characters falling through floors, invisible walls, unreachable areas | Creates unfair advantages or disadvantages |
| UI bugs | Shop not loading, code redemption failing, game pass not activating | Prevents players from using features |
| Economy bugs | Incorrect coin amounts, purchases not registering | Affects progression |
| Exploit-related | Speed hacking, teleporting, flying, god mode | Ruins gameplay for other players |
The VERITY rework will likely introduce new bugs as new systems (Giants, perks, maps) are added. Your reports during and after the rework launch will be especially valuable.
How to Report Bugs Through Discord
The official ULTRA works Discord at https://discord.gg/ultraworks is the primary bug reporting channel. Follow these steps to submit an effective report:
Step 1: Verify the Bug Is Real
Before reporting, confirm the bug is reproducible:
- Try to recreate it: Can you make the bug happen again intentionally?
- Check if it is already known: Search the #bug-reports channel for existing reports about the same issue
- Test in different conditions: Does the bug only happen on Forest? Only when playing as Guilt? Only at specific game times?
Step 2: Document the Bug
Gather the following information before writing your report:
| Information | Why It Matters | How to Collect |
|---|---|---|
| Bug description | What exactly goes wrong | Write a clear, specific description |
| Steps to reproduce | Developer needs to recreate the bug to fix it | List exact steps in order |
| Expected behavior | What should happen instead | Describe the intended game behavior |
| Actual behavior | What actually happens | Describe the bugged behavior |
| Platform | Different platforms may have different bugs | PC, mobile, Xbox, etc. |
| Frequency | How often the bug occurs | Every time, sometimes, rare |
| Screenshots/video | Visual evidence is the most compelling | Use Roblox screenshot (F12) or screen recording |
Step 3: Write the Report
Use this template for your Discord bug report:
**Bug Title**: [Short description, e.g., "Survivor stuck in Forest cave wall after pulse"]
**Platform**: [PC/Mobile/Xbox/Quest]
**Frequency**: [Every time / Sometimes / Rare]
**Steps to Reproduce**:
1. [First step]
2. [Second step]
3. [Third step]
**Expected Behavior**: [What should happen]
**Actual Behavior**: [What actually happens]
**Evidence**: [Attach screenshot or video link]
**Additional Notes**: [Any other context that might help]
Step 4: Post in the Correct Channel
Submit your report in the #bug-reports channel on the ULTRA works Discord. Do not post bug reports in #general or other channels, as they may be missed by the developer.
Reporting Exploiters
Exploiters use third-party software to gain unfair advantages in Lurking Giants. Common exploits include:
| Exploit Type | What It Looks Like | How to Confirm |
|---|---|---|
| Speed hacking | Player moves significantly faster than normal sprint | Watch for 2x+ normal speed consistently |
| Teleporting | Player disappears and reappears at distant locations | Observe sudden position changes |
| Flying | Player moves through the air | Clear visual — player above ground level |
| God mode | Survivor cannot be eliminated by Giant | Giant attacks connect but survivor survives |
| Wall hacking | Giant or survivor can see through walls | Difficult to confirm — watch for impossible awareness |
How to Report an Exploiter
- Record evidence: Use screen recording to capture the exploiter's behavior. Video evidence is required — text reports without evidence are difficult to act on.
- Note the username: Record the exact Roblox display name of the exploiter.
- Note the time and server: Record approximately when the exploit occurred.
- Report in #exploit-reports: Post on the ULTRA works Discord with the video evidence and exploiter information.
What NOT to Do
- Do not confront the exploiter in-game: This may provoke them and does not solve the problem
- Do not try to exploit back: Using exploits yourself, even to counter another exploiter, is a bannable offense
- Do not share exploit software: Posting or linking to exploit tools in the Discord is a bannable offense
- Do not name and shame publicly: Report through the proper channel, not in #general chat
Feature Suggestions
If you have ideas for improving Lurking Giants (not bugs, but features), the Discord also has a channel for suggestions:
Effective Suggestion Format
**Suggestion Title**: [Short description]
**Problem**: [What current gameplay issue does this address?]
**Proposed Solution**: [How would your suggestion fix the problem?]
**Benefits**: [Why would this improve the game for players?]
**Potential Concerns**: [What downsides or implementation challenges might exist?]
Examples of Good Suggestions
| Suggestion | Problem Addressed | Quality |
|---|---|---|
| "Add a compass HUD element" | Survivors have no orientation reference | Good — addresses a specific UI gap |
| "Let survivors choose their class before rounds" | No variety in survivor gameplay | Good — aligns with VERITY rework direction |
| "Make Guilt free" | 7,000 coins is too expensive | Poor — ignores economic balance |
| "Add a third map" | Only 2 maps leads to repetition | Good — community-supported request |
What Makes a Suggestion Valuable
- It solves a real problem: Not "it would be cool if" but "this specific issue could be fixed by"
- It considers game balance: Suggestions that would make one role overpowered are not helpful
- It is feasible within Roblox: Some features are technically impossible or extremely difficult in the Roblox engine
- It respects developer scope: ULTRA works is a small team — massive feature requests are unlikely to be implemented
Common Lurking Giants Bugs
Understanding which bugs are commonly reported helps you identify issues and write better reports:
Known Bug Categories
| Bug Category | Description | Frequency | Severity |
|---|---|---|---|
| Survivor stuck in geometry | Player gets trapped inside walls, floors, or objects | Common | High — prevents gameplay |
| Giant ability malfunction | Haunt (G) or Attack (Q) fails to activate or misses | Occasional | High — affects round outcomes |
| Code redemption failure | Entering a valid code produces no reward | Rare | Medium — economic impact |
| Map rendering issues | Invisible walls, missing textures, broken geometry | Occasional | Medium — gameplay disruption |
| Role assignment errors | No Giant selected, or two Giants in one round | Rare | High — breaks core game loop |
| Game pass not activating | Purchased pass does not provide advertised benefit | Rare | Medium — financial impact |
| Audio bugs | Missing audio cues, looping sounds, delayed effects | Occasional | Medium — reduces awareness |
When NOT to Report a Bug
Some reported "bugs" are actually intended gameplay features or limitations:
| "Bug" | Actually | Why |
|---|---|---|
| "Guilt can see me through walls" | Intended feature | Guilt's Haunt penetrates building walls by design |
| "I got highlighted even though I was in a cave" | Intended feature | Visibility pulse highlights all survivors regardless of cover |
| "E key doesn't work sometimes" | Likely user error | Sprint has a cooldown; check that you are not pressing Shift instead |
| "The Giant is too fast" | Intended balance | Giants are faster than survivors to create chase pressure |
| "My vote didn't count" | Likely user error | You must vote during the intermission period before the round starts |
The Bug Report Lifecycle
Understanding what happens after you submit a bug report helps manage expectations:
Typical Timeline
| Stage | What Happens | Duration |
|---|---|---|
| Submission | Bug report posted in #bug-reports | Immediate |
| Community review | Other players confirm or refute the bug | 0-48 hours |
| Developer review | ULTRA works reviews and prioritizes the report | 1-14 days (varies) |
| Investigation | Developer attempts to reproduce the bug | 1-30 days (varies) |
| Fix implementation | Bug is fixed in a game update | Days to weeks |
| Verification | Community confirms the fix works | 1-7 days post-update |
Why Some Bugs Take Longer to Fix
| Factor | Impact on Fix Time |
|---|---|
| Reproducibility | Bugs that are hard to reproduce take longer to diagnose |
| Severity | Game-breaking bugs are prioritized over cosmetic issues |
| Development resources | ULTRA works is a small team — limited capacity for bug fixes |
| VERITY rework priority | Active rework development may delay bug fixes for the current version |
| Platform-specific | Bugs that only occur on one platform require specific testing |
Building a Bug-Free Community Culture
The community plays a crucial role in maintaining game quality. Beyond reporting bugs, you can help by:
Encouraging Responsible Reporting
- Help new players report bugs: When someone mentions a bug in #general, direct them to #bug-reports with the template
- Upvote confirmed bugs: If another player confirms a bug you reported, acknowledge their confirmation
- Test reported bugs: If someone reports a bug you have not experienced, try to reproduce it and share your results
- Thank the developer: When a bug is fixed, post a brief thank you in #general — positive feedback motivates continued development
Reporting During the VERITY Rework Launch
The rework launch is when bug reports are most critical and most frequent:
| Post-Rework Period | What to Expect | How to Help |
|---|---|---|
| Day 1-3 | Many new bugs as new systems are tested | Report bugs with detailed reproduction steps |
| Week 1 | Rapid patch cycle as critical bugs are fixed | Re-test fixed bugs and confirm or report remaining issues |
| Week 2-4 | Patch cadence slows as remaining bugs are edge cases | Continue reporting even minor issues |
| Month 1+ | Stability improves, new content bugs become primary focus | Report any new Giant, perk, or map bugs |
Frequently Asked Questions
Where do I report bugs? In the #bug-reports channel on the official ULTRA works Discord at https://discord.gg/ultraworks. Do not report bugs in other channels or through private messages.
Will the developer respond to my bug report? Not guaranteed. The developer monitors the bug reports channel but may not respond to every report. If your report is clear, reproducible, and includes evidence, it is more likely to be investigated.
How do I report an exploiter without video evidence? Video evidence is strongly preferred. Without it, you can still report the exploiter in #exploit-reports with their username and a description of what you observed, but the developer may not be able to take action without proof.
Can I report bugs on the Roblox game page? The Roblox game page does not have a dedicated bug report feature. The Discord is the most effective reporting channel. You can also report game-breaking bugs through the Roblox "Report Abuse" feature in-game, but this goes to Roblox moderation, not the developer.
What if I find a bug that gives me an advantage? Report it immediately. Using a bug to your advantage (even if you did not create it) is considered exploiting and can result in a ban. Report the bug in #bug-reports and stop using the advantage until it is fixed.