Skaven: Clan Skryre Army

I have been playing Warhammer and collecting miniatures for close to two decades now. I got into the hobby somewhere around 1995 and have been in and out of it since then. I currently play three Warhammer Fantasy armies, and Skaven are my latest and ironically the most complete one. I have started it when me and my brother went halfsies on the Island of Blood box set. He took the High Elf minis, and I took the Skaven. Initially I figured I will just put them together and use them as a small 500-1,000 point force for pick-up games. The goal was to make it playable without spending any money.

Of course, as it always happens with Warhammer money got spent and I ended up with a 2,000 points. The good news is that this army is more or less complete. Unlike my ever-expanding Dwarf Throng, I don’t actually see it ever growing beyond this size. It’s compact, flavorful and diverse enough to handle most situations. It has all the unit types I like, and none of the stuff I don’t. I’ve been told it is a pretty fun list, so I figured I would share it here along with some pictures.

Please note that I am not what you would call a “competitive player”. When I design an army I usually pick units that fit a theme I like, and which seem characterful and appropriate for the army, rather than the stuff that will guarantee me a win due to a rule loophole. I tend to play with like minded people and we usually have a lot of fun with troop heavy, low powered pitched battles without any meta-gaming or dirty tricks.

Theme: Clan Skryre Field Research Team

The Skaven Clan Skryre is known for their Warlock Engineers which are essentially mad scientists who are also wizards. Skaven have a surprisingly advanced steam-punk style technology which is mostly powered by magic. Their main energy source is Warpstone which is magically “radioactive” substance – a crystallized magic that warps and mutates everything it touches. The instability of magic, and Skaven shoddy workmanship makes their technology highly unstable. Their war machines tend to kill as many allies as they kill enemies. But it works out in the end because Skaven life is cheep and plentiful.

Clan Skryre

Clan Skryre is known for unreliable, unstable, explody technology.

My army is a Clan Skryre Field Research Team whose primary task is to “peer review” the technological achievements of other races or factions. The review is of course done whether without the subjects consent and frequently over their dead bodies. To achieve this task, the Field Unit has been equipped with a lot of advanced Clan Skryre weapons. The secondary mission is to field test these weapons, figure out how they behave in extreme condition, note how often they explode, and how many friendly deaths they cause on a monthly basis.

Core

Let’s start with the core, which is the heart of every army. In case you’re interested, 48% of the total cost (points wise, not dollar wise) is spent on core troops.

Primary Field Research Unit

The unit consists of 36 Clanrats armed with spears and shields accompanied by a Poisoned Wind Mortar.

Skaven Clanrats

36 Skaven Clanrats with full Command Group

The models are the plastic Clanrats from the Island of Blood set. I specifically picked the models that had a lot of armor to represent their status and fighting capability. I painted them red and yellow which are the twp primary colors I picked for my army. This is partly because they are considered Skryre appropriate, and partly because I like how they look. I knew I would be painting a lot of brown, gray and black fur so I wanted their clothes to be distinct, and also to stand out on the table.

In most cases, this is the actual core of my army and this unit is typically joined by the Warchief making it quite capable in combat.

Unpaid Interns

They are also known as Skavenslaves but I don’t like to call them that. The unit is 60 model strong and contains a musician and a Paw Leader. It looks really, really intimidating when I put it on the table.

60 Unpaid Interns

60 Unpaid Interns

The models are also from the Island of Blood set, but hand picked for minimum armor. They all are equipped with spears and shields because I like to have an option to add these if I need them. In most cases I field them “naked” with just hand weapons to shave of few points. I pained their coats yellowish brown color to set them apart from the Clanrats. Their weapons and armor are old and rusted to indicate that unlike the paid researchers they get worst equipment available. The rust effects were done using Typhus Corrosion technical paint.

