Blog posts of '2025' 'November'

Public Rust can be chaos—cheaters, queue times, random wipes, and rules that change overnight. A private Rust server gives you control: your map, your rates, your rules, your community. This guide covers hosting choices, performance tuning, plugins (uMod/Oxide), wipe strategy, and a simple maintenance routine you can copy-paste.

Want it done for you? Launch a ready-to-play Rust server here: Get a Rust server.
Curious who’s behind it or need other services? alejandro7.com.

Why Run a Private Rust Server?

• No strangers, no drama – curate your Discord and keep the vibe consistent.

• Custom gameplay – gather rates, stack sizes, kits, TP rules, map size/seed, monument spawns, vehicles, and more.

• Predictable wipes – schedule wipes when it suits your community (and control BP vs. map wipes).

• Performance – tune entities, plugins, and restart windows for buttery combat and building.

Hosting Options (Pick Your Path)

1) Managed Hosting (easiest)

• Provision in minutes with a control panel (one-click restarts/updates/backups, uMod install, workshop maps).

• Support on patch day when plugins break.

• Perfect if you want to play, not babysit Linux services.
  👉 Get a Rust server

2) Self-Hosting (advanced)

• Rent a VPS/dedicated box or use a home server.

• Install SteamCMD, open ports, run RustDedicated as a service, wire RCON, automate backups and restarts.

• Full control—also full responsibility on patch day.

The Essentials You’ll Touch

• RustDedicated + server.cfg – Boot flags and CVar settings live here.

• uMod/Oxide – Plugin framework (timed rewards, kits, economy, TP, admin tools, QoL).

• RCON – Remote console via tools like RustAdmin or BattleMetrics RCON.

• Backups & Wipes – Save rotations and a clear wipe policy (map, BPs, or both).

Fast Start (Managed)

1. Pick a location close to your players.

2. Name your server, set the admin (ownerID) and a strong RCON password.

3. Choose rates (2x/3x?), map size (3–4k for 50–100 players), and seed.

4. Add core plugins (below).

5. Set scheduled restarts (e.g., daily off-peak).

6. Share IP:Port + name; pin rules and wipe cadence in Discord.
   👉 Launch now: Get a Rust server

DIY Setup Cheatsheet (Self-Host)

Install & Update

• Install SteamCMD → app_update 258550 -beta none validate for RustDedicated.

• Create a service (systemd/Windows service) to auto-start and restart on crash.

Typical start command

Firewall/Ports

• Open game port (e.g., 28015/UDP) and RCON (e.g., 28016/TCP).

• If you set a query port, open that too.

uMod/Oxide

• Install uMod so /oxide/plugins loads community plugins.

• Keep a text list of plugins + versions for quick rollback.

RCON

• Use RustAdmin/BattleMetrics RCON to watch logs, kick/ban, run commands, schedule messages.

Plugin Shortlist (Stable, Player-Friendly)

• Admin/QoL

  • Admin Radar / PlayerDatabase – visibility and tracking for staff.

  • Stack Size Controller – bigger stacks reduce entity count and lag.

  • Auto Purge (inactive bases) – keeps entity count sane over time.

• Gameplay

  • Kits – starter and donor kits (if applicable).

  • ZLevels Remastered – gentle progression for gather/craft.

  • BetterLoot / 2x–3x Gather – speed up early game without destroying balance.

  • NTeleportation – home/outpost/bandit TP with cooldowns to preserve PvP flow.

  • Rust Rewards – playtime or action-based rewards economy.

  • Vanish (admins) – investigate without interference.

• Community

  • Discord Connect – link in-game chat to Discord.

  • Rules/Info GUI – show rules on first join and after wipes.

Add plugins incrementally: one at a time → restart → test → scan logs for errors.

Performance That Actually Feels Good

• Hardware

  • Prioritize high single-core clock; Rust is sensitive to main thread time.

  • NVMe SSD for world saves; avoid HDDs.

  • RAM: 8–16 GB for modded medium servers; add headroom for entity-heavy builds.

• World Settings

  • Worldsize 3000–3500 for 50–100 players; larger costs CPU and travel time.

  • Tune animal/scientist counts; excessive AI spikes server time.

  • Use stack size and purge to keep entity counts down.

• Operational

  • Daily restart off-peak (memory and plugin GC stay fresh).

  • Watch entity count and server FPS; address lag before players complain.

  • Keep plugin count lean; remove anything nobody uses.

Wipe Strategy (Map vs. Blueprints)

• Map wipe – resets bases and monuments; keeps BPs (optional).

• BP wipe – resets researched items; great for fresh seasons.

