That's a question of proper dependency handling. When the game depends on that library and the library is available on the system it should automatically be installed when you install the game. Bundling the library with the game is not
The problem is not my
installation, I know how to handle that. The problem is the number of systems of users which do not know how to handle it and which are not provided with security updates of these bundled libraries and then work as spam relays, members of bot nets, whatever ...
That assumes that the packages are available at all.
For example, I've encountered various Mono and node-webkit games where, on Ubuntu 12.04, they worked out of the box perfectly but, on 14.04, you had to do non-trivial stuff to get them to work because they depended on system libraries with ABI versions which simply weren't in the package repository anymore.
For example, many games built on proprietary node-webkit/nw.js-based engines now depend on libudev.so.0 due to the engine developers being slow to release updated builds.
However, Ubuntu 14.04 only offers libudev.so. https://filezilla.software
and many indie devs are instructing people to make a symlink to libudev.so.1 since, in whatever they've tested, the ABI mismatch hasn't caused a crash.
(I'm not sure why they don't just bundle a build of libudev.so.0. It's LGPLed, they're not statically linking to it, and the source is something on the order of 150KiB. Trivial to bundle to ensure they'll always be satisfying their LGPL obligations.)
This kind of error is common when you have no support for 32-bit applications on your system.
You probably need to install a couple lib32-* packages, starting with lib32-glibc.