The open secret here is that this is actually the weakest unit in my army. These guys cost less, and perform worse than giant rats. But due to the unit size, the way Skaven add their rank bonus to their leadership and the “horde” rule they actually become somewhat formidable in combat. Opponents often get scared of this unit and try to thin it out from afar via shooting, which is great for me because it means they’re not shooting at units that actually count. The inters can soak up an incredible amount of damage without actually impacting their fighting ability (which is basically close to zero).

Senior Research Fellows

A unit of 30 Stormvermin with full command group. They are usually lead by Warlock Engineer Babag who typically carries Warp Musket, a Doom Rocket and sometimes some magic spells. They also have an attached Doom Flyer weapon team.

Stormvermin

30 Storm Vermin with Warlock Engineer.

The models are basic 8th edition Stormvermin plastics. They are armed with halberds and shields. The Doom Flayer attachment is a mini-chariot type thing which has impact hits and extra attacks. These are my heavy hitters and they are typically joined by a Chieftain with a Battle Standard for an extra “oomph”.

This unit is currently a work in progress. As you can see, I primed them but did not have a chance to paint them yet.

Stormvermin look imposing but not overwhelmingly so. They are only marginally scarier than the Clanrats and this is partly by design. I don’t like to put all my eggs in one basket, and by presenting the enemy with two heavy hitting core combat units I force them to make hard decision. Ignoring either is perilous, and splitting fire between the two is ill advised because both units can soak up a lot of causalities due to their large size.

Lab Rats

A unit of 20 Giant Rats accompanied by 5 Packmasters on loan from Clan Moulder. The rats have been purchased on a Clan Moulder grant to research “better things to poke the rats with” technology.

20 Giant Rats

20 Giant Rats

The Packmasters are plastics from the Island of Blood set. You can actually buy them individually on eBay for almost nothing. The Giant Rats are actually vintage Marauder miniatures from the 80’s. The first rank with a lighter coat was actually painted by my brother ages ago when he was using them for Mordheim and I didn’t feel like re-painting them. I didn’t feel like repainting them so I just tried to match the color the best I could, though my rats are markedly darker. One of these days I will add some highlights that match the front rank.

Escaped Lab Rats

Four Rat Swarms on standard swarm bases. These are the smaller, inferior rats that are rejected from the grant program. The interns keep feeding them so they just follow the research teams wherever they go. Most of them think they are pets, though some actually think they are real Skaven and they even took to wearing tiny clothes and wielding tiny swords. This probably has nothing to do with the leak in the portable warpstone reactor under which they made their nest.

4 Rat Swarms

4 Rat Swarms

Some of these came in the Doomwheel set. I bought the rest on eBay in a bag. Someone was literally selling a bag of plastic rats for like a buck so I picked it up. They don’t look like much but they are unbreakable and can actually tie up the enemy units for a turn or two setting up some beautiful flank charges.

The Forward Recon Team

A group of 10 Night Runners armed with slings. Their task is gathering requirements for new projects, and also scouting ahead of the army.

10 Night Runners

10 Night Runners

They exist to annoy the enemy and take the heat of the core of the army. Their slings can do surprising amount of damage to lightly armored units, and they can easily block march moves or charges if they need to.

The models are old Gutter Runner plastics. My brother bought a box of them to use for Mordheim at one point and I inherited them later. He also managed to lose all the extra weapons that were in the set, which is why they have a mix and match type equipment.

Special

About 26% of my total point cost of the army is allocated into the special category. In most armies this is where all the cool stuff is, but with Skaven I did not actually feel the urge to max out this category.

Advanced Optics Research

Four Warplock Jezzail weapon teams. Their area of research is optics, and more specifically the “glass tubes what you put on guns so that you can shoot things far away”.

Four Warplock Jezzail Teams

Four Warplock Jezzail Teams

The models are vintage Marouder models that date back to (I believe) 4th edition. Back then the Jezzail teams had the pavis shields which is why they are not represented on these models.

