Communication preferences

Understand what a preference controls

Communication settings help you choose which optional updates you receive or how they are presented. Read the exact label before changing a switch. A preference for news is different from the delivery of a support reply, an account notice or an earned reward. Do not assume one toggle has the same effect on every message category.

Start with the kind of communication you want to change. Is it a game announcement, an event update, a support conversation or a mailbox notification? Naming that category helps you find the relevant option and makes a later report much clearer. If the interface does not offer a separate control for it, say that rather than repeatedly changing an unrelated preference.

Record your current selection

Open the preferences panel using your own signed-in account and note the current state. On shared devices, confirm the username first. A screenshot of only the relevant switches can help you compare a later result without exposing private mailbox contents. Keep the visible label with each value so you do not confuse similarly named controls.

Decide the outcome you want before editing. For example, you may want fewer optional announcements while still following an active support ticket. That is a specific goal you can compare with the labels and descriptions. Switching everything off at once may hide which control actually affects the message you care about.

Change and verify one option

Update one preference, use the save action if one is shown, and wait for the interface to finish. Reopen the panel and confirm the displayed value. If a save error appears, record it. If the switch immediately reverts, note that sequence rather than treating the change as successful because you clicked it.

If the value stays correct but a later message seems inconsistent, record the message type and delivery time. Existing messages in your mailbox may remain after a preference changes. A saved setting and an already delivered message describe different events. Include the order of those events before concluding that the setting was ignored.

Keep important conversations easy to follow

For an active support case, check the ticket itself as well as any notification surface you use. A notification can help you notice a reply, but it is not the conversation history. Read the latest response before adding new information so that your reply answers the team's current question.

Do not create another ticket solely because a notification was missed. Open the existing case and continue there when possible. If the issue is that a reply exists but its notification did not appear, report the notification behavior specifically. Include where the reply is visible and where you expected the alert.

Distinguish mailbox state from delivery preferences

Reading, archiving or deleting a message changes how you see that message. A communication preference concerns the category of communication described by the control. These actions should not be treated as interchangeable. Deleting one announcement does not necessarily unsubscribe you from later announcements, and changing a preference does not necessarily remove past mail.

If a reward or support message appears missing, check the relevant mailbox view and filters before assuming a preference removed it. Record the views you inspected. A message present in an archive is different from one that never arrived. Keeping those observations separate helps support investigate the right stage.

Example: an announcement arrives after a setting changed

Suppose you turn off an optional news preference and later notice a news message in the mailbox. Compare the time you saved the preference with the message's displayed time. Check whether it was already present or simply unread. If the message appears to have been delivered afterward, preserve its title, category and time with a screenshot of the saved preference.

Send those details in one report instead of repeatedly switching the option back and forth. A stable setting gives support a useful state to investigate. If the interface shows a different value after refreshing, include that as a separate observation because the save itself may be the failing step.

Make choices for your own account

Communication preferences should reflect how you want to use the service. Do not let another player direct you to disable useful account notices as part of a claimed reward, trade or troubleshooting process. Read the label yourself and use the real account interface. A support conversation should never require you to hand over credentials or silence security messages.

On a shared account or device, clarify who is changing the setting before making assumptions about a reverted value. For support purposes, describe the visible change and the account context without claiming another person caused it unless you know that directly.

Frequently asked preference questions

Why is old mail still visible? A preference change and removal of existing messages are different actions. Check the message time and the control description.

Why did I miss a support reply? Open the ticket and confirm whether the reply exists. Then report the notification surface that did not behave as expected.

Can I turn off every kind of account communication? Use the options actually shown. Do not assume essential notices follow the same preference as optional news.

Should I keep toggling until the next message disappears? Keep one confirmed setting and collect a clear example. Repeated changes make delivery timing harder to interpret.

Review after an intentional change

Revisit a preference after your next ordinary session if you are checking persistence. Keep the value stable in between and note whether another device or account session was used. This gives a later mismatch a useful context.

Contact support with a before-and-after record

Include the exact preference label, old and new values, approximate save time, whether it persisted after reopening and the message that appeared inconsistent. Say whether the problem concerns delivery, unread state, a missing notification or the save action itself. These are distinct behaviors.

Attach focused screenshots with unrelated conversations hidden. Continue in the same ticket if another example appears, and note whether the setting remained stable in between. A small timeline is more useful than a full mailbox export and gives the team a practical way to compare the preference with the observed communication.