7D7DTD Signal7 Days to Die guides
Feedback
MOD Wiki / SMX

SMX

SMX UI guide for HUD readability, screen checks, file routes, and multiplayer rules.

SMX

SMX changes how 7 Days to Die is read and operated on screen. Test it as a UI package: inventory, crafting, map, trader, quest, vehicle, and scaling screens all matter.

UI / HUD V2.X Client-side Medium impact
Download

Images

Images are shown to help identify the MOD. Source previews link back to the page where they were recorded.

SMX image 1
SMX image from the recorded Nexus Mods page. Nexus Mods listing
SMX image 2
SMX entry mark, shown when no source screenshot is recorded yet. 7DTD Signal

Details

Use this page to judge what SMX changes, how to test it first, and whether it belongs in your save or server.

SMX changes how 7 Days to Die is read and operated on screen. Test it as a UI package: inventory, crafting, map, trader, quest, vehicle, and scaling screens all matter.

UI files often feel low-risk in solo play, but server rules, EAC policy, localization, and other HUD packages can still conflict.

Screens changed

SMX is mainly worth checking through inventory, backpack, and toolbelt screens, crafting, workstation, and recipe screens, map, quest, trader, and reward panels, and resolution, scaling, and language display. Do that in a copied save or test server before changing a main world.

Use Nexus SMX listing to confirm exact file names, branches, screenshots, and update notes; then judge the MOD by the in-game parts above, not only by whether the game launches.

  • Check slot layout, item panels, drag behavior, hotkeys, and readability.
  • Open recipes, stations, queues, and ingredient panels at the player resolution.
  • Check markers, reward selection, trader stock, and quest text before joining a server.
  • Test the language and resolution your players use, especially with other UI or localization packages.

Screens affected

SMX changes how 7 Days to Die is read and operated on screen. Test it as a UI package: inventory, crafting, map, trader, quest, vehicle, and scaling screens all matter.

SMX should be checked on the screens players open every day: inventory, crafting, map, trader, quest, container, vehicle, and settings.

  • A clean launch alone is not enough.
  • Use the resolution and language your players actually use.

Conflict check

UI and HUD packages often conflict with other UI replacements, backpack changes, localization, or server rules.

  • Add UI packages one by one.
  • Check overlap, missing buttons, unreadable panels, and broken item views.

Server permission

Before joining a public server, confirm whether client-side UI files are allowed and whether EAC rules matter for that server.

  • Do not assume every server allows local HUD changes.
  • Publish allowed UI packages if you run a server.
  1. Clean launch

    Start with this UI package and no other UI overhaul.

  2. Daily screens

    Open inventory, crafting, traders, quests, containers, map, and vehicles.

  3. Add-ons

    Add backpack, localization, HUD, and menu MODs one by one.

  4. Server rule

    Join a server only after its rules allow the client UI files.

Install and first test

Run the check on a copy first, then decide whether it belongs in a real save or server.

  1. Check the branchCompare V2.6 page seen; V3.0 needs check with the source page before installing.
  2. Check the install sideStart from Client-side UI files, then confirm whether clients, server, or both sides need matching files.
  3. Test the changed contentCheck inventory, backpack, and toolbelt screens, crafting, workstation, and recipe screens, map, quest, trader, and reward panels, and resolution, scaling, and language display, then save, restart, and reconnect if the MOD is used on a server.
  4. Test a copyUse a copied world or staging server before regular players join.
  5. Record the resultKeep the source page, file label, game branch, and rollback point together.

Server use

Use this part before bringing the MOD into a regular server.

Resolution
Test the resolution your players actually use.
Overlap
Check item panels, reward screens, map markers, and vehicle storage.
Stacking
Do not stack full UI replacements until file conflicts are known.

Notes before use

The page is useful for planning, but it does not replace your own branch and save test.

  • Do not use one successful launch as proof that all screens are safe.
  • Public servers should state whether client UI files are allowed.

Version and file check

Recorded game
V2.6 page seen; V3.0 needs check
Version range
V2.X
Install side
Client-side UI files
Dependency
No confirmed dependency
File size signal
920.0KB
Source updated
2026-04-20

Listing notice

MOD information on 7DTD Signal is collected from publicly available online sources and rewritten for navigation, compatibility judgment, and player reference. If you are a rights holder and believe any material is used improperly, please submit a feedback request and we will check, edit, or remove the entry promptly.