Australia Gaming Radar

The Australia Gaming Radar editorial team

Good guidance depends on clear roles, careful reading and an honest account of what has—and has not—been checked. Our editorial work turns public game information into practical context for people choosing what to play, while keeping provider claims distinct from our own observations and preferences.

Editorial roles at the guide

Our work is organised around three complementary responsibilities. These are descriptions of the roles that shape this guide, not biographies of named individuals or claims about personal qualifications. The aim is to make clear who handles each kind of editorial task and how a reader’s question can enter the process.

Game information editor

The game information editor checks the features described in publicly available provider material. That includes reading product pages and help information closely, noting the context around a stated feature and checking that our summary does not imply more than the provider has said. When details differ between public sources, the wording stays careful rather than presenting one description as universal.

This role also separates a feature description from a recommendation. A listed mode, setting or access option may help a reader decide what to investigate, but it does not by itself establish that a game will suit every person or device.

Beginner guide editor

The beginner guide editor explains what a new player may want to learn before starting. Guides aim to make unfamiliar terms, setup steps and common decisions easier to follow, with plain language and useful context rather than assumed expertise. Where a process can vary by game or provider, the guide says so and encourages readers to check the current in-game or provider instructions.

The role is to make an explanation approachable without promising a particular outcome. Reader preferences, available time, accessibility needs and experience all differ, so guidance should help people ask better questions rather than tell them what they must enjoy.

Reader enquiries editor

The reader enquiries editor reviews correction requests, questions about a page and reports that information may have changed. A useful report identifies the page and the passage in question, then points to a public source when one is available. This gives the editorial team something concrete to assess and helps distinguish a factual correction from a difference in taste.

Enquiries are considered for clarity and relevance to the guide. Sending a message does not guarantee a particular change, but specific, courteous feedback can help us identify material that deserves another look.

From provider information to reader guidance

Our editorial handoff begins with public information about a game or service. We gather the relevant provider descriptions and guidance, then check whether the sources agree on the point we plan to explain. If information is incomplete, time-sensitive or described differently in separate places, the copy should retain that limitation instead of smoothing it into a certainty.

Read, check and explain

Next, the material is reviewed for internal consistency. Names, feature descriptions and the relationships between details are checked across the available sources. A sentence that could be read as a guarantee is narrowed to match the evidence. This is a practical editorial check, not a claim that every game, setting or update has been exhaustively tested hands-on.

Editors then shape the checked information into plain-language guidance. We distinguish provider-stated facts from editorial preferences and explain when a point is general advice rather than a rule that applies to every title. The result should help readers compare their own needs with the information available, without making the decision for them.

Keep pages useful over time

Game details and provider instructions can change. Reader reports may flag a changed feature, a broken explanation or a new ambiguity. The enquiries role assesses those reports, and relevant information can be checked again before a page is revised. We do not describe this process as continuous monitoring or exhaustive coverage; it is a reasoned editorial response to information available to the guide.

Corrections are most useful when they identify the page, explain what appears inaccurate and include a source readers can inspect. A preference or personal experience is welcome as context, but it is not the same as independent confirmation. Keeping those categories separate lets us make updates more precisely and communicate their limits honestly.

Reach the editorial team

For a correction, a question about our explanations or feedback on a guide, use our contact page. Please name the relevant page and passage so the enquiry can be reviewed in context. A public provider page or help article can be useful evidence when the question concerns a published feature or instruction.

The contact channels supplied for the site are [email protected] and +61 2 5555 0946. These are site contact details; they are not a direct line to a game publisher. For an account, purchase, technical fault or other service-specific issue, contact the relevant game or service provider through its own official support channel. The editorial team cannot act on a provider’s behalf or resolve a player account issue.

When you write, share only the details needed to explain the question. We review messages as editorial enquiries and use the information to understand the reported issue; avoid including passwords, payment details or other sensitive account information. A message is an invitation for review, not a promise that a page will change or that an external provider will respond.