> For the complete documentation index, see [llms.txt](https://codingmace.gitbook.io/masterward/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codingmace.gitbook.io/masterward/software/ideas/game-destroyer.md).

# Game Destroyer

## Origin

So, I like to play some mindless games sometimes, and I don't know if it is to feel productive or to just play games to waste time. But maybe I could create a program to go through the tutorial and beat the game. Of course, it would record everything and how to do it but would create the fastest ability to do that and maybe some machine learning. The more games it plays the more strategies it picks up.

## Overview

It would be starting out as a test project and pushing to see how many simple games it can beat. Then I would move on to learning how to beat games faster and ultimately getting a way to test if the tutorials are sufficient enough for someone to learn and posting a result of what is broken in the game through automated testing. Well, more like an overlay running on a computer of the testing with a report but really the same thing.

## Information to consider

There is a software that is openAI that can help with this - Cost money though


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://codingmace.gitbook.io/masterward/software/ideas/game-destroyer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.