Language Selection

English French German Italian Portuguese Spanish

Machinarium - A Tasty Gaming Treat

What would you do if you were thrown and locked out of town separated from your true love? You'd fight every obstacle to return and rescue her, of course. And that's your goal in Machinarium. As the hero, you must figure out how to out-smart the bad guys and to save your lovely girlfriend.

As the game opens you find yourself broken and discarded in the dump outside the city wall. Your first task is to reassemble yourself. Once that is accomplished, you can begin your quest to return to the city and your girlfriend. Your adventure unfolds as you solve puzzle-like problems in order to progress. For example, how do you trick the guard to lower the drawbridge? Or how might you enter a tunnel that remains sealed except for the few seconds when a train cart passes?

The back story is revealed through Josef's memories seen as thought bubbles as the story progresses. Some of the first memories recollect our hero and his love as children playing around in an oil bath laughing and splashing. Later, dirty deeds of the antagonists against our hero, how he came to be in the city dump, and how the girlfriend came to be captured are revealed. It's amazing how these small glimpses into Josef's mind, feelings, and motives start to build a three dimensional character and pull the player in from almost the start. You care about him and want to see him reunited with his girlfriend. The environment is as much a character as the robot. It's a mechanized world of greasy and rusting metal fallen into disrepair - dirty, dangerous, and desolate. It's like Dr. Seuss meets the Road Warrior. Yet ironically, there's something quite beautiful in the cold metallic smoggy maze.

The game doesn't waste much time before the puzzles become challenging. Fortunately, you're not all on your own. Each puzzle environment has a hint bulb that will give you one quick hint usually pointing to the one thing that will make the rest fall into place. But if that's not enough, there's a book of sketchboards containing almost the full sequence of steps. Although the book is locked by a side-scrolling Alien Invaders type of game you must complete before gaining access. This will prevent someone from seeking answers too soon and also avoids the scramble of trying to find a walkthrough full of spoilers. However, Josef provides help himself. If you try to send him somewhere or do something inadvisable, he'll shake his head and mumble, "uh huh." Sometimes he'll give you hints through his thought bubbles as well. It's just an utterly charming game.

The best thing about Machinarium is that it also runs on Linux. News of this game's existence almost missed the Linux community entirely. However, upon its official release on October 15, a Linux version was also released. Surprisingly, after remitting the small fee users are given access to versions for all three platforms as well as the background music in MP3 format. An online demo is available to try before you buy, but a word of warning, once you begin you'll want to finish.

The Linux version is packaged as a compressed archive, or tarball. Some users will be able to simply click on this tarball and an archive manager will open. At that point click "Extract" to unpack the files. For others, open a terminal and change directories where you'd like the game installed. Unpacking it and running it from your home directory is perfectly acceptable and many times preferred, but if you'd like it available to other users, su to root and change directories to perhaps /usr/local/games. Just extracting the tarball is all that's required. You can start the game in a terminal or you might wish to make a link on your desktop. In summary, for example:

1. cd ~
2. tar -zxvf ~/Downloads/Machinarium_full_en.tar.gz
3. To play: cd Machinarium/
4. ./Machinarium

To unpack the background soundtrack:

1. unzip ~/Downloads/MachinariumSoundtrack.zip

Machinarium is a Flash-based game and as such the gameplay might be a little different from other games you've played, but it's described as point and click. Cursor clues drive the game action. Tests here found it didn't play very well under the KDE 4 environment with only one gigabyte of RAM. However, under other window environments, it played well for the most part. Some areas of the game suffer a bit of lag, but those with more memory shouldn't experience any negative issues with performance. Some suggest disabling (or enabling) Hardware Acceleration in your Flash settings (right click anywhere on the game screen), but this didn't seem to effect performance here either way. However, disabling Fullscreen when encountering these "heavy" areas helped a bit1. There is an active user forum if you need assistance or just want to learn more.

Machinarium is an imaginative game with a beautifully rich environment and amazing details. You'll fall in love with the ineffable main character and become addicted to his alien world. It's well worth the small fee for the hours of enjoyment received in exchange. For us Linux users, it's an especially tasty treat.

---

1. Adding another gig of RAM cured the lagging/hesitation issue.