• Cadence – many communities do biweekly map wipes and monthly BP wipes; adjust to your group.

• Patch day – plan your wipe window around the monthly game updates so you aren’t fighting hotfixes mid-cycle.

Tip: Post wipe dates at the top of your Discord and MOTD. Consistency = happier players.

Security & Moderation

• EAC enabled (default). Don’t disable it.

• Strong RCON password; restrict RCON to specific IPs if possible.

• Use ownerID for the head admin; give moderatorID sparingly.

• Keep an appeals channel in Discord with one-message, one-decision rules to avoid drama.

• Log moderation actions.

Rust+ & Quality-of-Life

• Enable Rust+ so players can pair the companion app with your server.

• Scheduled in-game announcements (restart warnings, wipe countdowns).

• Map link and Discord invite in your server’s description.

Maintenance Ritual (Copy/Paste)

• Daily: auto-restart, quick log skim for red errors, check server FPS/entity count.

• Every wipe: snapshot backup before wipe, test post-wipe spawn points and starter kits.

• Patch day: announce downtime → backup → update server → update uMod & plugins → test with an admin alt → reopen.

• Monthly: prune unused plugins, audit permissions, review feedback.

Troubleshooting Quick Wins

• “Packet Flooding/Timer late/lag spikes” → check plugin loops, reduce AI, entity cleanup, confirm CPU isn’t pegged.

• Players can’t connect → verify ports, correct IP:Port, RCON not blocking, server list visibility may lag—have them direct connect.

• Plugin stopped working after update → update plugin, read issue tracker, temporarily disable to restore stability.

• High entity count → enable purges, increase decay slightly, consider stack size increases, encourage smaller bases.

FAQ

How many slots can I run?
Depends on CPU and plugins. A well-tuned midrange CPU with lean plugins can handle 50–100 players smoothly. Heavy modpacks or huge maps need more muscle.

Do I need daily restarts?
Highly recommended. Memory, plugins, and entity churn all benefit from a clean slate.

Can I move my server later?
Yes. Copy the identity folder (saves/configs) and keep plugin versions aligned. Test on a staging instance first.

How big should my map be?
3k–3.5k is a sweet spot for mid-sized communities. Larger maps look cool but punish performance and travel time.

Ready to Build Your Own Rust Community?

Skip the sysadmin grind and start playing today:

👉 Get a Rust server

Need broader help (site, Discord, branding, integrations)?

👉 alejandro7.com

Set your rules, tune your rates, pick your map—and keep the wipes on your schedule. See you on the shore. 🛶🔧

If you change prices, rotate specials, or just want lines to move faster, a digital menu (on TV/tablet/monitor) is your highest-leverage upgrade. Below is a practical, non-fluffy guide—what it is, why it works, real-world proof, what you need, and exactly how to start.

Ready to get one set up for you? Skip ahead to the CTA sections—“Get a Digital Menu in 48 Hours”—and head to alejandro7 dot com. Alejandro7.com

Why digital menus work (and keep working)

• Instant updates & dayparting. Swap breakfast/lunch/dinner, promos, or sold-out items across all screens in seconds. Major chains invest in digital boards largely for this flexibility—Wendy’s publicly highlighted the ability to adjust items and run value deals with its digital menuboard rollout. AP News

• Shorter, felt wait times. Digital signage reduces perceived waiting; controlled studies show guests feel lines move faster when screens inform/guide them. ScienceDirect+1

• Sales lift you can plan around. Industry benchmarks often cite ~3–5% sales uplift when boards are executed well (clear design, featured add-ons, daypart swaps). Vendor and market studies put typical lift in the low single digits—treat this as directional, then measure your own mix. delphidisplay.com+1

• Compliance made easy (if you’re a chain). In the U.S., chains with 20+ locations must display calories on menus/menu boards; digital makes updates far easier and more legible. U.S. Food and Drug Administration+1

Who benefits most (and what to show)

• Quick-service / fast-casual & drive-thru: rotate by daypart, spotlight bundles, feature value during off-peak. Operators report smoother ordering and easier promo execution with digital boards. QSR Magazine

• Coffee / tea / boba / bakeries / ice cream / juice bars: seasonal flavors and LTOs shine with visuals; keep allergens and sizes obvious. QSR Magazine

• Bars, breweries & taprooms: rotating taps and limited releases update instantly (no more chalk edits).

• Food trucks, pop-ups, ghost kitchens: frequent price/menu changes done centrally across every screen.

• Salons, barbers, spas: digital “service menus” prevent reprint costs and clarify add-ons.

The simple stack (what you actually need)

1. Screens (bright enough for your space, properly mounted)

