MOD Wiki / Crafted In

Crafted In

Crafted In overview, version signal, and install notes.

Crafted In

Crafted In is a UI or HUD change for 7 Days to Die. Use it when you want to reduce repeated inventory or search work, then check the Nexus page for the current file, dependency, and version notes before changing a save or server.

Images

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

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

Details

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

Crafted In is a UI or HUD change for 7 Days to Die. Use it when you want to reduce repeated inventory or search work, then check the Nexus page for the current file, dependency, and version notes before changing a save or server.

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

Inventory and storage flow

Crafted In is mainly worth checking through slot count, carry capacity, and encumbrance, containers, quick stack, and item transfer, crafting queue and recipe material use, shared storage on multiplayer worlds, inventory, backpack, and toolbelt screens, and crafting, workstation, and recipe screens. Do that in a copied save or test server before changing a main world.

Use Nexus Mods 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.

  • Fill slots with real loot, die once if relevant, restart, and check whether items remain valid.
  • Move mixed stacks between player, vehicle, workstation, and base containers.
  • Queue several recipes, leave the menu, restart, and check materials and outputs.
  • Have two players touch the same container before using it on a busy server.

Screens affected

Crafted In is a UI or HUD change for 7 Days to Die. Use it when you want to reduce repeated inventory or search work, then check the Nexus page for the current file, dependency, and version notes before changing a save or server.

Crafted In 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 V3 Mods; MOD Patch Notes 1.0.8 with the source page before installing.
  2. Check the install sideStart from Server & Client Side, then confirm whether clients, server, or both sides need matching files.
  3. Test the changed contentCheck slot count, carry capacity, and encumbrance, containers, quick stack, and item transfer, crafting queue and recipe material use, and shared storage on multiplayer worlds, 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
V3 Mods; MOD Patch Notes 1.0.8
Version range
V3.X
Install side
Server & Client Side
Dependency
No confirmed dependency
File size signal
19.0KB
Source updated
2026-07-07

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.