Originally I have treated these models like a cheep version of the Dark Elf Reaper Bolt Trhower, but cheaper, stronger and less accurate. At short ranges this small unit is very deadly – especially to heavy cavalry. At long ranges however, their poor accuracy makes them rather ineffective. I’m currently working on obtaining models to double the size of the unit. Eight Jezzails should be a very formidable firing squad.

Maintenance Team

The field equipment maintenance team consists of four Rat Ogre janitors and two Clan Moulder Packmasters. They were brought on board in order to handle heavy equipment and carry heavy boxes, but they are also pretty formidable in combat.

4 Rat Ogres

4 Rat Ogres

Two of the Rat Ogre models (extreme left and right actually) are from the Island of Blood set, and so are the Packmasters. The second model from the left is an old metal Marauder cast from the 80’s, while the remaining one is from the last edition plastic set. I actually really like the miss-matched look this gives to the unit. I used my standard red and yellow color scheme on all the models. The Rat Ogres skin is painted with Bugman’s Glow and the scars and stitches are highlighted with Ratskin Flesh. I painted the Packmaster fur black to indicate their high status. I imagine the Clan Moulder only picks the largest and strongest Stormvermin for handling of large beasts such as Rat Ogres.

They are very intimidating on the field, that said they are a bit of glass cannons. They might look tough, but concentrated missile fire will cut them down real fast so they need to be deployed and moved carefully.

Meteorology Team

Ten Poisoned Wind Globardiers usually accompanied by a Warlock Engineer who study wind patterns. There have been some complaints that the chemical agents they use in their experiments are somewhat lethal if inhaled, so the entire unit was equipped with respirators just in case. They are sometimes accompanied by a Poisoned Wind Mortar

Poisoned Wind Globardiers

Poisoned Wind Globardiers

As you can see, the unit is still a work in progress.

The models are all current edition metal miniatures, with exception of the Warlock Engineer who was converted. The base model is a vintage Marauder death-globe warlock. I clipped his shoddy looking spear and replaced it with the high-tech looking Warlock weapon from the Island of Blood warlock. I also added the power-pack on his back from the same set.

This unit is rather versatile. Because their weapons ignore toughness they are excellent monster killers. I have also successfully used them to take down Imperial Steam Tank by simply drowning it in poison gas. The Warlock will sometimes have spells, but if I’m feeling especially nasty both him and the unit champion will be carrying a Death Globes.

Rare

Rare units compose 12% of my army.

Perpetual Movement Research

One Doomwheel used as a portable generator that also doubles as an excellent war machine.

Doomwheel

Doomwheel

The model is 8th edition plastic set, which in my opinion is the best looking incarnation of this model yet.

I have always loved the Doomwheel because it is basically the signature Skaven war machine, and the finest Clan Skryre invention. It is basically a giant hamster wheel used as a chariot. It has random movement, can easily spin out of control and it blasts warp lightnings at the nearest target (so usually a friendly unit) making it fun and hilarious addition to the army. Doomwheel related failures are always spectacular.

Advanced Ballistics Research

One Warp Lightning Cannon used as backup generator / heavy artillery.

As of writing of this post, I don’t actually have it put together yet, so no picture.

Similarly to the Doomwheel, I think the current edition plastic set is superior to previous incarnations, partly because of how intricate it is. This machine provides much needed long range support for my army.

Heroes

Heroic characters compose 15% of my army. You will probably note that all of my heroes are named after TV science personalities.

Project Leader, Chief Engineer Billnye

Billnye is a Warlord on foot.

Warlord

Warlord

The model is the Warlord from the Island of Blood set. I had to elevate him a bit by building up a pile of rubble on his base in order to make him fit neatly in the unit (his outstretched arms made it difficult to put him in a formation) so now he towers over his underlings. It is a really nice model, and it doesn’t really need much conversion work.

I typically field him on foot, with a halberd, tail weapon, poisoned attacks and sometimes a rat hound. I’m also considering building him a War Litter out of spare Skaven models.

