VALOSTRIKE

Missions and rewards

Daily missions, XP and what arrives in your mailbox.

6 min read 1,254 words VALOSTRIKE Player Support

Contents · 14 sections

Read the objective before starting

Mission descriptions define what progress is expected. Check the mission name, goal, current counter and any timing shown in the interface. Similar-looking objectives may track different actions, so do not infer completion from a single match result alone. Start by taking note of the counter before playing. Comparing a before and after value for the same mission is more useful than remembering that a reward should have arrived at some point during a long session.

Distinguish progress from payment

A progress counter, a completed objective and a delivered reward are separate pieces of information. Reaching a visible target does not prove that every later stage has already finished. If a reward is expected, inspect the mission description and the relevant delivery area rather than repeatedly pressing unrelated buttons. Explain the exact stage that appears wrong in a support ticket: the action did not count, the goal appears complete without a result, or a delivered item cannot be found.

Check the current mission period

Daily objectives can change between periods. Record the mission name and the date when comparing screenshots, especially if your session crossed a refresh. A new objective with a lower counter is different from an old objective losing progress. Use the timer displayed by the current game rather than guessing the reset from your device clock. Time zones and a session continuing across a boundary can make an otherwise normal change look surprising.

Find the reward in the correct place

Read whether the objective refers to XP, account currency or an item. Check the relevant balance or inventory category. The in-game mailbox can also contain reward messages; inspect the message itself and any available claim action. Merely opening a message is not the same as claiming an attached reward. If the mail has an expiry, follow the information shown there. Do not assume that every mission uses identical delivery behavior.

Understand website snapshots

The website displays game information that may not reflect the latest moment in your session. Compare the in-game mission and balance first, then check the website's synchronization information where available. Refreshing a webpage cannot force a game reward to be paid. If the game is correct but the website is behind, describe that as a display or synchronization issue. This helps prevent an unnecessary correction to a reward that was already granted.

Keep useful evidence

When something appears wrong, preserve the objective, counter, expected reward and current result. If you already have a match identifier or screenshot, include it. Approximate times are acceptable when clearly labeled as estimates. Do not recreate a problem by intentionally leaving matches or interfering with teammates. A short account of normal play can still be investigated, while an artificial test during a live match may introduce unrelated complications.

Work through a missing-progress example

Suppose an objective tracks wins and its counter appears unchanged after a match you believe was won. Confirm you are reading the same objective, record the match or approximate time and check whether the in-game result has settled. Compare the counter in the game with the website separately. Explain what makes you believe the win qualifies, without presenting an assumption as confirmed fact. Support can then distinguish a qualification question from a counter or synchronization defect.

Avoid duplicate claims and resets

Do not keep retrying a reward action rapidly or ask several people to change the same record. Repeated attempts make it harder to reconstruct which action produced the final balance. Do not reset your profile or mission data as a troubleshooting experiment. Such changes are not required to report a missing reward and could remove useful evidence. Keep the existing state intact until the team has established what, if anything, needs correcting.

Frequently asked questions

If a mission changed overnight, compare its name and displayed period before treating the new counter as lost progress. If XP changed but another expected item did not, report the individual missing component. If a mailbox reward shows as claimed, check the relevant balance rather than assuming the message itself is the item. If you are unsure what an objective requires, send its exact wording and ask for clarification; a screenshot of the objective is better than a paraphrase.

Contact support with a complete timeline

Choose Gameplay & bugs for progress tracking, or Purchases & items when a paid transaction is involved. Include the mission name, period, before and after counters, match time, expected reward and what you see now. State whether the problem is in-game, on the website or both. Support must review available records before confirming an adjustment. A ticket does not itself grant XP, reset payout history or guarantee that an additional reward is owed.

Track one mission from start to finish

Read the objective before entering a match and note the displayed progress. Identify whether the requirement concerns an action, a match outcome or a particular context. Then play normally and compare the mission panel again at an appropriate stopping point. A remembered action and a recorded mission increment are different observations, so write down both if they disagree. Avoid abandoning a team objective merely to force a counter to change.

If you are close to a reset, include that context in your notes. A mission displayed before a refresh may not be the same task shown afterward. Capture the wording, progress and approximate time together. The title alone can be insufficient when similar missions have different requirements. Do not assume that another player's mission or reward proves what your account should receive.

Distinguish progress, completion and delivery

A mission can have visible progress, a completed objective and a separate reward state. Follow the interface through each stage instead of treating one changed number as proof that every step finished. If there is a claim action, read its label and confirm the resulting state. If a mailbox message contains the reward, inspect that specific message rather than repeatedly reopening unrelated mail.

When something is missing, identify the last state you confirmed. “The objective reached its target, but no reward message appeared” is different from “the action did not increase progress.” Include the mission wording and relevant timestamps so support can investigate the correct stage. Repeatedly pressing a claim control can make the sequence harder to reconstruct and should not be used as the main diagnostic method.

Keep reward records organized

For a reward concern, keep the mission screenshot, relevant mailbox entry and resulting inventory view together. Label each with the time you checked it. If an item has variants or an upgrade state, specify which version you expected. An item appearing under a different view is a different problem from a reward not being delivered at all.

You do not need to expose unrelated mail, private conversations or full account history to demonstrate one missing reward. Crop the evidence to the relevant entries while keeping the mission or message identity readable. A concise record helps support connect the reported action with its expected result without sorting through an entire account archive.

Frequently asked reward questions

Does completing a mission always mean an item arrives by mail? Read the reward shown on the actual mission. Some rewards concern account progress, and the required action can differ. Report what that mission promised, rather than assuming every completion uses the same delivery route.

What if progress changes after I rejoin? Note the value before leaving and after returning. A temporary display mismatch and lost account progress need different checks. Include whether the game and website show the same result.

Back to the article contents ↑

Still need help with this topic?

Send the team a private ticket. Include what happened and the steps you have already tried so we can continue from here.

Contact support