Server browser filters · Week 250–251 current-player evidence boundary
ICARUS Server Browser: Matching Version and Duplicates
Quick Answer
The ICARUS Dedicated Server Browser left beta in Week 244. Its Matching Version filter is enabled by default, so servers on a different game version are hidden unless you turn that filter off. Week 244 also fixes nonmatching servers appearing while discovery was still running, duplicate peer-to-peer entries when multiple friends shared one session, and refresh feedback: the refresh button rotates while a search is active. Start by letting discovery finish, check the Matching Version state, and refresh once. These controls explain listing and duplicate-result behavior; they do not prove that a server is reachable or provide a universal fix for passwords, ports, firewalls, hosting configuration, or provider outages.
- Reading time
- 8 minutes
- Difficulty
- Listing and filter diagnosis
- Checked
- 2026-10-03
On this page
Guide details
Before you begin
Use the Week 244 server-browser controls correctly and distinguish filter or duplicate-result fixes from connection and hosting problems.
Week 244 browser discovery, filters, duplicates and refresh state; no invented networking, hosting, password, port, or universal connection fixes.
- Status
- Official ICARUS release evidence plus bounded exact-query review
- Edition
- Week 250–251 current-player evidence boundary
- Platform
- PC · Steam
- Checked
- 2026-10-03
- Check note
- Only the cited release facts are verified. Search volume, keyword difficulty, external SEO score, unsupported values, and later changes remain Unknown.
Before you set out
Prerequisites#
- Use Week 244 build 3.0.22.155681 or later.
- Record the client version and intended server version before changing filters.
- Distinguish a dedicated-server entry from a friend peer-to-peer session.
- Do not expose passwords, addresses, account data, or private server details in screenshots or reports.
How the ICARUS server browser changed in Week 244#
Week 244 moves the Dedicated Server Browser out of beta after a quality pass. The saved release focuses on discovery presentation rather than network setup. Matching Version is on by default, which keeps incompatible builds out of the normal result list but can make a known server appear absent. During active discovery, the older browser could also show servers that did not match the selected filters; the update fixes that state. A separate peer-to-peer issue could produce duplicate rows when multiple friends were connected to the same session. The fix deduplicates those friend entries. Finally, refresh now has an explicit busy signal: its icon rotates while the search is in progress. These details give a reliable diagnostic order—wait, inspect the filter, refresh once, classify the entry—without promising that every missing server is a browser bug. Keep three states separate: filter state controls which rows qualify for display, discovery state tells you whether the search is still running, and connection state begins only when a listed server is actually contacted. A completed filtered list can diagnose visibility, but it cannot by itself validate credentials, ports, firewall behavior, host capacity, or provider reachability.
Route 02
Find or clean up a server-browser result#
Resolve listing state before changing network or host configuration.
Confirm both versions#
Record the current client build and the server build supplied by the host. A version mismatch is a real compatibility clue, not merely a cosmetic filter issue.
Open the Dedicated Server Browser#
Use the current browser that left beta in Week 244. Do not mix its behavior with an older screenshot or beta-era walkthrough.
Let discovery finish#
Watch the refresh icon. While it rotates, results are still being discovered and filtered; judging the list early can produce a false missing-server conclusion.
Check Matching Version#
Leave the default enabled when you want joinable matching builds. Disable it only to diagnose whether a known server is hidden because its version differs.
Inspect the revealed build#
If a server appears only after disabling Matching Version, treat the version mismatch as the finding. Do not claim the filter itself prevented a compatible join.
Refresh once after a known change#
If the host has just updated or restarted, run one refresh and wait for rotation to stop. Repeated clicking does not establish faster or more accurate discovery.
Classify duplicate rows#
Determine whether repeated entries refer to one peer-to-peer session shared by multiple friends. Week 244 specifically fixes that duplicate P2P presentation.
Separate listing from connection#
A visible row does not prove that ports, passwords, firewall rules, host capacity, or provider connectivity are correct. Diagnose those systems with their own evidence.
Preserve the observed state#
Record version, filter state, discovery completion, entry type, and outcome. Keep private addresses and credentials out of the evidence.
Pocket list 03
Verified server-browser boundaries#
- The Dedicated Server Browser left beta in Week 244.
- Matching Version is enabled by default and can be disabled.
- Nonmatching results appearing during discovery were fixed.
- Duplicate P2P entries from multiple friends in one session were fixed.
- The refresh icon rotates while a search is active.
- The release does not define ports, firewall rules, passwords, host settings, or universal connection fixes.
- Record the client build, intended server build, discovery state, Matching Version setting, and entry type before changing anything; that sequence distinguishes a hidden version mismatch from an unfinished search or a duplicate peer session.
- A server row is listing evidence only. It does not prove credentials, reachability, firewall state, capacity, mod compatibility, provider availability, or host health.
- If a row appears only after Matching Version is disabled, report the build difference rather than forcing a join; if the row is visible but connection fails, move to a separate authorized network or host diagnosis.
- Keep private addresses and passwords out of screenshots and reports, and date later observations so Week 244 behavior is not silently presented as permanent.
- After the list stabilizes, preserve one final screenshot or written observation instead of stacking refresh actions; repeated searches do not prove a stronger diagnosis and can erase the exact filter state that explained the result.
Fault ledger
If the server list still looks wrong#
- A known server is missing
- Wait for refresh to finish, then inspect Matching Version. If disabling it reveals the row, compare client and server builds before attempting to join.
- Servers ignore the chosen filter
- Confirm Week 244 or later and wait until discovery completes. The fixed issue specifically involved nonmatching results appearing during active discovery.
- The same friend session appears several times
- Confirm that the rows are one peer-to-peer session shared by multiple friends. Week 244 addresses this duplicate case.
- Refresh seems unresponsive
- Look for the rotating refresh icon and allow the current search to complete. Do not stack refresh actions.
- The server is listed but cannot be joined
- Treat that as a separate connection problem. The browser release does not prove password, port, firewall, hosting, or provider status.
Field questions
Dedicated Server Browser questions#
- Why is Matching Version already on?
- Week 244 documents it as the default so incompatible builds stay out of the normal list.
- Can I show servers on another version?
- Yes, the filter can be disabled for diagnosis, but appearing in the list does not make the builds compatible.
- Why did one friend session appear more than once?
- The older browser could create duplicate P2P rows when multiple friends shared a session; Week 244 fixes that case.
- Does the update fix every connection failure?
- No. It covers discovery, filtering, duplicates, and refresh feedback, not all network or host problems.