Deadlock Config & Settings Guide – Profiles, Keybinds & Visuals
Organize your Deadlock: Predator configuration with clearly named profiles, readable visuals and separate activation keys.
This ESHub guide explains how to review, save and troubleshoot settings. For the complete feature overview, visit our Deadlock Cheats guide.
What Does a Deadlock Config Store?
A configuration stores the settings supported by the current menu. These can include enabled features, activation keys, aim controls, visual colors and display layout. A saved profile lets you revisit those choices without rebuilding the setup from memory.
Check which settings actually belong to the profile and which are global. Loading a profile should be followed by a review of the active values, especially after an update or import.
A Clear Workflow for Saving Profiles
- Review the starting state. Note the active profile, enabled features and important bindings before changing anything.
- Use a descriptive name. A name such as “Visual Layout – October” is easier to identify than “Config 2.”
- Change one settings group at a time. Keep visual layout changes separate from aim or movement changes so their effects are easier to identify.
- Save with the available controls. Check whether the current menu uses manual saving, autosave or both.
- Reload and verify. Confirm that the intended values remain after reloading the profile.
- Keep a backup where export is supported. Label it with the profile name and relevant build or date.
An exported config should be treated as settings data. Import through the menu’s supported controls; a config file is not something to run as a program.
Settings Groups to Review
🎯 Aim & Recoil
Review the aim key, FOV, smoothing, distance and hitbox selection individually. Recoil settings have a separate role. See Aimbot and No Recoil & RCS.
⚡ Trigger Controls
Check the active trigger mode, hotkey and available delay or distance controls. Keep trigger activation distinct from the aim key. The Triggerbot guide explains Standard and Magnet modes.
👁️ Player Visuals
Review boxes, skeletons, health bars, names and distance labels as separate layers. Avoid placing several labels over the same area. See ESP & Wallhack.
🗺️ Radar & World Markers
Check radar size, position and scale independently. Review world categories and filters separately from player labels. See Radar and World ESP.
🛡️ Parry & Ability Displays
Keep parry activation and timing controls separate from cooldown displays. Review their settings in Auto Parry and Ability & Ultimate ESP.
⌨️ Movement Activation
Check hold requirements and item conditions before assuming a feature is broken. See Auto Dash Jump and Movement Features.
Keybinds: Hold, Toggle & Shared Inputs
Hold activation depends on keeping the assigned input pressed. Toggle activation switches a state. Check the mode for each feature instead of assuming every binding behaves the same way.
Review the menu key alongside feature keys and in-game inputs. If two features share a binding, pressing it may affect both. An imported profile can change these assignments, so review its bindings before relying on your previous setup.
Readable ESP & Radar Layouts
Choose colors that remain distinguishable against the game background. Where visible and occluded colors are available, give each a consistent meaning. Health bars, skeletons and text labels should remain readable without covering one another.
For radar, panel size and map scale are different controls. Position the panel so it does not cover important game UI. Recheck the layout after changing resolution or aspect ratio; a profile made for another display may need adjustment.
Import, Export & Update Troubleshooting
Where JSON import or export is available, use the supported format and keep a backup before replacing an existing profile. Cloud sharing and local export are different capabilities; check which controls the current Predator menu provides.
- Settings appear unchanged: confirm the intended profile was loaded rather than merely selected.
- Changes disappear: check manual save and autosave behavior.
- A feature no longer activates: review its enabled state, binding and activation conditions.
- An import omits settings: check whether the source profile matches the current build and supported fields.
- The menu is unavailable: use the Menu Not Opening guide.
For a support request, include the affected setting, active profile and any visible error. Check current product status before treating an update-related compatibility problem as a configuration error.
Explore ESHub’s Deadlock: Predator
View the current Predator listing for available features, system requirements and subscription choices. Feature names and menu options should be checked against the current build.
Compatibility & Account Risk
Using unauthorized multiplayer software carries account risk and a saved profile does not guarantee protection from bans. Safe Mode is a feature control, not a promise of account safety. A temporary spoofer has separate requirements and does not determine which configuration controls are available.