AFK Journey 1.7.3 New Skins Preview Guide

AFK Journey Version 1.7.3 previews a broad cosmetic lineup for Cyran, Evie, Peggy, Kulu, Mehira, and Merlin. The range makes the update appealing to collectors, but the preview does not by itself establish the final acquisition route for every skin. A costume may come from an event, store, pass, milestone, bundle, or other system, and community labels should not be treated as official until the live client confirms them.

This guide evaluates the lineup through hero usage, visual exposure, ownership overlap, acquisition certainty, and budget. It does not invent prices or promise that a previewed skin is free.

Confirmed Lineup and Unknown Details

The six named heroes are the core of the announced cosmetic discussion. Exact names, rarity labels, dates, prices, and acquisition methods should be copied from the live Version 1.7.3 pages.

Hero	Confirmed planning point	Must be verified live
Cyran	Included in the previewed cosmetic lineup	Skin name, route, date, cost
Evie	Included in the previewed cosmetic lineup	Skin name, route, date, cost
Peggy	Included in the previewed cosmetic lineup	Skin name, route, date, cost
Kulu	Included in the previewed cosmetic lineup	Skin name, route, date, cost
Mehira	Included in the previewed cosmetic lineup	Skin name, route, date, cost
Merlin	Included in the previewed cosmetic lineup	Skin name, route, date, cost

Do not combine a community infographic with an official preview and present the result as one confirmed reward chart.

Start With Hero Usage

Open recent battle history and team presets. A cosmetic for a frequently used hero receives repeated visibility in formations, battle introductions, menus, and profile displays. A skin for an unbuilt hero may function only as a collection item.

Classify each hero:

Core: used in several current modes.
Specialist: used for one valuable matchup or mode.
Occasional: selected infrequently.
Unbuilt: not currently usable.
Collection favorite: valued regardless of combat use.

A core hero normally deserves more budget than an occasional hero, unless the purchase goal is explicitly collection.

Compare Visual Exposure

AFK Journey presents characters through battle models, hero pages, story scenes, formations, and promotional displays. Not every costume detail receives equal exposure.

Inspect the complete model, back view, battle scale, portrait, and any ability presentation. A costume with beautiful close-up details can look similar to the default model during normal combat. Conversely, a strong silhouette or color change can remain visible at small scale.

Do not assume an outfit changes ability effects, voice lines, portraits, or animations unless the product page says so.

Evaluate Each Hero Separately

Cyran

Compare the new design with Cyran's normal role and existing visual identity. Decide whether the costume will become the default or only a temporary novelty.

Evie

Check color contrast and how the outfit reads in the teams where Evie is actually used. A favorite support can generate high menu and battle exposure even without leading damage charts.

Peggy

Review model visibility and portrait value. If Peggy is not currently developed, separate future build interest from immediate cosmetic use.

Kulu

Check whether the new appearance remains distinctive at battle scale. Small accessories should receive less weight than silhouette and dominant palette.

Mehira

Mehira may appeal strongly to collectors. Compare the skin with existing cosmetics and ask whether the account will equip it consistently.

Merlin

Merlin's broad identity can make alternate styling attractive, but acquisition value still depends on actual use, display preference, and the confirmed route.

These sections are evaluation prompts, not rankings.

Verify Acquisition Routes

When Version 1.7.3 is live, create a six-row acquisition table. Record official skin name, event or store page, opening and closing dates, free requirements, paid currency, and claim deadline.

A “free” label can hide demanding ranking or participation conditions. A “paid” label can overlook a free event path. Use the exact client rule.

If a skin comes from a login event, confirm missed-day recovery. If it comes from a pass, calculate natural completion. If it comes from a store, inspect individual and bundle options. If it comes from ranking, do not count it as guaranteed.

Separate Free, Earned, and Paid

Use three categories:

Free claim: available without gameplay or payment after meeting basic eligibility.
Earned: requires missions, milestones, ranking, or event currency.
Paid: requires premium currency or money.

This language is more accurate than calling every non-store reward free. Time and competitive requirements are still costs.

Build a Cosmetic Priority Score

Score each skin from 1 to 5 for hero usage, design preference, visual visibility, uniqueness, and acquisition value. Weight usage and preference most heavily.

A possible weighting is 30% usage, 30% preference, 15% battle visibility, 15% uniqueness, and 10% acquisition value. Collectors can increase the uniqueness weight, but should keep a separate collection budget.

If two skins are close, wait for unedited in-game footage. Preview art can exaggerate lighting and detail.

Check Wardrobe Overlap

Open existing cosmetics for all six heroes. Assign each one a role: default, competitive, seasonal, profile display, or collection. A new skin should fill a different role or clearly replace an old favorite.

Do not buy because an account “almost has every skin.” Completion pressure can turn a low-use item into an expensive obligation.

For heroes with no owned alternate costume, a new skin may have more novelty value. For heroes with several strong options, the new design needs a clearer advantage.

Free-to-Play Plan

Free-to-play players should claim guaranteed cosmetics and evaluate earned routes by time. Prioritize tasks that overlap with normal play. Do not spend diamonds on refreshes until the live event shows the exact benefit.