(Update: If it begins to lag again real bad after playing and quitting a few times, eating up all CPU, try rm -rf ~/.macromedia - after moving your saved game file located at ~/.macromedia/Flash_Player/#SharedObjects/<some random number>/#localWithNet/Machinarium/Machinarium.sol)







More in Tux Machines

Google, IBM and Microsoft

  • Five Common Chromebook Myths Debunked
    When Chromebooks first came out in 2011, they were basically just low-spec laptops that could access web apps – fine for students maybe, but not to be regarded as serious computers. While they’ve become more popular (the low cost, simplicity, and dependability appeal to businesses and education systems), as of 2018 Chromebooks still haven’t managed to become widely accepted as a Windows/Apple/Linux alternative. That may be about to change. The humble Chromebook has gotten a lot of upgrades, so let’s get ourselves up to speed on some things that just aren’t true anymore. [...] The 2011 Chrome OS was pretty bare-bones, but it’s gone to the opposite extreme since then. Not only is it steadily blurring the line between Chrome and Android, it can now install and run some Windows programs as well, at the same time as a Chrome and an Android app, if you like. And hey, while you’re at it, why not open a Linux app as well? You can already install Linux on a Chromebook if you want, but one of the next versions of Chrome OS is going to include a Linux virtual machine accessible right from your desktop (which is already possible, just not built-in and user-friendly). In sum, Chrome OS has gone from barely being an operating system to one that can run apps from four other OSes at the same time.
  • Like “IBM’s Work During the Holocaust”: Inside Microsoft, Growing Outrage Over a Contract with ICE
  • Ubuntu Podcast from the UK LoCo: S11E15 – Fifteen Minutes - Ubuntu Podcast
    ...Microsoft getting into hot water over their work with US Immigration and Customs Enforcement. Plus we round up the community news.

KDE on Android: CI, CD & SDK

I guess we all agree that one of the biggest stoppers to get a contribution out is the ability to get the system ready to start working on the contribution. Today I want to talk a bit about generating Android binaries from our machine. In the KDE Edu sprint we had the blatant realisation that it’s very frustrating to keep pushing the project while not being swift at delivering fresh packages of our applications in different systems. We looked into windows, flatpak, snap and, personally, I looked into Android once again. Nowadays, KDE developers develop the applications on their systems and then create the binaries on their systems as well. Usually it’s a team effort where possibly just one person in the team will be familiar with Android and have the development combo in place: Android SDK, Android NDK, Qt binaries and often several KDE Frameworks precompiled. Not fun and a fairly complex premise. Read more Also:

today's howtos

Linux Kernel and Security: LVM2, Containers, AMD

  • LVM2 Begins Work On Major Changes To Logical Volume Management
    LVM2 as the user-space tools for Logical Volume Management (LVM) on Linux is in the process of going through a big re-work.
  • Containers and Cloud Security
    The idea behind this blog post is to take a new look at how cloud security is measured and what its impact is on the various actors in the cloud ecosystem. From the measurement point of view, we look at the vertical stack: all code that is traversed to provide a service all the way from input web request to database update to output response potentially contains bugs; the bug density is variable for the different components but the more code you traverse the higher your chance of exposure to exploitable vulnerabilities. We’ll call this the Vertical Attack Profile (VAP) of the stack. However, even this axis is too narrow because the primary actors are the cloud tenant and the cloud service provider (CSP). In an IaaS cloud, part of the vertical profile belongs to the tenant (The guest kernel, guest OS and application) and part (the hypervisor and host OS) belong to the CSP. However, the CSP vertical has the additional problem that any exploit in this piece of the stack can be used to jump into either the host itself or any of the other tenant virtual machines running on the host. We’ll call this exploit causing a failure of containment the Horizontal Attack Profile (HAP). We should also note that any Horizontal Security failure is a potentially business destroying event for the CSP, so they care deeply about preventing them. Conversely any exploit occurring in the VAP owned by the Tenant can be seen by the CSP as a tenant only problem and one which the Tenant is responsible for locating and fixing. We correlate size of profile with attack risk, so the large the profile the greater the probability of being exploited.
  • Canonical Releases AMD Microcode Updates for All Ubuntu Users to Fix Spectre V2
    Canonical released a microcode update for all Ubuntu users with AMD processors to address the well-known Spectre security vulnerability. The Spectre microprocessor side-channel vulnerabilities were publicly disclosed earlier this year and discovered to affect billions of devices made in the past two decades. Unearthed by Jann Horn of Google Project Zero, the second variant (CVE-2017-5715) of the Spectre vulnerability is described as a branch target injection attack.