Skip to content is dead, new host is is dead, new host is published on No Comments on is dead, new host is

A long time ago, the infamous klaatu of GNU World Order fame, recommended to me for a free and GNU friendly git host. I’ve been using them since, but the business model of (free) code hosting is a difficult problem to solve (just look at the recent Sourceforge scandals), and I was sad to receive an e-mail from them early this year about their closing down.

Gitorious was bought by Gitlab, a relatively well-known competitor of I’ve been discussing the move with Kastian for a while, and after trying out some alternatives, we ended up going for Here’s the current repo layout on github:

The main repo is the development version with current master (releases) and dev (development) branches. It will probably also contain some drafts of text-only documents for the background history, bestiary etc. in the future. The GPL only repository is provided as a courtesy for those who only want to look at/use/clone the Biamin «game engine» without any Creative Commons licensed artwork. The GPL version follows the official release cycle, with a short delay. The Legacy repo is provided for my own nostalgia, and contains the final version of the original game. It will only receive bugfixes.

The guys at are kind enough to continue hosting the static pages that are there now, and we’ve added a notice on each repo header to inform about the move to github.

Naturally, the move to github broke our update script, but that stopped working when we changed the branch models of the main repository. In order to future-safe the update script, I’ll be looking at using for hosting the release versions, regardless of code/git host. That’s all for now, more news to come shortly!

New development scheme for Biamin

New development scheme for Biamin published on No Comments on New development scheme for Biamin

We’ve changed a lot of stuff on the Biamin git repository, and I figured it’d be helpful to shed some light on how it’s supposed to work. (You can find this info in the git repo README as well.)

There are 3 main branches on the repository:

  • master: This is where we keep the last stable release of, the README and an archive/ folder with older, stable releases.
  • dev: This is where we keep the development files (numerous individual .sh files), a Makefile to build and a TODO. It also has a /licenses folder with our copy of the GNU GPL version 3 license as well as our Creative Commons license.
  • text: Currently N/A. This is a backup for textual resource for the world of Biamin.

The main idea being that a visitor can grab the lastest from the master (default) branch, that is both stable and recent. From now on, Biamin follows a versioning scheme of e.g. biamin 1.2.3, where 1 is official releases that are made for the master repo, 2 are feature added or major code overhauls and 3 are bugfixes, minor edits, commenting, formatting, etc.

Prospective developers or adventurous players can head to the /dev branch. If you git clone the repo, you can checkout to the dev branch and run ‘make’ to create a of the latest, unstable code. For any experimental feature, a sub-branch of /dev is created, for later merging to the dev branch (automatically or manually, depending on circumstances).

In order to create sensible logs, we ask committers to follow the conventions in the README. They aren’t mandatory, but makes sifting through heaps of commits much easier:)

This change in development scheme is the result of our decision to break up our code into their semantic parts, for easier coding. and signifies that we’re dealing with the menu of the core game or town configurations of the individual game respectively. In other words, Core* happens outside the loop or universally, while Game* is restricted to the loop, mostly.

Biamin mentioned in Linux Voice #2 (May 2014)

Biamin mentioned in Linux Voice #2 (May 2014) published on No Comments on Biamin mentioned in Linux Voice #2 (May 2014)

I was reading Linux Voice issue 2 last night, when my eyes stumbled upon a familiar ASCII image of Oldburg Castle on page 14! With the initial public release of Back in a Minute (1.2) I did e-mail the awesome guys at Linux Voice, notifying them of the release. I was not expecting to get anything in print, but seeing this was totally awesome! Click the thumbnail for a larger scan:)

Biamin in Linux Voice #2

Stable version 1.3.8, and new map released!

Stable version 1.3.8, and new map released! published on 2 Comments on Stable version 1.3.8, and new map released!

Shortly after version, we had gathered enough bugfixes to call it 1.3.8. I also created an update script for biamin players to keep their game current, and also a new pasted below, so you’ll have something to do in the weekend:)

