FloorConcrete

FloorConcrete is mainly worth checking through map, POI, biome, or prefab placement, audio, model, texture, icon, or decoration assets, recipe unlocks and required books, workstation chain and production steps, resource cost and output timing, and world generation, map seed, and biome layout. Do that in a copied save or test server before changing a main world.

Use Nexus Mods listing for exact file names, branches, screenshots, and update notes, then confirm the in-game behavior listed above still works after a restart.

• Generate or load a test world, visit the affected places, then restart and check quest and trader routes.
• Load the asset in the real screen or place where players will see it, then check missing files and multiplayer visibility.
• Check which recipes are learned by perk, schematic, magazine, workstation, or quest reward.
• Follow the path from raw material to finished item instead of testing one recipe only.

FloorConcrete shows up 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.

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.

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.