Live cluster population
// HFi Network // ARK ASA
The no-wipe ASA home for long-term PvP.
CrossArk1 is HFi's flagship ARK: Survival Ascended cluster: persistent progression, fair ORP PvP, no pay-to-win shortcuts, and infrastructure built to protect the time players invest.
// Cluster Command
Live cluster snapshot
Loading live dataCurrent spread across the cluster
Unique players active recently
// HFi Network // ASA-ORP Cluster Information
Your CrossArk1 command center.
This page is the central public reference for connection details, settings, rules, Offline Raid Protection, operations, player visibility, and support paths for the HFi CrossArk1 ARK: Survival Ascended cluster.
How to connect
Search the exact server names below in the unofficial server browser to connect.
- Use the HFi-PVP-OfflineRaidProtection-CrossArk1 prefix.
- Choose the map you want to join.
- Join Discord for support-ticket help if the browser is slow to refresh.
// Live Server Roster
Search these exact names.
The roster is presented as connection cards so the full server names stay readable on desktop and mobile.
HFi-PVP-OfflineRaidProtection-CrossArk1-TheIsland
HFi-PVP-OfflineRaidProtection-CrossArk1-ScorchedEarth
HFi-PVP-OfflineRaidProtection-CrossArk1-Aberration
HFi-PVP-OfflineRaidProtection-CrossArk1-Extinction
HFi-PVP-OfflineRaidProtection-CrossArk1-TheCenter
HFi-PVP-OfflineRaidProtection-CrossArk1-Ragnarok
HFi-PVP-OfflineRaidProtection-CrossArk1-Valguero
HFi-PVP-OfflineRaidProtection-CrossArk1-Astraeos
HFi-PVP-OfflineRaidProtection-CrossArk1-LostColonyHFi-PVP-OfflineRaidProtection-CrossArk1-ClubArk// Core Settings & PvP
Official baseline, HFi quality-of-life tuning.
CrossArk1 keeps progression recognizable while reducing avoidable friction for long-term play.
Official Small Tribes baseline
During official ARK events, the cluster follows 2x event rates.
8 players
Rosters must stay consistent across every map in the cluster.
30-minute activation timer
Make sure no one is hiding in your base before relying on protection.
Unlimited
No cooldown.
No upload cooldowns
The normal 72-hour expiration timer still applies.
Artifacts in white drops
Artifacts have been added to white supply drops so cave building does not lock the server out of boss progression. Aberration handles drops slightly differently.
// Stack Sizes
Targeted stack changes
- Meats / Jerky / Berries / Mushrooms / Honey
- 1000
- Organic Polymer / Corrupted Nodules
- 100
- All other items
- Vanilla default
// Cluster Rules
Serious standards, readable structure.
These rules are in addition to the official ARK Survival Ascended Code of Conduct, specifically the Small Tribes ruleset. Questions should go through a Discord support-ticket.
Official Ark Code of Conduct
All rules are in addition to the official Ark Survival Ascended Code of Conduct - specifically the Small Tribes ruleset. You are expected to know and follow both.
Official Ark Code of ConductCharacter Names
- 6.0 | No generic or placeholder names (e.g., '123', 'Human', 'Player', 'aaaa'). Your in-game character name must be unique and identifiable. If you get "arked" (character loss) and your name is generic, admins will deny your character restoration request. We restore from backups using character names. If we cannot identify you, we cannot help you.
PvP & Engagement Rules
We follow the Small Tribes ruleset from the official Ark Code of Conduct. Key points:
- 5.0 | No FOB countering. You may not counter another tribe's forward operating base during a raid.
- 5.1 | No teaming. All raiding and defending is strictly tribe vs. tribe. No alliances and no outside help, unless it is open-world PvP. If it is not your raid, stay out of it.
- 5.2 | Looting cave bugged structures that appear un-ORP'd when ORP should be active is prohibited at all times.
Spam / Build Range
- 4.0 | Cave bases are limited to 150m of spam.
- 4.1 | Non-cave bases are limited to 300m of spam from your base. Land base spam limits may be subject to admin team discretion and evaluated case-by-case.
- 4.2 | Anything beyond these limits may be considered excessive spam and may be removed. These ranges are subject to increase in the future depending on server performance.
Tribe Limitations
- 3.0 | Tribes are limited to 8 members.
- 3.1 | Tribes must maintain the same roster across every map in the cluster.
- 3.2 | This is a no-gameplay-mod cluster. There is no automated enforcement of tribe rosters. All tribes are expected to follow this rule on the honor system.
- 3.3 | HFi Admins will perform manual audits on each map periodically to ensure fair and balanced gameplay. Violations will be addressed.
- 3.4 | One character per account - no exceptions.
Base Limitations (Cluster-Wide)
- 2.0 | Tribes are limited to 2 alpha base spots total cluster-wide. An alpha base spot is any cave, rathole, or other high-value/contested base location. Submit a ticket if you are unsure whether a location is high-value.
- 2.1 | Tribes are allowed 1 non-cave main base per map. This includes open-world base locations or areas such as skylights.
- 2.2 | When re-locating to a new alpha spot, if exceeding the current limit, open a ticket. This allows admins to start the 7 day grace period for moving and prevents structures from unintentionally getting deleted.
- 2.3 | Alpha spot enforcement will be handled strictly. If your tribe already controls 2 alpha spots across the cluster, you may not place permanent or ORP structures inside additional caves, ratholes, or other contested locations just because they are not occupied.
- 2.4 | Permanent farming teleporters and travel setups are allowed, but must be outside caves or contested areas. Farming TPs should be far enough away that they do not interfere with another tribe's ability to claim that location. As a general rule, place them at least 200m away from cave entrances or contested spots.
- 2.5 | Outside farming teleporters must still respect normal spam rules. For cave-related areas, they must also respect the 150m cave spam limit if that location were to be claimed as a base.
Offline Raid Protection & FOB Rules
Rough draft: ORP and FOB rules are subject to change at any time as the cluster matures and edge cases are reviewed.
- 1.0 | ORP Activation. ORP activates 30 minutes after the last tribe member logs off.
- 1.1 | Official Settings. We are running official ORP settings with no custom modifications.
- 1.2 | Active Raiding & FOB Maintenance. A Forward Operating Base (FOB) is strictly for active raiding. If your tribe officially concludes a raid or abandons the push, you must take the FOB down. Dropping a FOB simply to grief, block an entrance, and log off (ORP bombing) is not permitted.
- 1.3 | Combat Logging & "Paused" Raids. If a defending tribe logs off while being actively raided or sieged to trigger the 30-minute ORP timer, the raid is considered "paused." In this specific scenario, the attacking tribe is permitted to leave their FOB in place to maintain the siege line.
- 1.4 | Stale FOBs & The 24-Hour Render Limit. To prevent paused raids from littering the map with permanent structures, a FOB may remain in place for a maximum of 24 hours of inactivity. The attacking tribe must render the FOB at least once every 24 hours to maintain it. If defenders refuse to log back in, or attackers decide not to finish the raid when defenders return, the FOB must be dismantled. Admins reserve the right to wipe any stale FOB that has not seen active PvP progression within a reasonable timeframe.
- 1.5 | Single Target Engagement. A tribe may only actively attack one enemy tribe at a time across the entire cluster. You are allowed to siege multiple bases and maintain multiple FOBs simultaneously, provided they are all strictly targeting that same single enemy tribe. You must conclude your current campaign and dismantle your FOBs before initiating a siege against a different tribe.
// ORP // PvP Fairness
Protection without abuse.
ORP exists to protect long-term progression while the rules continue to mature around real cluster behavior. The current guidance below is intentionally simple and may evolve over time.
Activation timer
ORP activates 30 minutes after the last tribe member logs off.
No custom ORP modifications
The cluster runs official ORP settings.
Single target engagement
One enemy tribe may be actively attacked at a time across the cluster.
// Infrastructure // Backups // Maintenance
Engineered for stability and data retention.
CrossArk1 is maintained like production infrastructure: frequent backups, VM-level cold storage, daily dino refreshes, and staggered restarts to protect performance.
Incremental backups
World states and player character data are backed up every 60 minutes.
Daily VM snapshot
The Windows Server VM is snapshotted daily, stored on-site on dedicated NAS, and replicated off-site to cloud storage.
Wild dino wipes
A wild dino wipe is triggered on every daily boot to keep spawns fresh and high-level rotation moving.
// Daily Restart Schedule
Staggered morning restarts
- The Island
- 6:00 AM
- Astraeos
- 6:00 AM
- Scorched Earth
- 6:15 AM
- Aberration
- 6:30 AM
- Extinction
- 6:45 AM
- The Center
- 7:00 AM
- Ragnarok
- 7:15 AM
- Valguero
- 7:30 AM
- Lost Colony
- 8:00 AM
// Players
Public player hall of fame.
The public Players page highlights active survivors while keeping tribe names, current maps, server movement, identifiers, and admin-only data private.
// Support HFi
Keep the cluster strong.
Support helps sustain the CrossArk1 infrastructure, backups, monitoring, and long-term operations. HFi remains community-first and no pay-to-win.