I'll third this. It wouldn't confuse anyone that way (other than figuring out where to find them in the first place).
Guys, if you REALLY want to unpack it without running the installer, someone already explained how to do that in this thread. But I can assure you this is certainly NOT the supported way of installing our games from now on and if you do that we CANNOT guarantee that everything will work without problems.
If I find something that gives me problems, I'll start learning how MojoSetup scripting works and see if I can write a non-interactive installer which executes only a trusted subset of MojoSetup scripting after my extraction script finishes.
My decision to remove write permissions from game folders after install is completed and symlinking any bits they complain about into $HOME for backup is already outside the range of supported installation configurations. (And I HAVE discovered some games which simply refuse to work in that configuration. As soon as I have time, I'll be looking into whether Ubuntu kernel builds include any overlay filesystems I could use to get the last laugh.)
...or maybe application sandboxing will advance sufficiently before that becomes an issue and I can just write a tool which:
1. Spins up a sandbox akin to a FreeBSD Jail for the game with a skeleton $HOME inside and no network access.
2. Runs the installer inside it and puppets it to completion
3. Adds an overlay mount so that any further changes beyond what the installer did will be redirected to a "game_saves" directory under the aegis of my nightly multiply-replicated backups.
(I don't like installers or applications doodling all over my homedir like little kids with markers, I prefer my installations to be Portable (my games folder is on a 2TiB USB 3.0 hard drive), I don't have room to back up game data to ensure I've got my save files, and I like to ensure that games will continue to work if their vendors go away by preventing things like Unity's first-run phone-home analytics ping from working.)