Billnye usually hangs out in the Clanrat unit, and his sheer presence there is what makes people agonize as to whether shoot at him or the Stormvermin. He is pretty deadly in close combat against rank and file units, tough he usually struggles if challenged by tough heroes of other races.

Assistant Engineer Carrlsagan

A Chieftain upgraded to a Battle Standard Bearer with the Banner of the Underhive.

Battle Standard Bearer

Battle Standard Bearer

This is actually my most complex conversion in this army. I used a crouching body from a Night Runner set, and repositioned it so that it looks like he is resting his foot on a skull of a fallen enemy. The right hand is a banner staff from an old Mordheim set. The cross-bar with a rat perched on it and the tiny bell are from the Island of Blood Clanrat banners. The left hand and the shield on the back are spare parts from current edition Stormvermin box. The head was carefully clipped off a Clanrat unit champion from the Island of Blood set.

He is nowhere near as intimidating as Billnye, but then again he is not supposed to be. The Banner of the Underhive provides additional attacks to the already quite capable Stormvermin unit he usually joins.

Warlock Engineers Degrese and Tyson

You have seen them above in the Stormvermin and Poisoned Wind Globardier entries so I will not be re-posting pictures. Degrese is unmodified Island of Blood warlock, while Tyson is heavily converted (as described above).


This is my Skaven army. I don’t really have any more ideas for adding new units. Other than putting together one or two more large Clanrat units accompanied by weapon team attachments I don’t really see a point. And that in itself would be a bit boring. What do you think?

Army on the Table

Army on the Table

I will probably update this post at some point with pictures of painted and assembled models when I get them finished. As usual, questions and comments are appreciated. Do you play Warhammer? What armies? Do your armies have strong themes to them, or do you just pick whatever will win you games?

Let me know in the comments.

Posted in rpg and tabletop | Tagged | 4 Comments

Installing Arch Linux on the PogoPlug

Back in 2012 I wrote about how I set up a $30 linux server by installing Debian Squeze on a PogoPlug. I have been using the device for close to two years, but it died. I grabbed an identical replacement few days ago, but for some reason I was having trouble getting Debian working again, despite using identical device, similar thumb drive and following the same procedure. The truth is that Debian is not the best OS to run on this device. Pretty much everyone’s go-to system of choice for these devices is Arch linux which has excellent ARM support.

I’ve been itching to try Arch for a while not but I never really had an opportunity so I figured I might as well use it now. It worked amazingly well, so I figured it would be wroth while to document the procedure for future reference. Especially considering it is slightly different from the Debian procedure. I used this guide but with some significant alterations (see below).

Logging into the PogoPlug

First, you need to figure out the IP of your plug. Best way to do this is to log into your router and match it by name or Mac address. Once you know the IP address you can ssh into it using root as the username and ceadmin as password.

Preparing the Thumb Drive

The default OS on the PogoPlug is locked down pretty tight. Pretty much the only place with write access on the device is /tmp so you won’t be able to install to the internal drive (or rather it is fairly impractical to do). Instead you want to set up Arch on a thumb drive.

First, you will need to figure out which devices is the drive recognized as. I’m fairly sure the top-most USB port on the back of the device always registers as /dev/sda but you can easily check it by plugging it in and then running:

dmesg | tail

The last few lines should reveal which device the system thinks was plugged in. I’ll assume it was /dev/sda. First thing you want to do is to repartition it using fdisk:

/sbin/fdisk /dev/sda

Create two new partitions:

  • Press o to blow away all existing partitions on the drive.
  • Press n to create a partition, p to set it as “primary” and 1 to designate it as first
  • Hit Enter to accept the default starting point
  • Specify size using the format +[size]M where [size] is an actual value in MB. For example, I used +1536M designating majority of the space on my 2GB drive for my primary partition, and leaving 512MB for swap. If you have 4GB drive use +3582 and so on.
  • To set up second partition hit n, p, 2
  • Hit Enter to accept the default starting point
  • Hit Enter once again to use all the remaining space
  • Hit t then 2 to change the filesystem on partition 2 and use 82 (Linux Swap)
  • Hit a, 1 to make first partition bootable
  • Hit w to write changes to the disk

