Discover experimental and AI-assisted games

Three routes to discovery

1. Browse a game catalog. Summer Games lists games by genre and other tags. Open a listing that matches your interests and inspect its current play options. Catalog presence alone does not establish AI provenance.
2. Use a specific filter. The itch.io AI tag page exposes AI-assistance filters including graphics, audio, text and code. These help narrow candidates, but read each creator’s account before describing its production.
3. Explore a jam. itch.io’s game jam directory lists hosted jams and their rules. Open a jam’s submissions and individual project pages. Jam participation by itself does not prove a particular entry used AI.

Follow a candidate to its source

Read the game page and the creator’s development log. Write down the exact claim, the date and a link. A statement that a model helped make artwork is different from a statement that dialogue is generated during play. If you cannot find a specific statement, label the game’s AI use unknown.

Check whether the version offered is a prototype, demo or full release. Confirm the current price and device before downloading or inviting a group. A jam page can remain online after its rules and submission window have ended, so check the dates.

Make a useful shortlist

Keep three candidates: one that fits your usual genre, one with an unfamiliar mechanic and one whose creator clearly documents the experiment. Record the platform, cost, session length if stated, source and the question you want the game to answer. This is an editorial discovery exercise, not a claim that any particular game has been tested.

Play a short session, write one observation about the interaction and check whether the game asks for a connection or account. If a build will not run on your device, mark that as untested rather than judging the game from screenshots.

Common questions

Does an AI-themed jam verify every entry?

No. The jam’s theme and rules describe the event. An entry needs its own evidence for the specific use claimed.

Where can I make an experiment?

Summer Engine describes an agent-assisted 2D and 3D creation workflow. Choose a small idea and document the tools and steps you actually use.

Worked route: from a jam to a candidate

Suppose you want an experimental game with an unusual dialogue mechanic. Open the itch.io jam directory and read an event’s theme, rules and submission dates. Then open its entries and select a project whose description mentions dialogue. The theme tells you why it caught your attention; it does not establish that the individual project uses a model.

On the entry page, look for a creator’s explanation of the interaction and its implementation. If the page says dialogue was written in advance, that may still be an interesting experiment, but do not describe it as generated during play. If the page says a model assisted the writing, record that limited development claim. If it says nothing, write “unknown.” Follow links to a development log when provided, and note the version and date of the statement.

Next check whether the available build matches your device and whether the entry is complete or a prototype. Try the controls and make one choice. Note what happened, rather than assuming that every playthrough varies. If the build requires something you cannot provide, retain it as a candidate and mark the interaction untested. This is a hypothetical search procedure, not a reported playtest of a particular entry.

Use tags without over-reading them

The itch.io AI tag page exposes both a general tag and separate assistance filters. Use the general tag to explore broadly. Use a more specific filter when your question concerns graphics, audio, text or code. The filter narrows the search, but its label is not a complete account of a project’s production.

Open promising pages in a short list and compare the creator’s own words. A game about a fictional AI character might appear in a broad AI search without using generative technology. Conversely, a creator might use assistance during development without making that the game’s subject. Neither case tells you whether the game is enjoyable.

For player-first discovery, start with a genre or session preference on Summer Games. Treat any AI connection as unknown unless a relevant primary source supports it. A listing can answer what the creator or store currently offers; the actual build still needs your own device check.

Build a small research trail

1. Candidate: record the name, creator and official project page. Avoid copying a third-party description without tracing it.
2. Question: write what you want to know, such as “Does the game generate dialogue during play?” This prevents a general AI label from becoming an answer to a narrower question.
3. Claim: record the creator’s specific statement and link, with the date you checked it. Distinguish a planned feature from the released version.
4. Access: note current price, platform, controls and whether you found a demo or full build. If the page does not say, leave the field unknown.
5. Observation: after playing, record the build, device and what happened. Keep this separate from the source’s claim.

A useful shortlist can include projects with unknown provenance, provided the label is visible. The shortlist should not describe those projects as verified AI-assisted games. If verification is a condition for inclusion, exclude the unknown entries from that particular list until evidence appears.

Compare experiments without assuming a winner

Ask what the creator is trying to explore. One project may test dialogue, another may explore level construction and another may simply document a new creation workflow. Choose a comparison that fits the question: can the player understand the interaction, does the input have a visible consequence, and can the experience be repeated? A prototype can be useful even if it is unfinished, as long as its status is clear.

Record practical constraints as well as interesting ideas. A browser build may need a particular input, and a downloaded build may only support certain operating systems. A free entry may have a paid version or optional payment. Read the current page rather than relying on an old jam list or assuming every entry uses the same distribution terms.

Can a jam’s rules serve as provenance?

Rules explain an event’s requirements, but they are not a detailed audit of each submission. Look for the individual creator’s statement and treat a missing explanation as a gap.

How often should I revisit a candidate?

Recheck when you intend to play, purchase or publish a claim. Prototypes can change, links can move and a later version can differ from the one described in an older post.