When a game will not work and you are not sure whom to ask, writing the inquiry can become the first obstacle. You bought it on Steam, so Steam may seem like the obvious destination. But the problem might belong with the developer instead. The useful first step is not to guess the cause; it is to decide whom to contact and describe what happened.
The puzzle game below, version 1.2.0, three outcomes, and inquiry text are all fictional examples. No real game was run, and no message or file was sent to a support team. The official paths discussed here come from public guidance by Steam, Factorio, and Larian, while the rewritten inquiry stays within this imagined scene.
Buying it on Steam does not decide whom to contact
The developer is unspecified in this fictional case, and no inquiry has been sent.
Valve's official guidance says to contact Steam Support directly about problems with games developed by Valve. Steam Support also covers Steam account and purchase issues, errors that prevent the game from starting and appear in a Steam dialog box, and authentication or CD-key errors after the game has loaded. For bugs or unexpected behavior inside a third-party game after it has loaded, contact the developer or publisher unless the problem concerns Steam authentication or a CD key. Steam's third-party game support guide
The same guide explains how to find a developer's contact details through the game's support entry in your Library. If you cannot find a third-party support contact, you can ask Steam Support for that information.
In a real inquiry, include the game's name. A game-specific forum may understand the context without it, but a channel handling several games may not know which one you mean. If there is no error code, do not turn an unchanged screen into a server error. Do not invent a message; describe the scene you actually have.
Questions split even inside an official forum
This fictional example separates the two questions; it does not imply that one conversation is automatically forwarded to the other.
Factorio's Help page sends bug and crash reports to the bug-report section of its official forum, while people asking about gameplay or how to use the game are directed to an area where other players can help. Its contact page lists bug reports, game help, and ideas and suggestions separately as well. Even after you find a technical support address, read the guidance about what belongs there. Factorio Help · Factorio's official contact routes
A 2023 developer-forum announcement from Larian directed Baldur's Gate 3 problems and bugs to the support team, while the relevant forum section was for players to discuss help and workarounds. This is an example of how those roles were separated at that time. It is not evidence about response times or every current intake policy. Larian's bug-report guidance
Public discussion and an official support channel therefore call for different questions. You can ask other players, “Has anyone seen the same screen?” You can ask the developer, “Is this behavior intended?” Neither question requires assuming that the recipient has read an earlier conversation.
A title should capture the scene, not guess the cause
Version 1.2.0 was chosen for this example.
The fictional inquiry starts with the title “The game is broken,” followed by: “It will not move to the next one. Is this a bug? Please fix it quickly.” Changing the tone to “I request prompt action” does not give the recipient any more information about the scene. Add the location and the action to the title first.
Factorio's bug-report guidance asks people to put the version in which the problem occurred and the context in the title. The guidance was first posted on May 16, 2014; it is not a single format used across Steam. Factorio's bug-report guidance
In this article's fictional scene, the player selects puzzle three from the puzzle list, completes all the pieces, and then presses the Next Puzzle button on the results screen. The results screen remains. The button's name is the basis for expecting the next puzzle to open. We did not check whether the instructions required a separate setup step, so that detail is not presented as a cause or a rule.
The observation stays narrow. The music continues and the cursor moves, but we do not know whether other buttons responded or how long the player waited. So the inquiry says “the results screen remained after I pressed the button,” not “the whole game froze.” The input device and the actual game name are also unspecified in this fictional case.
Count attempts, and leave unknowns unknown
These three outcomes are fictional examples, not a measured error rate.
In this example, the same interaction path is followed three times. The results screen remained twice, and the next puzzle opened once. We do not set an order for which attempt produced which result. The two-out-of-three count is a fictional condition for explaining the distinction, not a result of an actual test.
That is why the inquiry does not say “It never works.” Having one attempt move forward distinguishes a problem that never opens the next screen from a problem whose result changes even when the same action is used. Turning this small fictional count into a percentage or a game-wide failure probability would change its scope.
A conscientious inquiry does not require more attempts. If you experienced something once and stopped, report that one experience. If you checked anything else, pair each action with its result; leave unmeasured waiting time and environmental conditions blank.
Attach only what the scene needs; keep the inquiry short
The inquiry and diagram below are not a message sent or a file collected in practice.
A screenshot of the results screen may show the button name and the screen that remained. By itself, it cannot show whether the screenshot was taken before or after the button was pressed, or how long anyone waited. If you attach several images, state their order and the action between them. The actual attachment requirements are something to check in the destination's guidance.
Even if a fictional screen shows a messenger notification or someone else's name, that is not evidence about the puzzle button. Steam's Online Conduct Rules prohibit exposing personal information, harassment and spam, and the inappropriate collection or distribution of other people's information. Steam Online Conduct Rules
The official Factorio Wiki explains that logs include the session date and time, the updater's login name, and some full file paths, and that they are usually not sensitive. This describes the general information listed by the document; it is not the result of inspecting a reader's files. This article does not set out a procedure for creating logs or deleting and masking personal files. Information covered in Factorio's log documentation
> In example version 1.2.0, the results screen remains after I press the Next Puzzle button. I selected puzzle three from the puzzle list, completed all the pieces, and then pressed Next Puzzle on the results screen. Across three example attempts using the same interaction path, the results screen remained twice and the next puzzle opened once. When the screen remained, the music continued and the cursor moved. I did not check whether other buttons responded or how long I waited. I expected the next puzzle to open, but I do not know whether a separate setup step was required. Was this behavior intended? If not, what additional information would help?
The game name and device are not specified in the example. Check what the actual destination asks you to enter and attach. This short inquiry is not a report ready to post about a real game; it is an example that puts the observation, expectation, and unknowns in one place.
Similar titles are only the start of a comparison
This is a hypothetical comparison, not evidence that an identical report was found.
Finding a title such as “The Next button does not work” does not make a button on a login screen and one on a puzzle results screen the same scene. Factorio's bug-report guidance also asks people to add to an existing report only when they have found a definitely matching problem. Do not rewrite your own path and result to fit an earlier post just because the title sounds similar.
Conditions that are missing from the body can remain questions. For example: “Did it also happen when you selected it directly from the list?” Do not turn the number of “me too” replies into the number of people affected by the same bug, or expand one person's steps into a claim that everyone had no problem. Keep only what the post and its comments actually establish.
When someone asks a follow-up question, fill in the requested detail instead of pasting the entire first post again. If they ask whether you went through the puzzle list, answer that you selected puzzle three directly. If they ask how long you waited and you did not measure it, say so. Add the conditions to anything checked later; do not merge separate scenes into one result.
Seeing the same screen, investigating the cause, planning a fix, and completing a fix are different statements. Silence does not prove that you were ignored or that the issue is not a bug. A plan does not promise a fix or a date. Keeping those distinctions intact leaves both the information needed for the first question and the information that is still unknown.