2. A tiny media player or a smart commercial display (runs the menu app)

3. Menu CMS to schedule dayparts, change items/prices, push updates remotely

4. Templates & content (clear prices, big categories, enticing photos/video)

Reality check on ROI: Even with commercial displays, many operators see payback in 12–18 months when you combine reduced printing/rollout costs with modest sales lift and cleaner ops. SageNet

Launch plan (copy/paste)

1. Pick your “hero” 8–12 items per daypart; cut clutter.

2. Design a rush-hour version (fewer choices, big prices).

3. Feature 2 add-ons (drink + dessert / side + sauce) in every layout.

4. Schedule by daypart; add weather-based swaps if relevant (iced vs. hot). AP News

5. Measure weekly: attach rates, best-sellers movement, average ticket.

6. Iterate visually, not just price. Move winners “above the fold.”

7. For chains: keep calories and nutrition info current in the CMS. U.S. Food and Drug Administration

FAQs (fast answers)

Will this really speed up my line?
Studies find digital signage reduces perceived wait, and QSR ops reports connect boards with smoother drive-thru ordering. You’ll feel it most during peak. ScienceDirect+1

Is there proof of sales impact?
Benchmarks consistently cite low single-digit lift (commonly 3–5%) when boards highlight profitable items and rotate smartly. Start conservative and track your data. delphidisplay.com+1

What about “dynamic pricing”?
Big chains clarified they’re using digital boards mainly for flexible featuring and value offers, not surge pricing. The value here is smart promos and clarity—not sticker shocks. AP News+1

Get a Digital Menu in 48 Hours (Done-for-You)

What you get with Alejandro7:

• Plug-and-play templates matched to your brand (QSR, café, bar, truck, salon)

• Remote updates & daypart scheduling (we can manage for you or hand you the keys)

• Mobile-first versions for QR/table, if you want both

• Performance check-ins (what’s selling, what to promote next)

Ready to go live?
Visit alejandro7.com and tell us your business type plus how many screens you want. We’ll recommend hardware, set up your first layouts, and push your opening playlist—so you’re selling with a digital menu, not talking about one.

Sources & further reading

• FDA menu labeling (20+ locations; calories on menus/menu boards). U.S. Food and Drug Administration+1

• AP News: Wendy’s investment in digital menuboards and clarification on pricing intent (flexibility/value). AP News

• QSR Magazine on drive-thru digital menuboard impact and operator adoption. QSR Magazine

• Peer-reviewed research: digital signage reduces perceived waiting time. ScienceDirect

• Benchmarks on sales lift & ROI context for digital menus. delphidisplay.com+1

If you love Project Zomboid but hate random wipes, griefing, or laggy public lobbies, a private server is the way to go. In this guide, you’ll learn exactly how PZ private servers work, the best way to host one, how to manage mods and performance, and the essential routines that keep your world (and community) stable for months.

Want it set up for you? Spin up a ready-to-play server here: Get a Project Zomboid server.
Or learn more about the team behind it: alejandro7.com.

Why a Private Server?

• Consistency & control – Save settings, mod lists, and rules that don’t reset every week.

• Community – Play with friends or a curated Discord group without randoms.

• Progress that sticks – Backups and scheduled maintenance keep your world alive.

• Custom experience – Adjust loot, zombie population, respawn, erosion, cars, radio events—everything.

Choosing How to Host

1) Managed Hosting (easiest)

• Provisioned in minutes, web panel to manage restarts/updates/backups.

• Mod installs and workshop updates are automated.

• Support when a patch breaks something.

• Great if you just want to play, not babysit Linux services.

Tip: If you want a turnkey setup with hands-on help, go with Get a Project Zomboid server.

2) Self-Hosting (advanced)

• You rent a VPS or use a home server.

• You install SteamCMD, set firewall/ports, configure services, cron jobs, backups.

• Ultimate control, but you own every problem (patch days, mod breaks, IO spikes).

Core Concepts (What Actually Matters)

• Server settings live in files you can version and back up (servertest.ini, SandboxVars.lua, etc.).

• Workshop mods need both server and client enabled—pin exact mod IDs to avoid mismatches.

• Backups and update order matter: back up → update server → update mods → restart → test.

• Economy of restarts: small servers can run for days, but scheduled off-peak restarts keep RAM/GC tidy.

Fast Start: Turnkey Hosting Flow

1. Pick a plan → Get a Project Zomboid server.

2. Choose location close to your players.

3. Name your server, set an admin password, and whitelist mode (optional).

4. Paste your initial mod IDs (you can add more later).

5. Set a daily restart time (off-peak for your group).

6. Launch → Share IP:Port + password with friends.

