Plain Game Answers

How to play Plain Game

Plain Game is a daily estimation game. You get seven targets and 30 seconds for each. Name something close to the target, or estimate the number, and the plane climbs when you are close.

Everyone receives the same daily flight. Guest play does not need an account.

Closer estimates fly higher

In Plain Game, you score by getting close to a target. Check whether the question asks for a number or for something close to that number.

Estimate the scale, then refine it

Start with a rough range and check the units. Confusing thousands with millions, or one measurement unit with another, can matter more than small differences between two nearby guesses.

Use the archived target to review your estimate once it is published. The official archive normally arrives after the day of play.

Find the right Plain Game answers for your flight

Plain Game answers on this page refer to the daily estimation flight at plaingame.app. Begin by checking the date and the wording of the target. The answer can be a number, a named object with a relevant measurement, or a closest listed match. Those forms are not interchangeable. A name that works for a mountain-height question cannot be entered as a numerical estimate unless the question actually requests a number.

The current panel distinguishes hints from published answers. If the archive has not released the flight you are playing, read the general method below and return after publication to review it. Earlier targets are useful practice, but they remain attached to their original dates. An old answer should not be relabelled as today's solution just because it concerns the same topic. The full wording and the target value identify the question more reliably than a broad category name.

Identify the kind of estimate before doing arithmetic

First determine whether you are estimating a value or naming something near a value supplied by the game. These tasks reverse the direction of your reasoning. For a numerical question, you begin with an object and estimate its size, age, length or other property. For a named-answer question, you begin with a target measurement and search for an object whose known property is close to that measurement.

In a hypothetical numerical exercise, you might estimate how many seats are in a small venue. In a named-answer exercise, you might be asked to choose a venue near a specified capacity. The first invites a calculation from rows and seats; the second invites comparison among venues you recognise. These are teaching examples, not current Plain Game targets. Identifying the task correctly prevents you from spending the timer producing an answer in the wrong format.

Build an estimate around a familiar reference

A reference is a quantity you can picture well enough to use as a starting point. For length, you might imagine a familiar room or sports field. For duration, you might compare with a day, a year or a generation. The reference need not be exact to help distinguish a small answer from a very large one. Its purpose is to put your guess in the right order of magnitude before you worry about fine adjustments.

Suppose a practice question asks for the approximate area of a rectangular space. Estimating its length and width separately can be easier than guessing the area directly. Multiplying two rough dimensions gives a defensible starting figure. If each dimension is uncertain, remember that the final area is uncertain too. A calculation does not become precise merely because you used multiplication. Choose a sensible rounded estimate rather than adding extra digits that your initial assumptions cannot support.

Check units and powers of ten

A unit mismatch can overwhelm an otherwise reasonable estimate. Before submitting, identify whether the target uses metres or kilometres, seconds or minutes, individual units or thousands. Read any unit shown next to the answer field as part of the question. If you mentally calculated in another unit, convert deliberately rather than hoping the game will interpret the number as you intended.

A useful final check is to say the answer in words. Two thousand metres and two thousand kilometres describe radically different scales even though the typed number is the same. Likewise, confusing a million with a billion changes the estimate by a factor of a thousand. This check takes little time and catches errors that no amount of refining the last digit can repair. In estimation games, getting the scale right is often the most valuable improvement available.

Use a plausible range before choosing one number

Instead of asking for the exact answer immediately, ask what would definitely be too small and what would definitely be too large. These bounds turn a vague question into a more manageable interval. You can then choose a point inside the interval based on the strongest clue you have. A range is especially useful when your knowledge comes from a comparison rather than from remembering a published figure.

For a practice example, imagine estimating the number of objects in several similar containers. Estimate one container first, then multiply by the count of containers. If one could hold roughly eight to twelve objects and there are five containers, a total around fifty has a clear rationale. This does not describe a current puzzle or its scoring. It shows how breaking a target into smaller parts can produce a reasonable estimate from limited information.

Choosing a named answer near a target

When Plain Game requests a name, produce a small set of candidates before deciding. Start with something whose relevant measurement you know approximately, then consider whether another familiar example lies closer to the target. The goal is numerical proximity, so an unusual name is not automatically valuable. This differs from rare-answer games, where a less obvious correct response may receive a larger reward simply for being less common.

Use the game's selection interface to confirm the intended item when several names are similar. A city, mountain, structure or other object can have alternate names, and related objects can share part of a name. Choosing a listed candidate is more reliable than assuming that a loosely related phrase will map to the exact object in your head. If your intended answer is absent, reconsider the available options rather than treating an unsupported name as a guaranteed match.

Review the reference value separately from the final score

The archive can help explain how close a guess was to a target, but closeness and final displayed altitude are not necessarily identical numbers. The current game describes additional scoring factors beyond the basic estimate. When analysing your result, start by comparing the reference measurement and your guess. That comparison answers the simplest question: how well did you estimate the quantity itself?

Avoid reverse-engineering an exact scoring formula from a single result unless the game explicitly supplies that formula. Two rounds can differ in timing or other conditions, making the final totals a poor basis for a universal rule. For learning, the most transferable information is often the direction and size of your estimation error. Was the guess too high because you imagined the wrong unit, or too low because you forgot part of the object being measured?

Make a short estimation notebook

After a flight, record one target you found difficult, your estimate, the published reference and the assumption that mattered most. A short note is enough. For example, you might discover that you estimated a whole object from only one visible portion, or relied on a comparison that was much smaller than you remembered. The point is to improve the comparison, not to accumulate a list of disconnected answers.

On a later day, try the same reasoning before looking at your note. If you can reconstruct the scale, you have learned more than a number. This method works across heights, lengths, durations and other quantities because it trains the process of choosing references and checking units. It also makes the archive useful after the daily competition is over. A completed flight becomes material for practising estimation rather than a page you visit only to reveal a solution.

When a Plain Game answer looks wrong

Check the original date, complete prompt, target unit and named object before reporting a discrepancy. A numeric target and the closest listed named answer can legitimately have different values. Similarly, a measurement can depend on a definition or a source edition. Preserve the wording supplied by the puzzle so that the comparison remains specific. Removing the unit or qualifier can change the meaning of the question.

If the answer is unavailable, the guide should say so. If it is available but differs from your flight, include the details above in a correction report. That makes it possible to distinguish a source issue from a date mismatch. In the meantime, the estimation exercises here remain useful without claiming to replace a missing official target. They are practice methods, clearly separate from the dated answers in the reveal panel.

About this guide

If today's answers are not available yet, you can still use the hints.