When you’re done the p command should return something like:

/dev/sda1   *           1         911     3501853  83 Linux
/dev/sda2             912        1018      411308  82 Linux swap

Since arch uses ext3 file system we will want to format the primary partition /dev/sda1 as such. Unfortunately the default OS on the PogoPlug does not ship with support for ext3 so we will need to download the mke2fs tool from the arch website and then use it to format the partition:

cd /tmp
wget http://archlinuxarm.org/os/pogoplug/mke2fs
chmod +x mke2fs
./mke2fs -j /dev/sda1
mkdir alarm
mount /dev/sda1 alarm

Installing Arch

Now we are ready to download the Kirkwood Arch binaries. The latest builds are close to 200MB in size, which was too big to fit in on the PogoPlug system partition. I recommend downloading it it to the newly formatted drive instead:

cd alarm
wget http://archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz

The official PogoPlug write-up on the Arch website tells you to use bsdtar to extract this archive. This may or may not work for you. I had major issues unpacking that way due to a locale mismatch and the UTF-8 encoding being used for file paths within the compressed bundle. Extracting the file the old fashioned way however worked just fine which is what I recommend you do:

tar -xzvf ArchLinuxARM-kirkwood-latest.tar.gz
sync
cd ..
umount alarm

Finally, download the U-Boot installer which will flash the ROM memory of the PogoPlug and force it to boot off the USB drive. Note that this step can brick the device (though I’ve done it a dozen times by now and never had any issues):

wget http://archlinuxarm.org/os/armv5te/boot/pogo_e02/pogo_e02.sh
chmod +x pogo_e02.sh
./pogo_e02.sh

Once this is done, reboot manually:

/sbin/reboot

If everything worked correctly the device should now boot into Arch. When the device reboots, log in with username root and password root.

Configuring Arch

First thing you will probably want to do is to update the system. You use the default Arch package manager pacman for that:

pacman -Syu

Next, you probably want to change a root password and add a new regular user for yourself (remember to add yourself to the wheel group):

passwd
useradd -m -g users -G wheel -s /bin/bash luke
passwd luke

The Kirkwood install is very bare bones and it does not ship with sudo so you will probably want to install it:

pacman -S sudo

Configure it with visudo and append the following to the end of the file:

%wheel      ALL=(ALL) ALL

This will give your regular user and all the other potential future members of the wheel group access to sudo command. At this point it may be a good idea to log out and log back in to make sure the user account you just created works, and that you can use su and sudo to elevate your privileges. If everything works, you may want to disable the remote access to the root account like this:

passwd -l root

You will probably want to change the devices hostname. On Arch this is done via the hostnamectl command:

hostnamectl set-hostname mypogoplug

If you’re on a Windows network and you want to be able to use the hostname instead of the ip address when you ssh you will need to install samba and give it a netbios name:

pacman -S samba
cp /etc/samba/smb.conf.default /etc/samba/smb.conf

Modify the smb.conf file to include:

workgroup = MYWORKGROUP
netbios name = mypogoplug

Now start samba and set it to start on boot:

systemctl start samba
systemctl enable samba

You should now be able to ssh into your plug using mypogoplug rather than the IP address from Windows machines. If you have Apple machines on the network and you want to be able to access them using mypogoplug.local then you will need to install two additional packages: avahi and nss-mdns:

pacman -S avahi nss-mdns

Now open the /etc/nsswitch.conf file and change the following line:

hosts: files dns myhostname

into:

hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname

Finaly, start the avahi-daemon and set it to be run on boot:

systemctl start avahi-daemon
systemctl enable avahi-daemon

At this point your device should be discoverable on the network and more or less ready to go for whatever purpose you may want to use it.

Posted in sysadmin notes | Tagged | 2 Comments

