The first snag I hit was that I was expecting to be able to download pre-generated characters at the last moment. Yeah, that didn’t happen. I couldn’t find pregens anywhere, which seemed way weird. I’ve never looked for pregens that weren’t to be had.
That meant the the group got to roll their own pcs which is a surprisingly involved process. It was fun though– at least it was for both Schlock fans and myself. The 4th member of our party was so bored by the process he went to sleep.
Interestingly, while the book wants you to pick your Command Package, Background and Sophont type in that order, all of my players picked their sophont type first and went from there. They also picked the sophont types of their fireteams and named each grunt. Personally, I love that naming conventions have a chapter in the book which contains long lists of sample names.
We ended up with a Tausennigan Kss’thrata Captain with a crime lord background, an Esspererin Engineer with a driver background, a Kreely Doctor with a medical professional background, all appropriately named. Here came a snag that I missed til later. Endurance and Inspiration are both very important skills. One affects HP and the other dictates the usefulness of your fireteam. Because I missed that, and then failed to inform my players, 2 were fragile from the get-go and only 1 (the Captain) put points in Inspiration, meaning he was the only one who got real use from his team.
Then came gear shopping. The adventure I was running had given them a ship already, though I bumped up the AI rating to fit with the suggested starting company statistics from the creation portion of the book. I subtracted the appropriate resources but they still seemed to have plenty to shop with. Here was another snag. The Captain paid for a fancy gun and eschewed armor. This made him almost impossible to miss in a firefight. But it gave his fireteam a chance to shine!
Howard Tayler has been working on Schlock Mercenary for 18 years and 18 books. The depth of his universe is easy to see and appreciate with a read through the Planet Mercenary core book which spends plenty of time on locations and characters and not much time on the rules. This works well because the rules of the game are pretty light. Fast and fun is what they were going for.
- 3D6 system with both targeted and graded checks
- Mayhem card flips that trigger automatically on certain rolls to introduce . . . MAYHEM
- Roll Play Points that allow re-rolls, Mayhem negation, and sacrifice of a grunt for “Ablative Meat Shield”
I ran The Damaxuri Deception, the sample adventure contained in the core book. It opens with the pcs attending MercCon, which is being held at the dilapidated space station Highport, in orbit above Damaxuri. There is a surprise announcement of a high-paying bounty on the notorious arms dealer who is conveniently dirtside and the pc’s compete with other mercs to collect.
It’s divided into 5 scenes, each of which has a few goals for the Game Chief, a suggested time frame, a list of notable npcs present and a list of possible outcomes.
The first scene went pretty well. Our captain conned a merchant out of some explosives, while our engineer went straight to petty theft and made an underground contact. I made another mistake here with the contact and gave her the arms dealer instead of the fence as her contact– no one knew, or course. Both players seemed to enjoy themselves, while the 3rd, sleepy, non-fan was obviously bored and outspoken about not wanting to be part of a criminal gang (even though that sort of attitude is frankly unusual for that player’s pcs whose general play style is chaotic nuetral and often bordering on evil.)
The merchant the Captain conned dropped a hint about the upcoming bounty and Engineer’s contact pointed that merchant out as suspicious, I was trying to encourage them to take the tip seriously and look into it, but I didn’t pique their interest enough. Consequently they didn’t get any sort of head start on the upcoming rush.
As they moved to the advertised key-note address they saw a few species specific companies in the crowd– namely a group of Esspererin and a group of Ursumari (both of which I included because of the next scene). When the announcement was made about the bounty they didn’t start moving until they saw other companies move, but then the Engineer went into high gear.
She told the guards that one of the Esspererin crowd stole something from the merchant, effectively blaming her crime on one of them. That tangled them up in red tape and as the pcs moved to their ship they saw more Esspererin nearby wondering where the heck their captain was because they obviously couldn’t leave without her!
Once aboard ship, they became one of many headed to the planet. Again, the Engineer moved to flood local news with tales of a bounty already collected. Then she targeted a nearby ship’s AI, making it skate too close to a 3rd ship which fired a warning shot.
Confusion sown, they had their head start and we were in Scene 2 which is a ship combat/chase. The system is nifty in that all of the players get to take turns with controlling the ship. One thing I didn’t quite grok was the way the ship is powered– but I frankly just skipped over that part and let the pcs use all of their systems.
They’d effectively cut out all but one of the ships in the scene– the Ursumari “Advancing Ice”. The Captain’s Military History roll told him that the Ursumari might fire on them and he tried to hit them first with a very nice roll– and missed. At this point, looking at the stats given, I realized how badly the pcs were outgunned.
Ship combat doesn’t use the pc’s stats because the ship’s AI is doing the fighting. (There are some lovely AI rules that didn’t get utilized.) Even though I bumped up the rating to 3 from 2 on a max roll they’d be hitting with a 21. There are auto fails in the game but not auto successes. The “Advancing Ice” had a basic defense rating of 20 while the pcs had a basic defense rating of 13.
So the adventure says that if the pcs are beaten by another ship they can be stranded in space or they can be marooned in the desert on the planet below, but then it abandons you to the realm of making stuff up as you go along.
So . . . I had the Ursumari captain contact them instead of engaging them. To ensure that they realized they were outgunned, I had the captain eating yogurt and poking fun at them. He suggested that they didn’t want to meet up with him again.
The Captain, meanwhile, told the Ursumari that his illiterate Doctor had been the trigger happy culprit. This ired the Doctor.
Scene 3 consisted of 2 fights when 1 would have done just fine. I opened with them landing on the planet and needing transportation around the city. They went to rent a vehicle, but the only thing available was a limotaxi which was 3 times the price of a regular car. The Captain haggled brilliantly and got it for the same price as car. The Polyflorian behind the desk took a liking to him, to the amusement of all.
A computer hack gave them a destination (with no chance for it to be the right destination) and off they went. Here, I had an issue. The engagement was to take place at a warehouse and the adventure gives zero setting information. Granted this is not a tactical sim. There is no map and mini set up. Still. I could have used some direction! (And this from a gm who does run many theatre of the mind rpgs.)
The opening salvos of 3 pcs vs 9 henchmen showed up the Captain’s lack of armor. In came Ablative Meat! The Captain’s purp Danskin threw herself into the line of fire for him again and again and again. Each time there was a 50% chance she’d die. Each flip of the coin sealing her fate had 3 of the 4 of us on the edge our seats. The Captain also went down in this fight when he ran out of tokens to pay for Ablative Meat and the Doctor saved him. This was sad, because the Captain’s player was my Maxim Quoting Player! I didn’t want him to run out of RiPP tokens, but it happened.
One rule I did really like, to the point of ripping it for other systems, was that if someone is dead and their team can get to them and heal them that round, they live. It makes death a point of player agency– and not the dead pc’s player,
Also, in came the explosives conned out of the merchant in the first scene and mayhem. The first grenade was a dud due to a mayhem card. Another2 mayhem card later let it go off, ending the fight, which was pretty satisfying. The Engineer used the limotaxi to mow down the opposition and at one point flipped a mayhem card that let her juryrig it to greater lethality to everyone’s amusement.
The adventure then says, “At the end of this engagement, the players will know which location to visit next.” Really? Okay then.
That done, and with little in the way of direction from the adventure, the conned merchant commed the Captain with more direction, which they took and now they were finally trying to figure out what was going on. The Doctor’s player outlined a solid theory as he finally seemed to get invested and then he rolled an Insight check. Insight being a skill which basically lets the Game Chief feed the players information.
Of course, their transportation was trashed, so the Doctor called the rental agency and the Polyflorian with a crush on the Captain came to the rescue. After altering the records and renting the trashed vehicle out to someone else, she picked them up and delivered them to the next scene. Then the Doctor’s player emotionally checked out again.
Again, with very little in the way of scenery to go on, the Engineer took to flight and got an enemy count, the layout of this new warehouse, the possible location of the bomb the merchant told them about and a look at their target who was in some heavy duty armor (think Iron Man). That was nice because, “During the engagement, the characters will
find the bomb.”
She came back to relay the information as the Ursumari arrived. Though less than thrilled with the presence of our pcs Captain Murderbear cheered up considerably when the Engineer gave him some frozen yogurt she’d thought to buy when they first arrived dirtside. He wanted to hire her. And the doctor. And maybe the company’s ship too.
This got the Captain irritated but the Engineer suggested that they all work together to save the day. So this was essentially the same fight but the henchmen had more firepower and there was a bomb and a villain. So maybe it wasn’t the same fight. But it felt similar to me.
The Engineer made short work of the villain by hacking her suit as the Captain and fireteam sniped the muscle and the Doctor was supposed to take care of the bomb. The player let the npcs take care of the bomb instead. Huzzah for engagement.
I required 3 checks (which was how the bomb was supposed to be disarmed) from the Engineer and she made them. Danskin saved the Captain more times– to the point that her survival was making us cheer and the Engineer’s player was begging the Captain’s player to stop risking Danskin’s life. (I will be making people roll dice next time though– I think those coins are weighted.) The Captain went down again and as he plummeted to certain death the Engineer made the suit save him. The npc showed off the bomb and the pcs pointed out that it would have killed Kostavi’s henchmen, which resulted in them surrendering.
It was some fabulous play and I didn’t see it getting better. I was also a bit tired of the adventure fuzziness and the player conflict and the one pc who kept letting it be known that he wasn’t happy with . . . anything. So.
“By now the bomb has either gone off or not gone off — the players have resolved the explosive situation either way. If Kostavi is already dead or captured, then twist the plot by saying you killed her body double.” Then follows a chase scene done in skill checks and the direction, “The players should succeed at getting Kostavi, because the thrill is in the journey here.”
They already had Kostavi. I could run the chase scene. I opted not to. I brought their merchant contact in with the officials and they discovered he was an undercover agent (not the villain they half expected). They collected the bounty and he added a sweetener. The Doctor ran off to get a job in law enforcement and instead of offering to run a second adventure I gave up.
The game has some lovely bits. I’d recommend it to anyone who loves the comic it’s based on. I’d recommend it to anyone who loves comic space opera. To anyone looking for a way to tell a non-gritty scifi story. I’d run it at a con.
It has bumpy bits. I need to reread the bit on space combat. Someone needs to post pre-gens! The adventures, I’d sadly say, are not up to par. They assume too much for my liking and give too little in the way of meat. Very bare bones, but bare bones in a way that kept getting in the way of my fun instead of enabling it. I think this system would do better in a situation where the player’s are directing the story at as leisurely a pace as they wanted.
It was a less than ideal, but educational, situation. Lack of player buy-in is something I’m ultra-sensitive to and I’m not sure I can afford that sensitivity with the addition of a player to our group that refuses buy-in so adamantly.