Does the emulator open, or is the application missing?
This guide starts after the Lichii window opens. If you cannot launch the program itself, follow Windows, Linux or macOS setup first. A missing shared library or incomplete ZIP is not diagnosed by adding another game folder.
The project README says games, keys and firmware are not included. Downloading the emulator does not create a game library automatically. Use only files you have legally obtained.
Did you add the directory containing your game?
The repository’s inherited Quick Start describes double-clicking the empty main window to add a game directory. Some interface labels still retain Eden wording. Check the directory path you selected rather than assuming a previous emulator’s library list was imported correctly.
Make sure the selected directory exists, the drive is connected and your account can read it. On a removable or external drive, reconnecting can change the mounted location. Revisit the library configuration after moving files.
Do not move or delete the original game file while troubleshooting. Keep one known location and change one thing at a time.
Is it a base game, an update or DLC?
Confirm what the file represents. An update or DLC is not automatically a separate base-game entry. The Quick Start describes game-library setup separately from system-file installation; do not assume every file belongs in the same dialog.
If you are unsure of a file’s identity or integrity, check the method you used to obtain your own copy and the original documentation. The reviewed sources do not justify telling you to rename an arbitrary extension or download replacement files from an unrelated site.
Are required system files configured?
The inherited setup guide lists Tools → Install Decryption Keys and Tools → Install Firmware. Check the options visible in your current build and follow the appropriate dialog with your legally obtained files. Do not use a game-directory chooser as a replacement for these setup steps.
Record any exact error text. A missing key, failed firmware import and unreadable game file are distinct problems. A generic “it does not work” report makes them difficult to separate.
What if the entry appears but launching fails?
At that point the library-recognition task is complete and you have a different symptom. Record the build, game version, OS, GPU and driver. For Ocarina of Time, use its compatibility guide and, if the intro runs before a failure, the crash-after-intro guide.
If the entry appears but is slow or visually incorrect, follow low FPS or graphics and audio. Keep your previous settings and back up existing data before a build change.