Debt Hunt uses Roblox platform controls plus game-specific actions for its contract. Standard movement can be expected from Roblox, but the developer has not published a complete current keycard for interacting, using tools, taking photos, dropping items, or helping another player. Treat the prompt shown by your server as the final authority.
Set controls during daylight. A button you have not tested becomes a much larger problem when sunset begins and the monster is active.
Start with Roblox platform basics
On keyboard and mouse, Roblox normally uses WASD for movement, the mouse for camera look, and Space for jump. Touch devices use an on-screen movement control and context buttons. Controllers use the mapping exposed by Roblox and the experience. These are platform baselines, not a promise that every Debt Hunt interaction uses one universal key.
Open Roblox Settings and adjust camera sensitivity, movement mode, graphics, and volume before a serious run. Keep the camera fast enough to check the return lane without losing control of a narrow interaction prompt. Lower graphics if visual effects or shadows make route anchors harder to read.
Do not copy an exact E, F, G, trigger, or face-button mapping from an old video without checking the on-screen prompt. Alpha updates can change bindings or context behavior.
Identify the actions your run needs
The official badge list proves several action families: take photos with a camera, mine Mineral Ores, break Wooden Planks, dig Treasures, open Supply Boxes, and pick up a Gem. The official description also requires earning money, paying debt, moving through a procedural space, and surviving the sunset hunt.
Build your personal control card from the live UI:
- Move, look, jump, and run or sprint if available.
- Interact, pick up, open, sell, upload, bank, or confirm.
- Equip, use, aim, or activate the current camera and tools.
- Drop, store, swap, or clear the held item.
- Open the debt, inventory, shop, or objective interface.
- Communicate, ping, carry, revive, or assist only when the current build displays those actions.
Write the actual prompt beside each action. Leave an unsupported action blank rather than borrowing a key from the original Minecraft concept.
Run a five-minute daylight drill
First, walk from the starting area to one landmark and return while turning the camera. Next, approach a nearby container or pickup and follow its prompt. Confirm where the result appears in inventory or the contract UI.
Equip the camera if the current run provides it. Take one test photo and inspect the feedback. Then equip one available tool and check whether the target displays a distinct interaction. Do not consume rare resources simply to test a button.
Finally, open and close every important menu, return to normal movement, drop or store a harmless item if supported, and repeat the return route without looking at Settings. If playing with a friend, test any assist or carry prompt in a safe place before relying on it during sunset.
Improve touch controls
Keep the movement area clear and make the most important context button easy to reach without releasing the camera. Avoid stacking jump, interact, and tool use so closely that one action triggers another. Test the layout while moving around an object, because a stationary menu test does not reveal whether your thumbs can steer and interact together.
Increase button size where Roblox or the experience allows it. If the camera jumps too far during a small drag, lower sensitivity. If an interaction prompt is hidden behind your hand, rotate the device layout or adjust the interface scale when supported.
Touch players benefit from shorter routes. Extra input time at a container or tool target belongs in the sunset budget.
Improve controller controls
Connect the controller before joining, confirm that Roblox recognizes it, and watch whether prompts switch from keyboard to controller labels. Disconnect duplicate input devices if prompts flicker. Test movement, camera, jump, context interaction, tool use, inventory selection, and menu back/cancel in that order.
Use dead-zone and sensitivity settings when available, but change one value at a time. A high camera speed can help check behind you; it can also make photos or small prompts difficult. Choose a setting that supports both route awareness and precise interaction.
If a Debt Hunt-specific action lacks a controller prompt, do not assume a hidden combination. Rejoin once, test another supported input, and report the missing prompt through official channels.
Fix common control problems
A prompt appears but the action fails: empty or change the held item, face the target, move within range, and hold or tap exactly as the UI indicates.
The game keeps opening a menu: use the cancel/back action, click or tap outside the panel if supported, and verify that focus has returned to the character.
Keyboard and controller prompts alternate: disconnect unused devices and avoid touching the second input while testing.
Touch buttons cover important UI: adjust scale or layout, then retest with the camera moving.
A guide’s key does nothing: trust the current prompt. The guide may show another server build, platform, or the older non-Roblox concept.
Controls FAQ
What is the Debt Hunt interact key?
Use the prompt shown beside the target in your current server. The developer has not published one complete cross-platform keycard.
Can I rebind controls?
Roblox and individual experiences expose different settings. Check Roblox Settings and any in-game controls panel; do not assume every action can be remapped.
How do I use the camera?
Equip the in-game tool when available, follow its current capture prompt, take one daylight test, and inspect the result or capacity feedback. The Camera Guide covers the full workflow.
Why test on Easy?
Easy is an officially named difficulty and is the sensible place to learn prompts before adding more pressure. Exact difficulty modifiers remain unverified.
Sources checked
- Roblox support for computer controls, consulted for platform context.
- Official Debt Hunt badges, checked September 2, 2026.
- Current community controls guide, treated as a non-official prompt checklist.