MOD Wiki / POI Scourge

POI Scourge

POI Scourge overview, version signal, and install notes.

POI Scourge

POI Scourge is a enemy or horde-behavior change for 7 Days to Die. Use it when you want to change combat pressure or combat tools, 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.

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

Details

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

POI Scourge is a enemy or horde-behavior change for 7 Days to Die. Use it when you want to change combat pressure or combat tools, 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.

Enemy pressure

POI Scourge is mainly worth checking through enemy spawns and pressure, map, POI, biome, or prefab placement, spawn rules and encounter density, enemy health, damage, speed, and special effects, server spawn load and loot bags, and class, perk, book, or level progression. 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.

  • Check normal POIs, night travel, blood moon, loot bags, and server spawn limits before raising difficulty.
  • Generate or load a test world, visit the affected places, then restart and check quest and trader routes.
  • Check day, night, biome, POI, wandering horde, and blood-moon behavior separately.
  • Test common enemies before judging bosses or high-tier fights.

Screens affected

POI Scourge is a enemy or horde-behavior change for 7 Days to Die. Use it when you want to change combat pressure or combat tools, then check the Nexus page for the current file, dependency, and version notes before changing a save or server.

POI Scourge 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 1.5 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 enemy spawns and pressure, map, POI, biome, or prefab placement, spawn rules and encounter density, and enemy health, damage, speed, and special effects, 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 1.5
Version range
V3.X
Install side
Server & Client Side
Dependency
No confirmed dependency
File size signal
166.0KB
Source updated
2026-06-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.