About
What CS Kaiyuan Game is for, who writes it, how claims are checked, and where to write when we get something wrong.
What you are looking at is a working blog. Old pieces stay up in the archive rather than quietly disappearing, including the ones that have aged badly.
This site grew out of a spreadsheet. Kai Denton had been tracking the subject for years, mostly to stop repeating the same mistakes, and it turned out other people wanted the same answers.
There is no house byline here. Each piece is signed, and each signature leads to everything else that person has put their name to.
Kai Denton, CS2 strategy and tactics writer. Kai has played Counter-Strike competitively since the early CS:GO days and spent years breaking down how professional teams approach the game. He writes about tactics, economy and the decisions that separate average players from those who consistently rank up.
Mira Ashford, Esports and competitive gaming writer. Mira covers the competitive gaming scene with a focus on CS2, from tier-one tournaments to the mechanics that make the game worth watching. She is interested in what esports reveals about teamwork, pressure and preparation.
Jake Solis, Gear and hardware reviewer. Jake tests mice, monitors, headsets and peripherals with a single question in mind: does this actually make you play better? He approaches gear reviews from a player perspective rather than a spec sheet.
Articles are filed under one topic each, so an archive page reads as a list rather than a pile. Most of the traffic here lands on strategy, guides and gear.
There are questions we routinely decline. Anything that depends on facts only you can see, and anything where being wrong would cost you real money on our say so.
We would rather publish six pages we can defend than sixty that read well. That is why the archive grows slowly.
Nobody has editorial input except the people whose names are on the articles. That includes anyone who has ever sent us money.
How claims get checked and how money is disclosed is written down separately, on the editorial policy page.
Tell us which line is wrong and why, at [email protected] or through the contact page. Small errors are corrected the same week. Anything that changes the advice gets a dated note at the bottom of the article.
