Core archive size: 1.70TB (ZStandard)
Supplementary archive size: 269GB (ZStandard)
update cadence: when new content is released and tested
🌐TP Game Notes quick link
Curated by Eggman.
Welcome to my mega-mighty TeknoParrot Collection — a cleaned, organized, collector-focused RomVault set built around the TeknoParrot ecosystem. This project exists to take arcade game backups and turn them into something more consistent, more manageable, and a lot less irritating to maintain and utilize for original game owners.
I am unaffiliated with TeknoParrot, and I do not do outreach or support. Do not send me messages about issues you're having with TP setup or games. Take it up with the TP devs and community in their Discord channels.
- What Is TeknoParrot?
- Project Overview
- What This Collection Is Trying to Do
- Why There Are Two DATs
- Why RomVault Only?
- Eggman's TeknoParrot Game Notes
- About TPUI's ROM Scanner
- How to Store Your Games
- Rebuilding Tips for Nested ZIPs
- Antivirus False Positives
- Why Other Versions May Be Missing
- Game Not Working?
- Intel, AMD, or NVIDIA?
- BepInEx and Other Modding Frameworks
- FPS Frame Limiting
- Why Some Games Need Admin Mode
- Testing and Cleaning Standards
- File Naming Standard
- Additional Resources
- Where to Find Content
- Are You a TP Dev?
- I Do This for Fun, Not for Profit
- Licensing
- Support
TeknoParrot (also known as TeknoParrot User Interface or simply TPUI) is a software application that allows users to play original arcade games on their personal computers. It provides compatibility for a wide range of arcade hardware, making it possible to run games originally designed for dedicated arcade systems.
TeknoParrot supports over 140 game platforms and systems:
| Manufacturer | Platforms | Manufacturer | Platforms |
|---|---|---|---|
| Atari | Denver · Flagstaff · Hard Drivin · MediaGX · Phoenix · Seattle / Seattle Widget · Vegas | Capcom | CPS1 / CPS2 / CPS3 · ZN-1 / ZN-2 |
| Coastal | PC / Linux PC | Gaelco | PC / PC (3D Hardware) / PC (Atari License) |
| ICE | PC / Linux PC / ICE-RT Linux PC | Konami | Cobra · GQ · GTI Club · GV · Hornet · M2 · NWK-TR · PC · System 573 · Viper |
| Midway | Atlantis · PC · Seattle · V Unit / V Unit Plus · Vegas · Zeus / Zeus II | Namco | BNA1 / BNA1 LITE / BNA1-ES4 · ES1 / ES3 / ES3A / ES3B / ES3X / ES4 · N2 · System 10 / 11 / 12 / 21 / 22 / 22.5 / 23 / 23 Evolution 2 · Super System 22 / 23 · System 147 / 246 / 256 / 357 / 369 |
| Raw Thrills | Raw Thrills / PC / Linux PC | Sega | ALLS · Amusements · Chihiro · Europa-R · Lindbergh Red / Red EX / Silver / Yellow · Model 1 / 2 / 3 · Nu / Nu 1.1 · PC · RingEdge / RingEdge 2 / RingEdge 2 (APM2) / RingWide · System 32 · Triforce |
| Sony ZN-1 | Sony · Acclaim · Atari · Atlus · Eighting, Raizing · Taito FX-1 · Tecmo TPS | Taito | Air · FX-1 · G-NET / G-NET (Tecmo TPS) · NESiCAxLive / NESiCAxLive2 · PPC JC Type-C · Type X / X PC / X Zero / X+ / X2 / X3 / X4 |
| Team Play | PC / Linux PC |
| Acclaim Epidemic | Adrenaline PC | AirFrame PC | CAVE PC | Cecropia PC |
| Chicago Gaming Company PC | Cosmodog PC | Covielsa PC | D-Gate PC | Em-Teck PC |
| EXAMU eX-BOARD | GameWax PC | Global VR PC | Interactive Light PC | IT Nighthawk |
| Korean PC | Nintendo RVA | PAOKAI Linux PC | Phantom PC | Ritual Entertainment-Activision Custom |
| Roxor Games PC | SNK Hyper Neo Geo 64 | TouchMagix PC | Triotech PC | Tsunami PC |
| UDC PC | Uniana PC | UNIS PC | Unique PC | WAHLAP PC |
Players can configure game settings, map controls to keyboard, controller, or even force feedback wheels, and in some cases use network play to recreate more of the original arcade experience on PC. It is especially popular with people who enjoy preserving and playing arcade titles that were never properly released for home use.
Quite a few games in TPUI are free to play, but newer games may require an active monthly subscription. That helps fund ongoing development and support. These kinds of devs do not work for free, y'all.
Always run the latest TPUI version available. Before troubleshooting any game, use the hamburger menu in the top-left of TPUI to Check for Updates, then Install Updates if needed. Update first, retest second, ask for help third.
This project aims to clean up, organize, standardize, and maintain arcade game dumps used with the TeknoParrot loader.
Public game dumps (unpacked drive images) often arrive with all kinds of baggage attached from the underground arcade scene, including:
- operating system or platform leftovers
- older loaders and launcher junk
- mods and other assisting utilities
- temporary files and runtime-generated files
- unrelated scripts and support tools
- orphaned folders from previous repacks
The goal here is to remove the clutter and produce something more useful for collectors:
- cleaner folder structures
- more consistent naming
- more predictable file layouts
- easier integrity checking
- easier long-term maintenance inside RomVault
This project is still a work in progress and will likely be for a long time. The goal is eventual perfection. The reality is that refinement happens over time, one cleanup pass at a time.
This is not just a random pile of TeknoParrot game folders.
The broader aim is to keep one curated collection that is:
- practical for collectors to store and manage
- consistent enough for reliable scanning and rebuilding
- cleaned up enough that you are not dragging around years of junk from old repacks
- named sensibly enough that the files make sense at a glance
Whenever possible, the collection is shaped toward what most people actually want:
- one good main release per supported game
- cleaned folders
- reduced junk
- clear naming
- notes where weirdness matters
It is a collector set, not a museum of every random broken repack that ever floated around the internet.
Earlier in the life of this project, there was one big datfile with everything thrown into it. That worked for a while, but over time it became bloated.
The original idea behind splitting things was simple:
- keep the main TeknoParrot dat focused on one primary release per supported game in TPUI
- push everything else into a supplementary dat
That supplementary material included things like:
- language translation mods
- supported minor game revisions that are older than the latest version in the core dat
- alternate music variants
- unsupported but useful enhancements
- setup guides to assist users in setting up certain platforms
- landscape hacks for portrait games
- larger compatibility mods needed for modern operating systems
For example, games such as Gaia Attack 4 and Haunted Museum II needed major video conversion work for modern Windows systems because their original proprietary video formats were no longer practical. Those conversions worked, but they massively increased file sizes and were really mods, not original content.
The main philosophy remains the same:
- the core set should stay practical
- extra or non-standard material should be clearly treated as extra material
- one supported, sensible main release per game is still the preferred approach
This is a RomVault-only DAT.
That is not me being dramatic. It is because many games in this collection contain things that other ROM managers do not handle correctly, especially:
- zero-byte files
- empty folders
- unusual folder structures
- content layouts that do not behave nicely in other managers
RomVault is the ROM manager this collection was built around for scanning, rebuilding, and general collection management.
Other ROM managers such as:
- ClrMamePro
- Romulus
- RomCenter
are not designed around the way these game folders are structured, so they are not a proper fit here.
If you want to manage this collection correctly, use RomVault.
Also, a small number of games contain nested ZIP archives that must remain zipped for the game to function. I cannot change that. It is what it is.
Do not ask for RomVault support in the TeknoParrot Discord. If your question is about RomVault, take it to the RomVault community.
An interactive compatibility and setup reference for the TeknoParrot collection, updated alongside every dat release. Other than the notes themselves and the condition of the game (working, broken etc), the existing XML's provided by the TeknoParrot UI are the source of information that, combined with everything else, forms the webpage.
Each game entry includes:
- Compatibility status — Working / Partial / Broken / Untested
- Hardware compatibility — per-GPU family results (NVIDIA, AMD, Intel) with known issue details
- Setup executables — primary, secondary (daemon), and test menu EXEs where applicable
- Arcade system — the original hardware platform the game ran on
- Supplementary archives — alternate versions, orientation fixes, patches, mods, and DOX/EMU/APP packs linked to each title
- Notes — setup tips, workarounds, controller config, and anything else worth knowing
- Tags — quick-reference labels for common traits (e.g.
lightgun,amd-fix,no-sound-fix)
The page is fully client-side — no login, no install, works in any browser.
- Search the full text of any field including notes
- Filter by status, TPLoader backend (TeknoParrot, OpenParrot, RPCS3…), or GPU compatibility
- Expand any row to see the full detail panel
- Works on mobile
-- NEW UPDATES COMING SOON!
In RomVault, you can store the collection in several archive formats:
- Zip (TorrentZip)
- 7z (LZMA)
- ZStandard in ZIP or 7z form
The short version:
- Use ZStandard if you want fast extraction and more practical day-to-day use
- Use TorrentZip if you want the safest common-denominator choice and like sharing with random people
- Avoid 7z/LZMA unless you enjoy watching your machine age in real time
One example game in the collection contains 1381 folders and 4853 files.
- Original size: 1,777,325,102 bytes (1.66 GB)
| Final Size | MB | Compress Speed | Extract Speed | Format |
|---|---|---|---|---|
| 929,942,678 | 887 MB | normal | slow | Zip-Torrent |
| 805,497,880 | 768 MB | slow | very slow | 7Z-LZMA |
| 631,563,006 | 602 MB | slow | ultra slow | 7Z-LZMA-Solid |
| 868,626,724 | 828 MB | faster | very fast | Zip-ZSTD |
| 867,793,906 | 828 MB | fast | very fast | 7Z-ZSTD |
| 729,269,298 | 695 MB | fast | very fast | 7Z-ZSTD-Solid |
TorrentZip creates deterministic ZIP archives that match between users when packed the same way. That is useful for sharing, comparison, and consistency.
ZStandard also gives excellent speed, slightly better compression than TorrentZip in many cases, and much faster extraction than LZMA. It is the better practical choice if your toolchain supports it.
7z/LZMA is not recommended for an actively maintained collection. Yes, it compresses well. No, you will not enjoy updating or extracting it later.
If you are not going to read the full write-up and just want the quick answer: use TorrentZip or ZStandard, and do not fall into the 7z trap.
If your collection is already stored as TorrentZip and you want to move to ZStandard, RomVault includes Structured Archive Maker (SAMUI) in the Help menu.
That tool can convert archives in parallel using multiple worker threads. Doing the same conversion through normal RomVault archive-type changes is much slower because RomVault processes files one at a time.
A few practical notes:
- more worker threads means more I/O pressure
- spinning disks do better with fewer threads
- SSD and NVMe storage can handle more aggression
- long conversion jobs will heat up SSDs and NVMes, so keep cooling in mind
And remember:
TeknoParrot only uses games in an uncompressed state. Archives are for storage, movement, backup, and collection management.
Some games contain ZIP files inside their game folder as part of the game’s original file structure. By default, RomVault treats ZIP files as archives and scans the contents inside them. In a few cases, what you actually need is for RomVault to treat the ZIP as a normal file. The nested zip files included in this collection need to remain as a zip file for that game to function, and must not have any deflate algorithm applied to them that does not 100% align with the deflate algorithm, otherwise the game's decompressor will not be able to unpack the zip contents to use during gameplay. This means no ZStandard, no 7Zip. TorrentZip is OK to use but it does not create a "pure" deflate archive as it adds a comment line to indicate its deterministic hash, which is non-standard.
Bearing all this in mind, I decided to simply ensure any nested zips in this collection all use the natural, simple and fully compatible Zip DEFLATE, with "STORE" compression set so no compression is applied to the nested zip or its contents. This gives the user the ability to recreate the zip archives should the need ever exist, as there is no compression to deal with. Nested zips that don't come from MAME are made with 7-Zip; nested MAME zips are StoreZips (see below).
Since most people will compress the parent game folder with TorrentZip, 7Zip or Zstandard, the lack of compression in these internal nested zips will be compressed at the parent level, so you'll still get space savings.
Many games in the collection (NAOMI, Sega Model 2 and 3, Konami, Namco, Capcom and other arcade boards) carry MAME ROM sets as nested zips: the game's own MAME set, plus BIOS and device zips such as naomi.zip, naomigd.zip and jvs13551.zip. Every one of them is now a StoreZip, marked format="storezip" in the dat, and every ROM inside them matches official MAME.
The dat doesn't only list the ROMs inside a nested zip. It also lists the nested zip itself as a file with its own size, CRC and SHA-1, and RomVault checks the whole file against that hash.
The problem is that an ordinary zip's hash depends on far more than the ROMs inside it:
- file dates;
- the order the files were added;
- folder entries and extra timestamp fields;
- which tool made it, and its compression settings.
Two people zipping the exact same ROMs with 7-Zip on two different PCs get two different files with two different hashes. That means a nested zip could never be rebuilt to match the dat. If yours went missing or got damaged, the only fix was finding someone else's copy.
A StoreZip fixes every one of those bytes:
- files stored (no compression), so the game can read them and your game zips still compress them at the parent level;
- files sorted the same way every time;
- one fixed date, no folder entries, no extra fields and no comment.
What's left depends only on the ROMs inside. The same ROMs always give the same StoreZip, byte for byte, on any computer, so its hash in the dat can be reproduced by anyone.
MAME is the reference for these arcade boards. Its official ROM list (the MAME XML) records every ROM's name, size, CRC and SHA-1, which set it belongs to, and which ROMs belong to BIOS and device sets. It is corrected with every MAME release.
Before this, many nested MAME zips in the collection were one-offs: trimmed to only the variant TeknoParrot used, packed from older MAME layouts, or carrying ROMs MAME now keeps in a device set. They worked, but nobody could recreate them from a real MAME set, and every one was slightly different.
Lining up with MAME means:
- One standard. Each nested MAME zip holds exactly what the MAME merged set of the version the dat follows holds (currently MAME 0.289). Clones are in their parent's zip, and BIOS and device ROMs are in their own zips, just as in MAME.
- Every ROM matches official MAME, byte for byte. Every file inside every nested MAME zip has the name, size, CRC and SHA-1 MAME lists for it. Combined with the StoreZip format, every nested zip in the collection is exactly what you get by running StoreZip on that MAME merged set.
- You can rebuild from what you already have. If you keep a MAME merged set, you already have everything needed to recreate any nested MAME zip in the collection.
- The collection follows MAME. When a new MAME version changes a set, the collection's copy changes with it.
- Stored zips make the collection smaller. The collection's game folders are TorrentZip or ZSTD-compressed by RomVault. A stored nested zip compresses well inside them, but a deflated (TorrentZip) one barely compresses at all.
For example, on "18 Wheeler":
| Nested zip | Size | Space it takes in the game zip | Deflated, TorrentZip-style |
|---|---|---|---|
| naomi.zip | 59.3 MB | 1.5 MB | ~9 MB |
| 18wheelr.zip | 189 MB | 86.6 MB | ~93 MB |
naomi.zip alone is nested in about 200 entries, so this adds up across the collection.
- Byte-matching Pleasuredome wouldn't hold anyway. Their sets are rebuilt with every MAME version, so a TorrentZip copy would only match while both sides were on the same release. Many users keep their MAME sets in other formats too (my own are RomVault RVZSTD, not TorrentZip). The ROM files inside match MAME exactly. The zip containers are StoreZips, so their hashes won't match the TorrentZip zips in your MAME folder, but they will match anything StoreZip builds from that folder.
None of this was repacked by hand. My own datfile tools do it:
- read the official MAME data and the MAME merged sets;
- build every nested MAME zip as a StoreZip straight from MAME's own zips, never from extracted files;
- check every file in it against MAME;
- refuse anything that doesn't match;
- update the dat.
The same build is run again to prove the result: rebuilding every nested MAME zip in the collection from MAME gives back exactly the hashes in the dat.
People make mistakes repacking hundreds of zips: a wrong file, a stale variant, a stray folder, a different date. A tool that follows a fixed spec and checks itself against MAME doesn't. That's what keeps the collection consistent and accurate from one release to the next.
- Get Eggman's StoreZip (Windows, Linux and macOS).
- Use MAME merged sets of the version the dat names. The reference is Pleasuredome's "MAME 0.xxx ROMs (merged)" set from the Pleasuredome MAME page. Non-merged or split sets, and "BIOS and devices" packs, hold different files and won't match.
- Drop the MAME zips you need onto StoreZip. It writes them to your output folder as
name.zip_. - Put those files in a RomVault ToSort and run Fix. RomVault matches them by hash and places them as
.zipinside the right games.
The .zip_ extension is the same trick as in the workarounds below: it stops RomVault opening the nested zip as a set of its own. The exact format is in the StoreZip spec.
- rename the nested archive suffix temporarily, for example from
.zipto.zip_ - or place those ZIPs into a FileOnly ToSort location so RomVault rebuilds them as files
That gets around the issue cleanly enough.
RomVault also supports a Mixed (archive as file) mode, but that is not a good fit here because it effectively forces the collection into a fully uncompressed workflow, and this set is far too large for that to be a pleasant long-term choice.
As much as I dislike putting a CHD inside a zip, it cannot be helped. Just understand that a CHD is a container, and contains its own compression formats internally, thus it has an internal SHA1 hash value of its internal contents. There is zero bonus for putting them inside a zip. They belong out on their own, in the raw. It would be too much work and confuse the hell out of most people who barely understand what a datfile is to keep CHD's in their native format and outside of zips. It's not ideal, but it's all I have to work with to keep things in the folder and structural format TPUI wants.
Some TeknoParrot games rely on modified executable files or other patched core files to work around things like:
- copy protection
- resolution handling
- input handling
- compatibility issues
- platform-specific oddities
That means some games may trigger false positives in antivirus software.
In plain English: a handful of patched executables look suspicious to AV software, even when the files are there purely to make the game run.
None of the TP games in this curated collection are intended to be malicious, but I also cannot control where you got your files from. Use common sense when handling unknown files from the internet.
Do not globally disable your antivirus on a machine you care about.
Instead, set folder exclusions for:
- your TeknoParrot games folder
- your RomVault download folder
- your temp/cache folders
- your ToSort folder
Common executables that may trigger a false-positive include:
- Daytona Championship USA [Sega PC]
- Exception [Taito NESiCAxLive]
- Luigi's Mansion Arcade [SEGA Nu 1.1]
- Raiden III (2005) [Taito Type X]
- Raiden IV (2007) [Taito Type X]
If you do not set proper exclusions, do not be shocked when your antivirus eats game files and wrecks your setup.
A game existing on the internet does not automatically make it a supported TeknoParrot game.
Many arcade titles need custom work before they can run in TPUI, such as:
- executable patching
- disassembly and reverse engineering
- DLL hooks
- plugins
- loaders
- other game-specific fixes
If you try to launch an unsupported version, you will often get an unsupported CRC error or just a dead launch.
Also, from an arcade operator’s point of view, a newer version does not always mean more content. Many updates are simply:
- hardware bug fixes
- OS-level fixes
- operator-side maintenance revisions
- minor changes with no meaningful player-facing content
The TeknoParrot developers usually support the version that gives the best practical result for users, not necessarily every version ever released.
When a game version becomes officially supported by the TP team, it can be brought into the collection.
Usually, this is a you problem before it is a collection problem.
Common causes include:
- the game was not configured correctly in TPUI
- you are using the wrong resolution
- you are using unsupported GPU hardware
- an old third-party loader or patch is interfering
- required service mode settings were never configured
- TPUI changed and something that used to work no longer behaves the same way
- you didn't read the manual
- you didn't know a manual existed
- you found the manual, but can't understand how to read it
- you asked someone else to read the manual for you, and are now more confused than before
The TP developers do their best to support NVIDIA, AMD, and Intel hardware, but that does not mean every game behaves the same across all GPUs.
Some games are heavily vendor-dependent. A good example is Incredible Technologies material, which is only designed to run on NVIDIA GPU hardware.
If you want the best overall compatibility across the collection, use NVIDIA.
If a game is officially supported and still gives you trouble after you have:
- updated TPUI
- checked your game setup
- confirmed your GPU is supported
- removed conflicting junk files
then ask for help in the proper TeknoParrot Discord channel.
Intel graphics should generally be treated as a last-resort option. Newer Intel GPUs may do better than older ones, but overall compatibility is limited and a good chunk of games simply will not behave.
I do not personally test on AMD GPUs, so I am going by user reports here. AMD users usually have more work to do, and some games may never behave properly at all. Some older games may require AMD graphics patches.
NVIDIA is the clear winner for TeknoParrot compatibility. If you are serious about getting the widest range of games running with the least pain, use NVIDIA. Anything in the RTX 3000-series or earlier, even going back to the 1080-series, is still viable as a GPU. Check with the TP Discord about specific card questions.
CPU vendor matters much less than GPU vendor. In general, Intel and AMD CPUs are both fine. A few games may dislike specific Intel generations, but that is the exception rather than the rule.
Some Unity-based games in the collection include a BepInEx folder.
BepInEx is a patcher and plugin framework for Unity and .NET games. It lets the devs inject custom code and patch assemblies in memory where needed.
When running a BepInEx-based game for the first time, you will often need to start and restart the game twice so the framework can finish configuring itself.
Example games in the collection that use BepInEx include:
- Night Hunter After Dark Chapter II
- Wild West Shootout
- Chase Chase Joker
- Need for Speed Heat TakeDown
- Family Guy Bowling
You can safely reset BepInEx by deleting:
BepInEx\cacheBepInEx\config
Do not delete:
BepInEx\coreBepInEx\plugins.doorstop_versiondoorstop_config.iniwinhttp.dll
If you have an updated plugin DLL, place it in:
BepInEx\plugins
and replace the previous version.
You can update BepInEx by replacing its files with the latest stable x64 release.
Rules:
- use the most recent stable x64 build
- do not use beta releases
- do not use x86 builds
- to grab the latest release, visit the Bepinex github
Some games can run too fast or otherwise behave badly if left uncapped.
When that happens, use a frame limiter such as RivaTuner Statistics Server and cap the game to 60 FPS, or use your GPU software if it provides a frame limiting option.
If a game is running like it got into the good cocaine, this is one of the first things to check.
Some older games require TPUI to be run with elevated privileges.
If TPUI complains that it needs administrator rights:
- close TPUI
- right-click the TPUI executable
- choose Run as administrator
Nothing mysterious there.
- Intel Core i7-13700
- 64 GB RAM
- NVMe local storage
- NVIDIA RTX 3050 8GB
- Windows 11 Pro
Every single game has been tested, including subscriber-only games.
- game paths are kept short where practical, for example:
D:\TPGames-testing\<game folder> - games are tested in fullscreen mode whenever possible
- unnecessary third-party loaders and patches are removed unless TPUI genuinely needs them
- required general fixes may be kept if they are necessary for the game to function
- crosshairs are included where supported
- bezels are generally not supplied unless they are especially useful, such as for portrait games
- service-mode files may be preconfigured if a game needs awkward internal settings to become usable
- testing normally includes reaching attract mode and verifying at least some in-game play
Many of these dumps came from the internet and were passed around repeatedly before landing here. That usually means they arrive with years of extra nonsense attached.
I do my best to clean the folders back toward a fresher, more original state. When possible, I compare against fuller drive dumps to make that process more accurate.
It can take multiple iterations of the dat before a newly added game is fully cleaned up. DO NOT EXPECT PERFECTION ON THE FIRST RELEASE! Give me some bloody time.
- remove orphaned files and folders from previous loader setups
- remove other loaders and their support files
- remove obvious original-hardware system leftovers where safe
- remove random junk files and folders not needed for the game
- remove obvious log files, while leaving required
.logor similar data files intact - use ReShade where needed for portrait-to-landscape presentation with bezel support (Supplementary games)
- include custom crosshairs where the game supports them
- remove files such as:
teknoparrot.inisteam_appid.txtthumbs.db- macOS junk files
The collection uses the following filename format:
<game title> (version)(YYYY-MM-DD)(Region)[Platform][TP]
<game title>
Uses the title as listed by the game developer when known. Original casing is preserved where appropriate. If the intended casing is unclear, normal English title case is used.
(version)
Included when known. The leading v is removed because it is implied.
(YYYY-MM-DD)
Used when the full release date is known. If only the year is known, only the year may be used.
(Region)
Standard region notation when known. A game being in English does not automatically mean it is a USA release.
[Platform]
The game’s arcade system platform.
[TP]
Used to visually identify the games came from the TeknoParrot Collection. There are other collections I curate that may also have the same or very similar games/versions with the same type of file naming. This hopefully avoids accidental crossover when users are extracting games across different loader platforms.
If you are looking for the Incredible Technologies Super Easy Universal Setup Guide, it lives here:
- tp-it-guides repository on GitHub
There are community-created torrents and archival sources floating around in the usual places. Roms are Rare and org has a big archive.
This README is not intended to be a sourcing manual. Use your own judgment, be careful with unknown files, and do your own homework.
No.
I am not associated with TeknoParrot, its admins, or its developers. I am just a collector who wanted my own curated TeknoParrot set. I don't even get a free subscription.
If you paid some back-alley drive seller for this dat or for a set built from it, then congratulations — you got hustled.
This project exists because I enjoy doing the work. Don't be a dick by paying someone else for my efforts.
Original source code, scripts, tooling, and hand-authored documentation and metadata in this repository are licensed under the MIT License.
Archived game data, binaries, firmware, media assets, and other third-party materials are not covered by the MIT License and remain the property of their respective copyright holders.
See the LICENSE and NOTICE files for full details and scope clarification.
If these tools, dats, notes, or archives save you time, consider supporting the work.