7. Play. Adjust servertest.ini and SandboxVars.lua over time as your group evolves.

DIY Setup Overview (If You’re Self-Hosting)

• Install: SteamCMD → download ZomboidDedicatedServer.

• Firewall/Ports: open the required game and query ports (your host panel typically lists these explicitly).

• Run as a service: systemd (Linux) or a scheduled task/service (Windows) for auto-restart on crash.

• Backups: tar/zip the Zomboid/Server and Zomboid/Saved directories on a schedule and keep several rotations.

• Update flow: stop server → back up → update server → update mods → start → verify logs.

Keep a simple runbook that your co-admins can follow exactly.

Configuration: The Files You’ll Touch Most

• servertest.ini – Main server settings (name, password, whitelist, voice, PVP, safehouse rules).

• SandboxVars.lua – Zombies, loot rarity, infection rules, car frequency, erosion speed, etc.

• SpawnRegions.lua – Starting locations.

• server.ini / admin.txt equivalents – Admin roles, privileges, and server list entries.

• mods.txt (or web panel) – Workshop mod IDs and load order.

Pro tip: Keep these in a Git repo or cloud folder. Commit after each change so you can roll back when a mod update goes sideways.

Mods: Keep Them Stable

• Pin exact Workshop IDs and audit after big PZ patches.

• Load order matters—UI frameworks first, content next, patches last.

• Change one thing at a time—restart, test, check logs for red flags (missing textures, lua errors).

• Share the list with players: a pinned Discord post or a tiny site page goes a long way.

Performance Tuning (Biggest Wins First)

1. Choose the right hardware:

   • CPU single-core speed > core count for small/medium servers.

   • SSD/NVMe storage; avoid spinning disks.

   • Enough RAM for mods & player count (2–4 GB baseline; add more for heavy modpacks).

2. Right-size your pop settings:

   • Extreme zombie counts look cool but crush ticks. Raise gradually.

3. Scheduled restarts:

   • Once daily is plenty for most communities; twice daily for heavy modpacks.

4. Headless maps & cleanup:

   • Disable unused regions; periodically clean abandoned safehouses with clear rules.

5. Network locality:

   • Pick a region close to players. Latency hurts combat and driving most.

If you just want it to feel smooth: let a managed host size it for you—Get a Project Zomboid server.

Security & Anti-Griefing

• Whitelist mode and a private Discord invite flow.

• Strong admin password; give mod permissions sparingly.

• Safehouses: enable claim limits and protection rules that fit your vibe.

• Backups: daily + on-demand before big events or mod changes.

• Audit logs after incidents; keep notes on repeat problems or plugins that help.

Community Rules That Actually Work

• Wipes: set expectations (e.g., seasonal wipes every X months or only on major patches).

• PVP: if enabled, clarify zones/times/consent rules.

• Raiding: all hours vs. windowed periods—less burnout if limited.

• Trading & economy: pin your barter rules and base prices to reduce arguments.

• Appeals: one channel, one message, one decision (keeps drama low).

Maintenance Ritual (Copy/Paste This)

• Daily: automated restart, quick glance at latest logs.

• Weekly: backup rotation check, disk space check, minor config tidy.

• Patch Day: announce downtime → back up → update server → update mods → test with 1–2 admins → reopen.

• Monthly: review performance, prune dead bases, poll the community on next features.

Troubleshooting Quickies

• Players get “mod mismatch”: confirm workshop IDs & load order match server; have them restart Steam to refresh mods.

• Rubber-banding: reduce zombie density, check CPU spikes, confirm players are near the server region.

• Can’t join: verify server is running, correct IP:Port, firewall/ports open, server password correct, and whitelist (if any).

• Crash after patch: disable newest mod(s); re-enable one at a time to isolate.

Frequently Asked Questions

How many players can I host?
It depends on CPU speed, disk, and mod load. Small groups (4–12) are easy on modest hardware; 20–40 needs stronger single-core performance and stricter sandbox settings.

Do I need restarts?
Yes. Once per day keeps memory and scripts healthy, especially with many mods.

Can I migrate worlds between hosts?
Yes. Copy the saves and config folders (and keep the same mod set). Test on a staging server first.

How do wipes work?
You can wipe characters, map chunks, or both. Always back up first, announce clearly, and consider seasonal schedules.

Ready to Play?

If you’d rather spend time surviving than sysadmin-ing, let experts provision and maintain it for you:

👉 Get a Project Zomboid server

Want to see the broader services, portfolio, and contact options?

👉 alejandro7.com

Build a world your group actually wants to log into—stable, modded the way you like it, and online when you are. Happy surviving!