DOWNLOAD version 1.3.8
Download the latest release from the download page.
GPL-Only releases are available here.

CHANGES in 1.3.8
Several small bugfixes in ASCII and LoadGame function were handed in by Kastian, thank you!
We’re eeking closer to version 1.4 which will be LEGACY.

Notably, there is now a biamin update script available! It simply pulls the raw text of the current in our gitorious repository, checks the version numbers of the local and the remote file and if they are any different, asks the player if s/he’d like to update the local to the latest version. This makes things so much easier, especially on the blogging side! Please note that the update script is version 0.5. It has been tested, but since it assumes default config there may still be bugs worth ironing out. The update script does not destroy character sheets, highscore list or the current configurations.

WORK IN PROGRESS on version 2.0
We’ve already started developing the new features for version 2.0. This version goes beyond the original scope of Biamin, so when 2.0 is released, the current game (reaching 1.4) will be renamed to Biamin-LEGACY. I’ve also started working on some of the many new ASCII screens the new features require.

This collaboration has forced me to learn how git is a developer’s tool and not just a fancy FTP put command. When I was coding alone there were few reasons to branch and merge code, since I was the only one who would face the consequences. But more than that, it has taught me how F/OSS projects grow and take on a life of their own. This is exactly why the concept of a LEGACY and a 2.0 version is important to me. The 2.0 would never have seen the light of day without Kastian! Cheers!

I’m going to revisit this function to make sure it sanitizes the map file before loading it into the game, for version 1.3.9. In testing it out, I created this little kingdom so ya’ll have something to do in the weekend;)

       A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R 
 1 )   @   @   x   x   x   x   x   x   T   .   .   .   .   T   .   .   @   @ (
 2 )   .   .   H   x   @   @   x   .   .   x   x   x   x   @   @   .   T   @ (
 3 )   .   @   @   @   @   @   x   .   x   x   x   x   x   @   @   .   @   @ (
 4 )   .   @   @   @   @   x   x   .   .   x   x   x   x   @   @   .   @   @ (
 5 )   .   T   @   @   x   x   x   x   .   @   x   x   @   @   @   .   @   @ (
 6 )   .   @   @   @   @   x   x   x   .   @   @   @   @   @   @   .   @   x (
 7 )   .   .   @   T   @   x   x   x   .   @   @   @   @   @   @   .   @   x (
 8 )   @   .   .   .   @   @   x   x   .   @   @   @   @   @   .   .   .   . (
 9 )   @   @   @   .   .   @   @   .   .   @   @   @   @   .   .   @   x   . (
10 )   @   @   @   @   .   .   .   .   @   @   @   @   @   .   @   x   x   . (
11 )   @   @   @   @   .   @   @   @   @   @   @   @   @   .   @   x   T   . (
12 )   @   @   @   @   .   @   @   x   x   @   @   @   @   .   @   x   x   . (
13 )   @   T   .   .   .   @   x   x   x   x   x   @   @   .   @   x   C   . (
14 )   @   @   @   @   @   x   x   x   x   T   .   .   .   .   x   x   x   x (
15 )   @   @   @   @   x   x   x   x   x   x   x   x   x   x   x   x   x   x (
          LEGEND: x = Mountain, . = Road, T = Town, @ = Forest         N
                  H = Home (Heal Your Wounds) C = Oldburg Castle     W + E

Add a launcher in your .bashrc

Add a launcher in your .bashrc published on No Comments on Add a launcher in your .bashrc

You can add a biamin launcher at the bottom of your (hidden) .bashrc file that resides in your home directory, to allow you to just run “biamin” in the terminal without having to remember the full path.
$ nano ~/.bashrc
# Biamin launcher
biamin() {
/path/to/your/ "$@"
CTRL+X and hit ENTER

Close the terminal and open a new one to enable the launcher. Done!