Minion Academy

Have I mentioned that the nemesis system in Shadow of Mordor was really cool? Because it was. Playing that game made me wander what else could be done with it. For example, I have always been fond of RPG oracles and general random generators for pen and paper RPG games. I am firm believer that every NPC and/or enemy, no matter how minor or unimportant should have a name and a few distinguishing features. A good game master can usually make up such details on the spot, but keeping track of dozens of throw away characters which may or may not die or conversely become important at some point can be difficult. So random generators are GM’s best friend – especially when trying to populate the game world with diverse collection of characters and not just standard “dwarf with brown beard, elf with blond hair” type stand-ins which is what you usually come with when you need to make up a character on the spot.

While there are dozens of random NPC generators, I figured I might as well write my own. It seemed like a fun and quick side project. How would one go about procedurally generating non player characters though?

First and foremost I figured it should be easy to modify and expand. Instead of hard coding values into the generator itself, I figured it should be stored as some sort of a structured list. I went with YAML because unlike many data serialization formats what claim to be “human readable” it actually is. Well, at least for me it is – your opinion may of course vary and it is not like YAML is without a lot of weird quirks. But I basically just needed a simple data format that could be easy to edit by hand, and that could be consumed by my code without doing a lot of parsing. Seeing how in Ruby can slurp a YAML file into an associative array in a single line of code, it was more or less perfect.

Moreover, I wanted my generator not to be “fully” random but rather use weighted probability scores for specific things. For example, it should be relatively rare to see a Rogue wearing a plate armor, but it would be common to see it on Warrior characters. How do you implement that? There is a few ways. For example you could find the discrete cumulative density function (CDF) of your list, generate a random number in the range between 0 and the sum of all weights, do a binary search to find this number… Actually, no. Scratch that. This is a solved problem and there is literally no reason to re-invent it other than as a classroom exercise maybe (or if you are worrying about performance). Instead of spending hours writing and debugging CDF code, we could just grab a gem such as this one and be done with it.

The basic idea was to let me write a weighted list like this in YAML (higher the number, the better likelihood the item gets picked):

race:
    Human     : 6
    Elf       : 6
    Dwarf     : 6
    Orc       : 6
    Goblin    : 5
    Halfling  : 4
    Hobgoblin : 3
    Kobold    : 2
    Ogre      : 2
    Troll     : 1
    
class:
    Fighter  : 4
    Soldier  : 3
    Cleric   : 1
    Bard     : 1
    Diplomat : 2
    Ranger   : 5
    Rogue    : 5
    Sage     : 1
    Scout    : 3
    Warrior  : 6

social:
    Commoner : 5
    Noble    : 2

Then in Ruby I could pull stuff out of it like this:

require 'yaml'
require 'pickup'
 
data = YAML.load_file('stuff.yml')
race = Pickup.new(data['race']).pick(1)
class = Pickup.new(data['class']).pick(1)

This was basically as complex as the code would get. As it is usually the case with this kind of projects the bulk of the work went into actually generating the data files that would yield not only a good deal of variety but also return both mundane and ordinary foot soldiers as well as funky and exceptional fun characters from time to time. It is more of a creative endeavor rather than programming.

What kind of weapons are appropriate for a rogue? What kind of armor should be worn by scouts? What color can Orc eyes be, and would this be any different for goblins? What kind of scale colors are most popular amongst the Kobolds? These were the sort of questions I had to answer while making this tool.

If you follow me on Twitter (as you should) you have probably seen me posting screenshots of the minions I was generating on the console:

This is back when I still had “barbarian” as a class which I later decided against including. Why? Well, to me it seems like every other class (warrior, rogue, bard, cleric, etc..) is something you choose to be. Barbarian, on the other hand is something you are. It is more often than not used to describe a social caste or grouping of people rather than a profession / calling. So I removed it and replaced it with Fighter and Soldier to have 3 solid close combat classes. In my mind warriors fight out of conviction (they have a duty, seek glory, want justice, etc..), fighters do it because they like it (they are the brawler, trouble-maker types that start fights in taverns for shits and giggles) and soldiers do it strictly for money.

