Contact
One inbox, read by the person who writes the games
Write to contact@mtclab.net. It reaches MTC Lab, the shop that builds Quakedle and the rest of Gamecove, and a person reads it. If you are writing about a particular puzzle, the date and the number at the top of the page are the two things that identify it.
Write to contact@mtclab.net. That address reaches MTC Lab, the shop that builds Gamecove, and there is no support queue or ticket system behind it.
Corrections are the most useful thing you can send
The games are built from public datasets, and public datasets have mistakes in them: a tower with the wrong height, a ship credited to the wrong builder, a lighthouse in the wrong country. If you spot one, tell us which game, which day and what the right answer is. It gets fixed here, and where the mistake is upstream it can be reported to the source as well.
It also helps to say which browser you were using if something looked broken, and to mention if a puzzle felt unfair rather than just hard. Those are different problems and we treat them differently.
Reporting something that looks broken
The useful details are the game, the date or puzzle number shown at the top of the page, your browser, and what you expected to happen instead. A screenshot settles most questions faster than a description does.
It is worth separating two kinds of report, because they get handled differently. A bug is the game doing something it was not built to do: a grid that will not scroll, a guess that is rejected, a page that will not load. An unfair puzzle is the game working as designed but asking something unreasonable, usually because the underlying record is thin or misleading. The first gets a fix; the second usually gets an entry pulled from the calendar.
Suggesting a game
New games are welcome as suggestions, with one condition that decides most of them: there has to be a public, openly licensed dataset with enough entries to run for years without repeating. If you know of one for the subject you have in mind, say so, because that is the part that usually kills an idea.
What we cannot do
We cannot restore a streak. Streaks live in your browser and we never see them, so there is nothing on our side to reset. If you are moving to a new browser or a new device, use the export and import controls on any game’s cookies page before you switch.
We also cannot tell you tomorrow’s answer, which people do ask. The calendars are built in advance, but the whole point of a daily is that everyone finds out on the same morning.