fortnite-xp-map-codes-windows

本页保存的是公开项目资料快照，阅读过程不需要连接 GitHub。

Fortnite XP Map Codes

Compare Creative island codes, timer requirements and last-check dates. Map availability and XP rewards need separate checks.

English · Español · Português · Deutsch · Français · 简⁠体⁠中⁠文 · 繁⁠體⁠中⁠文 · 日⁠本⁠語 · 한⁠국⁠어

Why this tool exists

XP islands can be renamed, disabled or patched while old codes continue circulating. The status board puts the last check beside every code and lets players narrow the list by AFK flow or timer behavior before launching Creative.

What it does

01 · island-code status board

Separates reachable codes from disabled or patched entries.

02 · no-timer and AFK filters

Filters islands by timer style, AFK flow and last verification time.

03 · last-checked timestamps

Copies a code in one click and keeps useful entries in a favorites list.

Interface tour

• 01. Status board split into active, uncertain and patched islands.
• 02. No-timer and AFK filters for the desired map flow.
• 03. Code cards with creator, last check and quick-copy action.
• 04. Favorites for codes worth retesting after an update.
• 05. Compact check history for changed or disabled islands.

At a glance

Function	What you get
Input	Map type + status filters
What you get	Current island code
Output	Favorites and copied codes

Built for

• Find active map codes
• Filter no-timer or AFK maps
• Avoid patched islands

How to read the result

Status and last-check time should be read together. Active means the code worked during the recorded check, while uncertain means the island needs another visit. Filters describe the reported flow of the map; they do not guarantee a fixed XP rate because islands and rewards can change.

Before you begin

• Keep Map type + status filters ready and confirm that it belongs to the intended Fortnite Creative profile or session.
• Note the current game/client build or data date before changing a profile.
• Choose where Favorites and copied codes will be saved so the previous result is not overwritten.
• Use island-code status board in one short test first; keep the original save, profile or comparison beside it.

Data and recovery

Codes and status history are local reference data. A last-checked label is evidence of a past check, not a promise that an island remains available.

Use automation and game-modification features only where the game rules and session type allow them.

A complete first run

1. Open Fortnite XP Map Codes and confirm the detected Fortnite Creative build or data source.
2. Select the input or profile, then configure island-code status board without changing the defaults that are not part of this test.
3. Review no-timer and AFK filters in the preview or status panel and correct any version, filter or detection warning.
4. Run one controlled action. Compare the visible result with the preview before changing a second setting.
5. Save the profile or export the result, keeping last-checked timestamps available for recovery and comparison.

After a game update

• Sort by last checked and move old favorites back to uncertain status.
• Open codes individually because an island can change without changing its code.
• Recheck timer and AFK labels against the current island flow.
• Keep disabled entries in history so recycled or misleading codes remain recognizable.

Troubleshooting

Common failure pattern: an XP map code is disabled or patched.

A code opens a different island

Compare the creator and last-check details; a reused listing may point to a changed island.

An active code no longer works

Move it to uncertain status and keep the check time; island availability can change without notice.

The list feels stale

Sort by last checked and retest saved favorites before browsing older entries.

Questions

What does an Active code mean?

Active means the island code was reachable at the displayed check time. The timestamp matters because creators can disable or change a map later.

What information belongs in a compatibility report?

Record the exact game build, tool or data version, input used and observed result. Keep unknown fields marked unknown. A screenshot or a successful test in a different version is not evidence for the current build.

Is a working executable or script included?

The current repository contains documentation and an interface concept, not a verified working release. Compatibility notes and screenshots are not execution tests. Do not infer official authorship, supported builds or account protection from them.

---

Download

Review the documented scope and compatibility before choosing a release.

---