The best Hell Let Loose server configuration depends on whether you run an open community server, a passworded clan/event server, or a temporary seeding session. Start with a rented dedicated server, then set a descriptive identity, correct ports, named admin permissions, an RCON policy, and a map rotation that matches your player count. There is no universal “best” queue size, ping limit, or rotation: those choices should follow your moderation capacity and region. This guide gives practical presets while identifying the settings that are version- or provider-dependent.
What do you need before configuring a Hell Let Loose server?
Team17 restricts hosting, so groups normally rent a dedicated game server from an approved provider rather than running one on a home PC. The provider’s control panel is the operational hub: use it to start and stop the service, set the server name and password, edit configuration files, create backups, and schedule tasks. Keep the panel credentials separate from your game-admin credentials and enable two-factor authentication if the provider offers it.
- A rented server: Select a region close to most players and enough slots for your intended events. Current slot availability and prices change, so verify them in the provider panel at purchase time.
- SteamID64 values: You need the exact 64-bit Steam identifier for every administrator and VIP entry.
- RCON credentials: RCON is the remote protocol that lets staff monitor and administer the server without joining as players.
- A written policy: Decide who can kick, ban, change maps, move players, or alter settings before assigning ranks.
- A rotation plan: Prepare separate public, event, and seeding rotations instead of changing a live list ad hoc.
Should your server be public, private, or used for seeding?
Choose access rules first; they determine the password, queue, moderation workload, and rotation. The HLL Admin definitions treat a public server as not password protected and an event server as password protected.
| Use case | Access and password | Queue and moderation | Rotation and message |
|---|---|---|---|
| Public community | Leave the join-password field empty so the server appears openly in the browser. | Use a finite queue, auto-balance, an idle-kick rule, and a published high-ping policy. Staff should monitor RCON during peak hours. | Mix popular maps with variety; state house rules in the welcome message. |
| Private clan or event | Set a join password and distribute it only to registered players. | Use named admin tiers and event-specific moderation. A queue may be unnecessary when attendance is controlled. | Use a schedule-specific rotation and a welcome message containing times, password guidance, and match rules. |
| Seeding session | Usually open the server so prospective players can find it. | Temporarily simplify rules and actively invite players through your community’s Discord. Remove temporary restrictions when the seed target is reached. | Switch to a smaller, popular map and publish the exact cutoff for returning to normal rules. |
How do you set the server identity and access controls?
Open the provider panel’s server-settings or launch-configuration page, edit the name and password, save, and restart if the panel requests it. A useful public name tells a stranger what they are joining without requiring a Discord search.
Build a searchable server name
Include the region, community name, game mode or focus, language, and a short house-rule hint. For example, a name can identify a European English-speaking community and its no-toxic-chat policy without becoming a paragraph. Avoid decorative characters that make the listing difficult to search or sort.
Set the password deliberately
Leave the password blank for a public listing. For a clan or event, use a strong, time-limited password and change it after the event. A password is an access control, not a substitute for moderation: staff still need RCON permissions and a ban procedure.
Write the welcome message
Use the welcome-message field exposed by your RCON tool or panel to state the map rules, idle limit, language expectations, Discord address, and where players can report problems. For events, include the start time and whether spectators or late joiners are allowed.
Which ports does a Hell Let Loose server use?
LOW.MS documents these defaults: 7777/UDP for game traffic, 7778/UDP for the Steam query, and 7779/TCP for RCON. Treat the provider panel as authoritative because providers can allocate a different base port.
| Function | Documented default | Protocol | What to verify |
|---|---|---|---|
| Game | 7777 |
UDP | Use the game port shown in your provider panel. |
| Steam server query | 7778 |
UDP | It is normally the game port plus one. |
| RCON | 7779 |
TCP | It is normally the game port plus two; copy the panel’s value into your RCON client. |
If your allocated game port is not 7777, apply the documented offsets only as a starting check: query is base port plus one and RCON is base port plus two. Do not open ports guessed from another host. A wrong protocol or stale port is the usual reason a server appears in the panel but not in the browser, or an RCON client cannot connect.
How do you add admins and define their permissions?
The panel exposes configuration files for administrators, map rotation, and server settings. AdminUsers.ini identifies users and their rank; AdminPermissions.ini defines what each rank can do. Add the correct SteamID64, save the file, and restart the server so the change loads.
- Stop the server from the provider panel, or use its documented safe-edit function.
- Open
AdminUsers.iniand add each administrator’s SteamID64 with the intended rank. Check every digit; a display name is not an identifier. - Open
AdminPermissions.iniand grant only the commands required by each rank. Keep map-changing and ban authority with trusted senior staff. - Save a backup copy of both files before restarting.
- Start the server and test each rank with a non-destructive command. Remove and re-add an account if a rank does not load rather than granting broader permissions blindly.
Use tiers such as moderator, administrator, and owner to make accountability clear. A smaller team can use fewer tiers, but every person should know who handles bans, appeals, technical failures, and match scheduling.
What is the difference between RCON and CRCON?
RCON is the underlying remote-control protocol supplied by the game server. CRCON is a web-based administration layer that uses RCON and adds logs, statistics, Discord integration, moderation workflows, VIP management, automation, map rotation tools, map shuffle, and condition-based settings such as a different rotation late at night or during seeding.
| Capability | Basic RCON client | CRCON-style web layer |
|---|---|---|
| Live administration | Commands for player and server control. | Commands plus a dashboard for staff. |
| Moderation records | Depends on the client’s own history. | Centralized logs and statistics are available. |
| Community integration | Usually manual. | Discord notifications and automated actions can be configured. |
| Rotation and automation | Manual map changes or client-specific scripts. | Map rotations, shuffle, VIP handling, and condition-based automation. |
| Compatibility | Depends on the RCON implementation. | Check that the release supports your server’s current API version before upgrading. |
Use plain RCON when a small staff only needs reliable commands. Add CRCON when several moderators need an audit trail, Discord alerts, scheduled behavior, or a browser interface. Store the RCON password as a secret; anyone who obtains it can potentially administer the server.
How should you configure the queue, auto-balance, and fairness rules?
RCON tooling exposes maximum queued players, team-switch cooldown, auto-balance and its threshold, idle kick, high-ping threshold, vote-kick controls, profanity filtering, VIP slots, and welcome messages. Set each value to match your community’s policy rather than copying a number from another server.
Queue size
The RCON v2 queue method documents a range of one to six players. A short queue keeps a public listing active without trapping newcomers behind a long wait; a larger queue can retain regulars during peak times but may discourage first-time players. Review join and leave logs after a busy evening and adjust one step at a time.
Auto-balance and team switching
Enable auto-balance for a public server and set a threshold that prevents constant moves when teams are nearly even. A team-switch cooldown reduces last-second stacking. For a private match, disable automatic moves only when captains or referees have an agreed manual process.
Idle, ping, and vote-kick rules
Publish an idle limit before enforcing it, with a longer allowance during brief disconnects or reconnection windows. Set a high-ping threshold that reflects your region and test it during normal peak traffic; an aggressive threshold can remove players whose connection is playable. Configure vote-kick controls so a coordinated group cannot remove players without a clear reason, and use profanity filtering as a supplement to human moderation.
VIP slots
Reserve VIP capacity only if your community can explain who qualifies and how many places are protected. Too many reserved slots make a public server look full while ordinary players wait; too few may fail to retain the regulars who seed it.
What timer settings are available in Update 17.1?
The official Update 17.1 brief (Team17, 2025) added RCON controls whose changes apply at the next match or when the current map resets. The published ranges are version-sensitive:
| Setting | Allowed range | Operational note |
|---|---|---|
| Warfare match timer | 30–180 minutes | Applies on the next match or map reset. |
| Offensive match timer | 50–300 minutes | The total is divided among five capture-point phases; 300 minutes provides 60 minutes per phase. |
| Control Skirmish match timer | 10–60 minutes | Applies on the next match or map reset. |
| Warfare warm-up timer | 1–10 minutes | Set through the new RCON control. |
| Control Skirmish warm-up timer | 1–10 minutes | Set through the new RCON control. |
Offensive warm-up is the exception: it remains governed by the global spawn-wave system rather than the new warm-up control. Tell players when a timer change will take effect; changing a value during a live round does not rewrite that round’s clock.
How do you build a map rotation that keeps a server healthy?
Put the map-and-mode sequence in the provider panel or RCON tool, then test it from a full restart through several transitions. CRCON can shuffle maps and apply different rotations based on conditions such as time of day or seeding status.
For a public rotation
Lead with a popular, readable map to attract first-time players, then alternate familiar and less-played choices. Avoid a sequence that repeatedly places a long Offensive match after another long match if your audience usually leaves during extended rounds. Keep the list finite enough that players can understand what is coming next.
For an event rotation
Use only the maps and modes in the event schedule, in the required order. Password the server, put the timetable in the welcome message, and disable automation that could shuffle or replace the referee’s next map.
For late-night and seeding periods
Create a smaller-map rotation for low population and switch back when the server is healthy. Condition-based rules in CRCON can automate that transition, but a moderator should still verify that the player count and map state justify the change.
How do you seed a new server from zero players?
Seeding means moving from an empty server to roughly the 40-player threshold at which a match can sustain itself, according to LOW.MS (2026). It is a coordinated community activity, not a setting that fills a server automatically.
- Announce a seeding window and the temporary rules before anyone joins.
- Switch to the smaller, popular map rotation and keep the server visible with no join password unless the session is invitation-only.
- Use a simple rule shape, such as middle point only, no artillery, and no armor until there are enough players on each side. Publish your exact rule and the player-count cutoff; these are examples, not a universal HLL standard.
- Call players in through Discord and have moderators join early so new arrivals see active squads and organized play.
- At the agreed threshold, announce the change, restore the normal rotation and rules, and remove any temporary restrictions.
Record how long each seed takes and which map produces the best retention. That local history is more useful than copying another community’s threshold.
Which settings should you use for each group type?
These presets combine the documented controls into starting points. They are operating recommendations, not official best-value tables.
| Setting area | Public community starting point | Private clan/event starting point | Seeding starting point |
|---|---|---|---|
| Name | Region, community, language, and concise rules. | Community, event name, date or match label. | Community plus “seeding” and the temporary rule summary. |
| Password | Empty. | Required; rotate after the event. | Usually empty to maximize discovery. |
| Queue | Finite queue within the documented 1–6 range. | Short or disabled when attendance is controlled. | Short enough that new players can enter quickly. |
| Moderation | Auto-balance, published idle/high-ping rules, vote-kick oversight. | Named tiers, referees, and event-specific permissions. | Active moderators and a clearly announced cutoff. |
| Rotation | Popular maps mixed with variety. | Fixed event order. | Smaller popular map, then automatic or manual return to normal. |
| Automation | Optional CRCON alerts and condition-based changes. | Minimize automation that could disrupt the schedule. | Use a condition-based switch only after testing it. |
How do you choose a hosting provider without relying on a headline price?
Compare the operational features that affect uptime and administration, not just the advertised monthly amount. Prices, regions, slot limits, and promotions change, so check the current panel before ordering.
- Region and latency: Choose a location near the majority of players and confirm that the provider offers the required slot capacity.
- Panel quality: Look for clear lifecycle controls, editable configuration files, restart history, and scheduled tasks.
- RCON access: Confirm that the panel exposes the RCON host, port, and password and allows the client or CRCON version you intend to use.
- Backups: Verify whether configuration backups are manual, automatic, retained for a stated period, and restorable without opening a support ticket.
- File permissions: Ensure your staff can edit rotation and admin files without sharing the provider’s master account.
- Support and migration: Check how quickly the provider handles a failed allocation and whether you can export your configuration if you move hosts.
No source establishes a peer-reviewed performance benchmark or a universal hardware-sizing formula for HLL servers. Treat claims about guaranteed performance as provider-specific and test your actual player load during a busy session.
What should you check when a setting does not work?
- Server is not visible: Confirm the game and Steam-query ports in the panel, including UDP protocol and any provider-specific base-port offsets. Restart after changing them.
- RCON will not connect: Check that you are using the TCP RCON port, the current host address, and the password generated by the panel. Make sure a firewall or corporate network is not blocking TCP.
- Admin commands fail: Recheck the SteamID64 in
AdminUsers.ini, the rank spelling, and the matching permissions inAdminPermissions.ini; restart to reload both files. - Players are moved unexpectedly: Review auto-balance threshold, team-switch cooldown, and any CRCON automation before changing the map rotation.
- Timer appears unchanged: Update 17.1 controls take effect at the next match or map reset, not necessarily immediately. Offensive warm-up still follows spawn-wave behavior.
- Seed collapses: Use the smaller rotation, state temporary rules in the welcome message, and have moderators invite players directly rather than waiting for organic browser traffic.
How do you maintain the configuration after launch?
Keep a dated copy of every edited file and record who changed a permission, timer, rotation, or automation rule. Review moderation logs and queue abandonment weekly, then adjust one policy at a time so you can see its effect. Before a major event, test the password, RCON login, map order, welcome message, and backup restore on a scheduled rehearsal rather than discovering an error during the first round.
Frequently Asked Questions
Can I run a Hell Let Loose server from my own PC instead of renting one?
The HLL Admin FAQ states that hosting is restricted by Team17 and directs groups to rent a game server from a provider. A home machine therefore is not the normal supported hosting path; use a provider panel for the dedicated service.
Do I need CRCON if only two people moderate our server?
No. A basic RCON client is sufficient for live commands when the staff is small. CRCON becomes useful when you need searchable logs, Discord notifications, VIP workflows, scheduled automation, or several moderators working from a shared web dashboard.
How can I safely test a new admin rank?
Create the least-privileged rank first, add a test SteamID64, restart, and run a harmless command while another administrator watches the logs. Expand permissions only after confirming that the intended commands work and restricted commands remain unavailable.
Why do players leave during a long Offensive match?
Offensive time is split across five capture-point phases, so a high total can produce long individual rounds. Review your audience’s tolerance, announce the timer in the server message, and choose a lower value within the allowed range for the next scheduled match.