If several earned skins share one event currency, calculate the total cost before exchanging. Unique limited cosmetics may come before ordinary materials, but account progression can still matter more for a developing player.

Avoid upgrading an unused hero solely to justify a free costume.

Paid Player Plan

Paid players should establish a total Version 1.7.3 cosmetic budget before opening individual offers. Six appealing skins can create repeated small purchases that exceed one planned large purchase.

Players who decide to recharge can review options through Topuplist and use the dedicated AFK Journey top-up page. Verify player ID, server, product, currency, and payment total before ordering.

Purchase only after the live route and deadline are confirmed. Do not pay based on a preview assumption.

Bundle Evaluation

If a bundle includes a skin with other resources, value each extra according to actual account use. Common materials with a large displayed quantity may add little value to a veteran account.

Compare:

Skin-only option, if available.
Bundle price.
Useful extras.
Unused extras.
Regional taxes and currency.
Whether another desired skin uses the same currency.

A discount does not make unwanted items useful.

Create an Acquisition Verification Card for Every Skin

Use one card per hero when Version 1.7.3 goes live. The card should include the official costume name, source page, start date, end date, claim deadline, required missions, currency, price, region, and ownership confirmation. Add a screenshot of the rule page rather than relying on memory.

For an event skin, track daily and one-time progress separately. For a store skin, record whether it can be purchased alone and whether a displayed discount depends on owning another item. For a pass skin, identify the required level and whether paid rewards unlock retroactively. For a ranking skin, write the exact bracket and recognize that it is not guaranteed.

This six-card method prevents one hero's acquisition rule from being copied onto another. It also makes regional differences visible.

Allocate One Version-Wide Cosmetic Budget

Set a single maximum for all Version 1.7.3 cosmetics, then divide it by priority rather than setting a fresh budget every time a new offer opens. Reserve the largest share for the primary skin, a smaller share for a secondary favorite, and leave a contingency amount unassigned until every route is visible.

If a desired skin can be earned for free, move its reserved paid amount back into the contingency instead of automatically spending it elsewhere. If a bundle exceeds the remaining version budget, skip it or replace a lower priority item; do not quietly increase the total.

Include taxes, platform conversion, and leftover premium currency in the calculation. A package that leaves unusable currency can cost more than the skin's displayed amount suggests.

Compare Account-Wide Value, Not Six Isolated Designs

The six heroes may compete with progression purchases, recruitment plans, and cosmetics from later updates. Rank the skin against all current account goals. A costume for a favorite core hero can outrank a small material bundle, while several low-use costumes may fall below one important hero investment.

Ask whether the skin improves daily enjoyment, profile identity, or collection goals enough to replace another purchase. Avoid using sunk cost: money already spent on a hero or prior skin does not make the next cosmetic cheaper.

Perform a Two-Week Wardrobe Review

Two weeks after acquisition, capture the equipped skin for each of the six heroes and compare it with the original plan. Record matches used, profile display time, and whether another costume replaced it. Give each purchase a result: primary, rotating, collection-only, or regretted.

Before the next cosmetic update, review these outcomes. If the account accumulated several collection-only items without intending to collect, reduce the next budget. If one frequently used skin created lasting value, prioritize similar high-use purchases.

Launch-Day Audit

After 1.7.3 opens:

Confirm all six cosmetics in the client.
Record official names.
Record acquisition routes and deadlines.
Check regional differences.
Preview battle models.
Review owned alternatives.
Calculate free and earned progress.
Set a total paid budget.
Prioritize no more than the number the budget supports.
Save receipts and claim confirmations.

Avoid Regional Assumptions

A costume promotion on one regional account may have different dates or methods elsewhere. Check the in-game event center and official regional channels.

Do not use another region's price or currency conversion as a promise. If the same skin appears through different publishing systems, state the region clearly.

Track Real Use After Acquisition

For two weeks after obtaining a skin, record whether it remains equipped. If the player returns to the old costume quickly, note why: effects, portrait, model visibility, or simple preference.

Use that history for later purchases. An account that repeatedly abandons cosmetics after a few days should adopt a longer waiting period.

Free skins should also be reviewed. Claiming them is useful, but upgrading or buying accessories for an unused hero may not be.

Common Mistakes

Treating Previewed Acquisition as Final

Use the live client for exact free, earned, or paid routes.

Buying All Six Without a Total Budget

Small individual purchases can create a large combined cost.

Ignoring Hero Usage

A beautiful skin has limited practical exposure on an unused hero.

Assuming New Effects

Confirm animations and effects in the item description.

Confusing Collection With Value

Collection is a valid goal, but it needs its own budget.

Final Recommendation

The Version 1.7.3 cosmetic lineup offers variety, but players should not rank or purchase the six skins from preview art alone. Confirm acquisition routes, compare recent hero usage, inspect battle-scale visibility, check wardrobe overlap, and set one total budget.

Prioritize the skin that will be equipped most often, not the one with the loudest announcement. Claim guaranteed options, calculate earned routes, and wait for the live client before paying.