STR Coding Club logo STR Coding ClubLearn to code, together
Games

How Coding Club Members Test Secret Online Game Tips Before Sharing Them

"If you open the chest while jumping, you get better loot." The tip arrived in our club chat with three fire reactions and a screenshot of a rare sword. By the end of the evening, half the members had tried it in the game.

Illustration of a treasure chest on a scale balanced against a tally sheet

"If you open the chest while jumping, you get better loot." The tip arrived in our club chat with three fire reactions and a screenshot of a rare sword. By the end of the evening, half the members had tried it in the game. By the end of the week, we had turned it into a coding exercise, and the tip did not survive.

Secret tips are part of how players bond. People pass them around in voice chat, video comments and group messages, often with real excitement about having found something nobody else knows. A member who tracks where these tips come from keeps a list for the club, covering school friends, streamers, modding forums and pages like ankertoto that get forwarded with a "trust me, this works." The sharing is generous. What is usually missing is a test. Coders are in a good position to supply one.

Why Tips Are Hard to Check by Feel

Most secret tips are about rare events. A rare drop, a critical hit, a lucky spawn. Rare events are exactly where human judgement is weakest. If a drop has a 3 percent chance, a player who tries a tip ten times will usually see no drop at all, and occasionally see one or two. Either result feels meaningful, and neither is.

There is also memory. A player who tries the jumping trick and gets a sword will remember it vividly. The twenty times it did nothing fade. By the time the tip is shared, it has been filtered through that selective memory.

Step One: Turn the Tip Into a Claim

The first thing members do is rewrite the tip as something measurable. "Jumping gives better loot" becomes "the rare item rate when opening while jumping is higher than when standing still." Now there are two groups to compare and a number to count.

This step alone kills a surprising number of tips. Some cannot be made measurable at all, such as "the game likes you more if you play every day." Others turn out to be about a mechanic the developer has openly documented, such as a daily bonus, which is not a secret at all.

Step Two: Build a Model to Practise On

We cannot see inside a commercial game, so members first build a small model. A chest function returns a rare item with 3 percent probability and a common one otherwise. Members add a parameter called jumping which, in the honest version, does nothing.

Then they write the test harness: open 5,000 chests with jumping set to true and 5,000 with it false, and compare the rare rates. In the honest model, the two rates come out close, something like 2.9 percent against 3.1 percent, and the order flips between runs.

Next, a member secretly edits the chest function so that jumping really does raise the rate to 4 percent, and the others run the harness without being told. They can detect it, but only with enough trials. At 200 trials per group the difference is often invisible. At 5,000 it shows up clearly. That is the core lesson: small tests cannot detect small effects.

Step Three: Test the Real Game, Carefully

Armed with this, a few members tested the real tip in the game. They agreed on a protocol beforehand:

  1. Same character, same chest type, same area.
  2. Alternate between jumping and standing for each chest, so time of day and luck streaks affect both groups equally.
  3. Record every result in a shared spreadsheet, including the boring ones.
  4. Stop at a number agreed in advance, not when the results look good.

Point four matters a lot. If you stop the moment the tip looks true, you will "confirm" almost anything.

The Result

ConditionChests openedRare itemsRate
Jumping412133.2 percent
Standing409143.4 percent

No meaningful difference. Members then ran their model with a true 3.3 percent rate for both groups, 410 chests each, a thousand times over, and found that gaps as large as the one above happened in most runs. The jumping tip was noise.

The member who had shared it took it well. He pointed out, fairly, that 410 chests could not rule out a tiny effect. True. But it ruled out the kind of effect the tip promised, and that was enough to stop sharing it as a sure thing.

Where the Usual Attitude Goes Wrong

A common response to tips like this is "it does not hurt to try." Usually that is true, and trying a harmless tip for fun is fine. But it does hurt in two situations. When the tip costs something, such as in game currency, a lot of time, or real money, and when the tip asks you to download a tool or log in somewhere. The second category is how many account thefts start. A real tip never needs your password.

So our rule is: harmless tips, try for fun and report honestly. Costly tips, test before spreading. Tips that need downloads or logins, refuse and warn others.

Sharing Results the Right Way

The last step is telling people. Members write a short post with the claim, the method, the numbers and the conclusion, and they keep the tone friendly. Nobody likes being told their tip was nonsense. "We tested this with 821 chests and could not find a difference" lands better than "this is fake."

Writing up results is good practice in explaining technical work, much like reading and explaining error messages, which we covered in reading an error message without panicking. Members who reused another club's test harness rather than writing their own were encouraged too, since copying code you do not fully understand yet is a normal part of learning, as long as you study it afterwards.

A Habit That Lasts

The jumping chest tip is long forgotten, but the habit stuck. Members now ask "how many tries?" whenever someone shares a trick, in games or anywhere else. For those who enjoy this kind of reasoning, puzzle games are excellent practice, and our list of online game puzzles that secretly teach programming is a good place to start.

BN
Bartholomew Ng

Bartholomew taught maths for years before switching to teaching Python. He writes about the basics of the language and about teaching code without drowning learners in syntax.

More posts by Bartholomew

More in Games

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto