About GamesRead

GamesRead is a gaming resource built around one idea: give players accurate, hands-on information without the padding. We cover cheat codes and console commands, game guides and walkthroughs, hardware recommendations, and news from across the industry.

The people who read us range from casual players looking up a quick cheat code to dedicated fans working through every mechanic of a 100-hour RPG. We try to be useful to both.

Who We Are

GamesRead is run by a team of writers and editors who play the games they write about. That’s not a tagline — it’s a working requirement. Before a guide goes live, someone on the team has opened the game, tried the method, and confirmed it works on the platform and version stated in the article.

Our contributors write under pen names and specialise by genre and platform. Some focus on open-world RPGs and sandbox games, others on shooters and competitive titles, and others on hardware and peripherals. That specialisation matters when accuracy depends on knowing how a specific engine handles console input, or which patch broke a previously working command.

How We Write

Guides and walkthroughs are based on direct gameplay. Where that’s not possible — older titles, platform-specific mechanics we can’t reproduce — we cross-reference against the developer’s official documentation, verified community wikis, and multiple independent sources before treating anything as confirmed.

Cheat codes and console commands are the core of what we do, and we treat accuracy here seriously. Every code is verified against the specific game version and platform listed in the article. We cross-check against official sources first — developer patch notes, publisher documentation — then against established community sources like dedicated wikis and verified Reddit threads. A single wrong character in a console command wastes the reader’s time, so we don’t guess.

Hardware coverage draws on manufacturer specifications from official product pages, independent benchmark data from established testing outlets, and hands-on experience where available. When we make a recommendation, it comes with the data behind it — not just a general impression.

News is sourced from official announcements, developer and publisher statements, and established games press. Unverified leaks and rumours are clearly labelled as such. We don’t present speculation as fact.

Editing and Fact-Checking

Every article is reviewed by an editor before publication. The editing pass covers factual accuracy, platform and version consistency, source quality, and whether the piece actually answers the question a reader is likely to have. For cheat code articles specifically, the editor cross-checks commands against at least one independent source before sign-off.

We don’t have a word count minimum. Articles are as long as the topic requires and no longer.

Keeping Content Current

Games get patched. Commands stop working. Hardware gets discontinued. We update articles when the information changes and mark the revision date in the piece. A guide that was accurate six months ago might be wrong today — we’d rather fix it than leave it.

If you find something that’s outdated or broken — a code that no longer works, a guide that doesn’t match the current version — let us know at [email protected] and we’ll look into it.

What We Don’t Do

We don’t publish guides based on unverified community posts without cross-checking. We don’t recommend hardware based on spec sheets alone when independent benchmarks say otherwise. We don’t run advertiser-driven “best of” lists where placement is paid — sponsored content, when it exists, is clearly labelled and kept separate from editorial.

Get in Touch

Editorial corrections and factual feedback: [email protected]

Advertising and partnerships: [email protected]