THE PORTAL · COMMUNITY GUIDELINES
What goes on the shelf
14 November 2026
Make something for the UNC 64. Make sure it's yours to share. Say what it is. Be decent to each other. However you made it, by hand, with a friend, or with an AI, it's welcome.
What belongs here
Anything that runs on a UNC 16 or a UNC 64: games, demos, music, tools, type-ins, a routine you're proud of, an experiment that only half works. Small is good. Unfinished is fine, if you say so. Ten lines of BASIC sit on the same shelf as ten thousand of assembly.
AI is welcome
You can submit a cassette you wrote with an AI's help, or one an AI wrote and you only asked for. It goes on the same shelf, under the same rules, as one typed in by hand. You don't have to label it. If you'd like to say how it was made, the line about it is a good place: people are curious, and it's interesting either way.
Two things stay the same whoever did the typing. It has to run on the machine. And it's yours: you answer for what you send in, including that it's yours to share.
UNC 64 isn't against AI. The project is built with it, and the manual is published in a form made for AI agents to read (llms.txt). What the game offers is somewhere without it: a desk in 1984, where the only help is a ring binder. Both are true, and the note on AI says why.
Yours to share
- Submit your own work, or work you have permission to pass on. If you built on someone's cassette, say whose.
- An old idea done your way is the tradition: a snake is a snake. Another game's name, characters, pictures or music are not yours to put on a tape.
- It stays yours. By submitting, you let UNC 64 keep the cassette on the Portal and let people download it and play it: here, in the Machine Room and in the game. Ask, and it comes down.
- Source is optional and very welcome. A cassette with its source is one anyone can open in the Machine Room and learn from, which is how most of us learned. If it lives in a GitHub repository of yours, give the link instead, or as well: Read the source on the cassette's page leads there, and otherwise to the files the cassette carries. If you want it reused on particular terms, put a line or a
README.mdon the cassette saying so.
Say what it is
- A title, who it's by, a line about it, the keys, and how to play if that isn't plain from the screen. The Submit page has a box for each, and they travel on the cassette, with up to four screenshots and your cover art if you've made some.
- What it needs: 16K or 64K, and the NIECE if it uses her. A cassette that asks for less than it needs shows a blank screen to someone, and they won't know why.
- Don't pass one thing off as another, or as somebody else's.
Be decent
The shelf is for everyone, including the twelve-year-old this would have been for in 1984. No hate, no harassment, nothing sexual, nothing aimed at a real person. Jokes are welcome; cruelty isn't. The same goes for titles, labels and the lines about them.
The cassette itself
- A
.unc.pngin the cassette format, version 1, with a tape that loads. The Submit page makes one from a.tap, a.sor a.bas, and checks it by loading it. - One megabyte at most. A title of 40 characters or fewer.
- The face is a picture of a cassette, in a cassette's proportions. Draw your own label if you like: it's a PNG, and the program rides in its own chunk. Keep it a face people would want on a shelf.
- A cassette can't reach your computer. It's a program for an emulated 8-bit machine with 64K and no way out of it, so there's nothing to scan for. The worst a tape can do is jam the processor, and the RESET button is on the case.
How it's looked at
A person looks at every cassette before it goes on the shelf, usually within a few days: that it loads, that it's what it says, that it keeps to this page. You may get a question. An update is a submission like the first: send the new cassette and say which one it replaces.
If something on the shelf shouldn't be there, or is yours and you didn't send it, write to unc@viljami.io or say so on the Discord. It comes down first and gets discussed second.