I wanted to note that the installation instructions suggest modifying files in the installation directory of Mathematica. You should never do this without very good reason, and without being aware of the potential consequences. It even suggests modifying your sysinit.m file, for which there is never a good reason, and which can completely break your Mathematica.

The fact that finding such installation instructions is still fairly common illustrates why it is so critical that Wolfram Research should provide guidelines and training materials for package developers.

Some people will inevitably fail to follow instructions precisely. When the installation instructions involve doing serious surgery on Mathematica (as here), the consequences of a mistake can be dire. The end result is that user will learn that "packages are not to be trusted" and "it's better to rely solely on built-in stuff". That attitude of users is damaging the health of the Wolfram Language package ecosystem.

Update: To be clear, the criticism is primarily aimed at Wolfram Research (not the package's author) for not publicizing best practices. It is not that easy to figure out the best way to put together a complex package, especially if one has to work with multiple bits of very old code. The package referenced here clearly contains a lot of useful and non-trivial functionality, and I hope that it will continue to be maintained and these issues will be ironed out.

However, what I said above also stands: modify Mathematica's system files at your own peril! Wolfram would be right to refuse support once you have done that.

Thank you both for the answers.

Due to the justified criticism that we have not respected best practice of publicizing a Mathematica package with the consequence that we have provided, in particular, incorrect manual installation instruction for Windows systems, we decided to completely overhaul the package structure.

Since version 2.5.1, the package is distributed as a Paclet that allows a custom installation for everyone. The installation of the package requires about 90 MB free hard-disk space, and the Mathematica version should not be smaller than 10. For Mathematica versions smaller than Version 10, a manual installation is requested. In that case one has to respect the guidelines related to the associated operating system that can be found from the Mathematica documentation.

Moreover, in order to react more quickly to the needs of the community, we changed the host from Wolfram Library Archive to GitHub. The most recent version 2.5.4 can now be downloaded from the following URL

Project Host

as an ordinary Zip file or as a Mathematica Paclet that can be found at

URL Paclet: TuGames

We strongly recommend to rely on a custom installation. Such a installation can be easily accomplished while applying the subsequent steps:

Start Mathematica, open a notebook, and execute therein

PacletInstall["/full/Path/to/TUG-2.5.4.paclet"]

that should return the value

Paclet[TUG, 2.5.4, <>] 

to indicate a successful installation. Notice that

/full/Path/to/TUG-2.5.4.paclet

indicates the directory where the TUG-2.5.4.paclet is located at your hard-disk.

After these steps, the installation procedure is completed, and one can start a session while executing

Needs["TUG`"]

For additional information of how to use the package, and to get a rough overview of the implemented changes we also refer the inclined user to our post at

tugames-package-does-not-run

We highly appreciated the conducted discussion at this forum while making us aware about some crucial deficiencies of our package, and we hope that the new and revised version fits now better the needs of the community.

Updated Information for Installing the Package TuGames: 17.05.2020

For those who want to get the most recent version of the Mathematica Package TuGames 2.6.1, we recommend a direct installation from GitHub under Mathematica V11.3 or later while executing in a notebook the command

ResourceFunction["GitHubInstall"]["himeinhardt", "TuGames"]

otherwise one needs to follow one of the alternative custom installation procedure that can be found at project home at GitHub

TuGames