Creating plausibly sounding names proved to be a whole separate problem. I knew that when it came to elves and Dwarfs, I could just shamelessly crib from Tolkien if I wanted to because there are billions of good names for both of these races in the Middle Earth lore. But I didn’t just want to have gigantic copy pasted lists. So I opted for something slightly more clever. I grabbed some interesting names, broke them into (usually) two parts, and then randomly recombined them. For example, here is a sample of Orc name table:

Orc:
    given:
        Male:
            prefix:
                grish: 5
                gor: 5
                muz: 5
                maz: 5
                lag: 5
                lat: 5
                lar: 5
                lir: 5
                rad: 5
                shá: 5
                rag: 5
                rat: 5
                urf: 5
                goth: 5
                núr: 5
                nir: 5
                fár: 5

            postfix:
                nákh: 5
                bag: 5
                gash: 5
                gnash: 5
                bash: 5
                mash: 5
                gol: 5
                mol: 5
                duf: 5
                buf: 5
                rúf: 5
                muf: 5
                dúr: 5
                grat: 5
                gnat: 5
                thrak: 5
                lúk: 5
                múk: 5
                mog: 5
                rog: 5

This particular selection can yield names like Grishnákh, Gorbag and Muzgash (all of whom are named characters from Lord of the Rings) as well as dozens more or less plausibly sounding names.

Most races have gendered first names and last names dictated by social status. So for example a noble’s name may include the name of their estate, or name of their father, whereas the names of commoners are typically nicknames or trade profession related. Elves, Hobgoblins and Trolls ended up with gender neutral names just because of how alien they sounded and because I wanted to have at least one group which did not have a concept of gendered names.

Once I had basic data files created, I wrapped it up in a bit nicer interface and started generating minions by dozens. It was interesting just to read their short descriptions and try to imagine how they would look and what their personalities would be. At some point I even noticed emergent little micro-stories popping up every once in a while. For example, here are two randomly generated Orcs I got the other day:

I found it interesting that they were both ambitious and feared losing face. It felt like they were connected somehow. Ragma was a noble born warrior while Mizni one was a commoner and a ranger. Possibly Ragma’s attendant and a guide? They were likely traveling companions: Ragma young, impetus, and irresponsible, but eager to make a name for herself. The older, wiser Mizni was likely appointed by her parents to keep the young warrior in check, and make sure she returns home safely from their adventures. They both driven by their ambition. Ragma wants to prove she can live up to the high standards of heroism set by her parents. Mizni wants to prove her value to the family by taking on a challenge of keeping the wild and irresponsible Ragma in check. You could literally write a short story about them, just based on this relationship.

This is the beauty of randomly generated content: sometimes a short little blurb can strike a chord with you and your imagination will immediately fill in the blanks creating interesting and meaningful relationships and scenarios. I figured it was worth sharing this little thing that I have done with others.

Minion Academy Screenshot

Minion Academy Screenshot

I set it up on Heroku cloud platform, and named it Minion Academy, mainly because I managed to snag that as a URL. So it is now up at minion.academy. When you visit the page you will get five randomly generated NPC’s and you can refresh the page for five new ones. It’s very basic, and still rather rough around the edges. There is still some work I want to do with it.

For example, I want to add more armor choices. Right now it’s basically just cloth, leather, chain or plate. I would like to expand it so that you could have a wide variety of different armor types for each of these categories. You might have also noticed there are no magic user types being generated right now. This is partly by design (I was initially trying to make a minion specific generator which kinda grew to cover all kind of NPC’s) but I’d like to add some wizards and sorcerers at some point.

If you notice a bug, I have the source code on Github so feel free to submit a bug report. As usual, let me know what you think in the comments.

Posted in programming | Leave a comment