ICRPG Gunk in your Junk, Part 3

Mecha crew in spaaaaaaace for more alt-Gamma World!

This is a play session set in Warp Shell using Index Card RPG Core. I play a team of five Mecha (Eve, Izzy, Keys, Fish, and Nate) through this scenario which I’ve adapted from The Albuquerque Starport by Paul Reiche III.

The Albuquerque Starport is from Gamma World Referee’s Screen and Mini-Module

Index Card RPG Core Set from Runehammer Games

Index Card RPG Vol 3

Rigaroga is a technologist lost in the wilderness, having adventures in geekery and nerdy mishegoss.

The Odd Order is a place for Rigaroga, friends and acquaintances to gather online.

If you’d like to pitch in, add a buck to the tip jar.

Or become an ongoing Patron, get gratis music downloads, and help me geek out!

ICRPG Gunk in your Junk, Part 2

Continuing alt-Gamma World with the Mecha crew in Spaaaaaaace!

This is a play session set in Warp Shell using Index Card RPG Core. I play a team of five Mecha (Eve, Izzy, Keys, Fish, and Nate) through this scenario which I’ve adapted from The Albuquerque Starport by Paul Reiche III.

The Albuquerque Starport is from Gamma World Referee’s Screen and Mini-Module

Index Card RPG Core Set from Runehammer Games

Index Card RPG Vol 3

Rigaroga is a technologist lost in the wilderness, having adventures in geekery and nerdy mishegoss.

The Odd Order is a place for Rigaroga, friends and acquaintances to gather online.

If you’d like to pitch in, add a buck to the tip jar.

Or become an ongoing Patron, get gratis music downloads, and help me geek out!

ICRPG Gunk in your Junk, Part 1

This is a play session set in Warp Shell using Index Card RPG Core. I play a team of five Mecha (Eve, Izzy, Keys, Fish, and Nate) through this scenario which I’ve adapted from The Albuquerque Starport by Paul Reiche III.

The Albuquerque Starport is from Gamma World Referee’s Screen and Mini-Module

Index Card RPG Core Set from Runehammer Games

Index Card RPG Vol 3

Rigaroga is a technologist lost in the wilderness, having adventures in geekery and nerdy mishegoss.

The Odd Order is a place for Rigaroga, friends and acquaintances to gather online.

If you’d like to pitch in, add a buck to the tip jar.

Or become an ongoing Patron, get gratis music downloads, and help me geek out!

ICRPG Hacky Sack Trial

This is a play session of a new, original solitaire Trial set in Warp Shell using Index Card RPG Core. I play a team of five Mecha (Eve, Izzy, Keys, Fish, and Nate) through this short scenario.

Index Card RPG Core Set from Runehammer Games

Index Card RPG Vol 3

If you would like to play this Trial, I have posted a write up of the scenario

Rigaroga is a technologist lost in the wilderness, having adventures in geekery and nerdy mishegoss.

The Odd Order is a place for Rigaroga, friends and acquaintances to gather online.

If you’d like to pitch in, add a buck to the tip jar.

Or become an ongoing Patron, get gratis music downloads, and help me geek out!

1-2-3-4 I Declare A Mecha War Trial

This is a play session of a new, original solitaire Trial set in Warp Shell using Index Card RPG Core. I play a team of five Mecha (Eve, Izzy, Keys, Fish, and Nate) through this short scenario of three challenges.

If you would like to play this Trial, I have posted a write up of the scenario

Index Card RPG Core Set from Runehammer Games

Index Card RPG Vol. 3

Rigaroga is a technologist lost in the wilderness, having adventures in geekery and nerdy mishegoss.

The Odd Order is a place for Rigaroga, friends and acquaintances to gather online.

If you’d like to pitch in, add a buck to the tip jar.

Or become an ongoing Patron, get gratis music downloads, and help me geek out!

Behemoth Trial

This is a play session of Behemoth, a solitaire Trial from Index Card RPG Core, in the Sci Fi setting Warp Shell. I play V-4E, a Mecha Tank, in this short scenario.

Index Card RPG Core Set from Runehammer Games

Index Card RPG Vol 3

In the video, I use OmniGraffle by Omni Group for the virtual tabletop playing surface, which I’ve used forever for my projects, just nothing like this before!

Prior to OmniGraffle, I used Lighthouse Design’s Diagram! on NeXT, so it’s a tool that’s been around for decades, in one form or another! https://en.wikipedia.org/wiki/Lighthouse_Design

Rigaroga is a technologist lost in the wilderness, having adventures in geekery and nerdy mishegoss.

The Odd Order is a place for Rigaroga, friends and acquaintances to gather online.

If you’d like to pitch in, add a buck to the tip jar.

Or become an ongoing Patron, get gratis music downloads, and help me geek out!

How to play the Hacky Sack Trial

I created this Hacky Sack Trial to play, as a follow-up to 1-2-3-4 I Declare A Mecha War, in a solitaire let’s play video which you can watch on my video channel. This is a micro scenario of three Moments for use in the Warp Shell setting of Index Card RPG Core. Here’s how you can play this Trial. You will need Runehammer Games’ Index Card RPG Core and may also want Index Card RPG Vol 3.

Hacky Sack

You’ve gotten stuck and cannot proceed on your overall mission. You have determined there is specific information you need to resolve your issue that is stored on a particular network. Finding that information will require accessing that network, travelling the network as virtual copies of yourself, locating and reading a particular file. You must go all hacky and sack it.

Setup: Create a character or characters in Warp Shell. Overcome all three Obstacles. If you are killed while connected to the network, make a CON check or die IRL. Optionally, if you are killed online, you are disconnected and incapacitated IRL for 1d6 ROUNDS, leaving you unable to move or take actions, vulnerable to whatever is happening around you, including being attacked or killed again IRL, you St00pid N00b!

Screech-Warble-Warble: Target 10. Heroes must find and use a physical network access point, then decide who all will enter the network and who, if any, will stay behind to physically protect the vulnerable hackers while they are virtually travelling. This takes an action at the physical access point and moves the hero to the I/O node on the network map. Optionally, connecting to the network might require a 1 HEART challenge for each hero going virtual, and connecting may be something that can only be done one at a time, requiring the first heroes on the network to enter alone.

Hacky Sack: Target 11. Heroes enter a network at the physical I/O node. They must find a STR node where a particular file must be found, a Perception check. They must use the Read action to determine the contents of the file, a 1 HEART challenge. While the heroes are engaged in these activities, a TIMER counts down to when enemy Ice program spawn at a network ACC node, where they will explore the network seeking intruders to attack using Delete actions, or specialized programs if they have them.

In my example run, the heroes were also held captive within a lab, behind a locked door. The heroes had the secondary, necessary task to enter the IOT node which controlled the door lock, and succeed at a 1 HEART challenge to Update the lock, to set it to unlocked.

+++ATH0: Target 12. Heroes must leave the network, and return to their IRL bodies. This takes an action at the I/O node on the network map, and move the hero back to their actual map location. Optionally, disconnecting from the network might require a 1 HEART challenge for each hero leaving the virtual map, and disconnecting may be something that can only be done one at a time, requiring the last heroes on the network to stay behind, holding the flank, increasingly alone.

Hey! Wait! Don't pick up the ph{#`%${%&`+'${`%&NO WARP SHELL

Conclusion: You have succeeded in finding the file you sought, and now have the information you needed. Not only did the file solve your showstopper issues, it also contained the location and access code for a lonely Warp Shell awaiting worthy passengers at the nearby spaceport, which may also contain 1d4 chests of Warp Shell loot in its hold. Optionally, if you’ve already got access to your own Warp Shell, you instead find the location of a shipment of 1d6 chests of Warp Shell loot that has become lost in a forgotten storage unit at the starport.

Type of Nodes:

These are the node types I used for this Trial.

CPU is a machine on the network. Could be represented by a d20 placed on the map.
HUB is an interconnect, or empty room. Could be represented by a d12.
I/O is a physical, direct access port, where players or rival hackers can enter the map. Could be a d10.
ACC is a system access node, a virtual or network point of entry for units coming from a larger outside map. Could be d8.
IOT is a device, an Internet of things, connected to the network, like a door or camera control point. Could be a d6.
STR is a storage location, where files can be found. Could be a d4.

There are six node types, so one could simply roll a d6 to determine a new node to place, if one wanted to randomly create a network. Interconnections between nodes could be represented on the map by toothpicks, paper clips, bobby pins, or soever. One might also use Looney Labs Pyramids for nodes and interconnections, which would be cool. Here’s a representation of the map from my video using dice and pennies for the map on a tabletop (though as I look at the image, I’ve accidentally swapped suggested die for some nodes. Oops!).

For the purpose of moving, the current Node a character is at on the map is CLOSE. Any Node directly connected is NEAR. Nodes connected to NEAR Nodes are FAR. Visibility from a Node includes each NEAR node. Movement to a NEAR Node allows for an Action. Movement in a Dash to a FAR Node precludes an Action. In all other aspects, Nodes act as discrete rooms, about which normal, physical room-like moves and actions can be taken.

I have not yet brainstormed how to represent the wider outside network, whatever one calls it: Internet, Matrix, Cyberspace, Aethyr, or soever. Maybe I’ll do another Trial in future to explore that! One thing that occurred to me was using something like cards Steve Jackson Games Illuminati to create a large map of bizarre organizational networks to attack and play around in, but that’s probably not specifically an ideal theme for Warp Shell. Probably cooler to keep it more abstract, like another chance to use Looney Labs Pyramids. Optionally, one might consider this part, the travelling between maps, as something similar to how a Warp Shell travels from place to place, simply by showing up, folding the locations together, without bothering with the intervening path.

Types of Actions:

There are four basic actions one can take on things on the network.

Create makes something from scratch, like crafting or summoning.
Read reveals the contents of something, like perception or deciphering.
Update makes a change to something, like persuasion or intimidation.
Delete removes something, like attacking.

In this example, I really only used Read and Update, to reveal the contents of the file the heroes found, which contained their Giant Mecha instruction manual and a bonus bit about how to find their new Warp Shell and to unlock the lab door. If the heroes had encountered the Ice spawned, they could have attempted to Update the Ice’s programming to “persuade” or “charm” it to stop attacking, or to target another Ice program, and so on. The heroes might have attempted to Delete the Ice, essentially an “attack” using their weapon or magic programs, their skills or loot. The heroes may also have attempted to Create a firewall or an ally program, based on some kind of magic or skill they possess, which would cast or summon something IRL similar.

Various upgrades and programs, and class or bio-form bonuses or disadvantages might apply to various basic actions. I didn’t explore what that might have looked like, but perhaps there would be some kind of permissions that were required. For example, perhaps a Lock file would have to be Deleted before a target file could be Updated. Or, perhaps, a permissions bit must be Updated before any Create actions could be taking in a particular Node on the network. I didn’t explore these ideas in the example run, but it could lead to interesting or puzzling complications for players.

Class or Bio-Form:

I didn’t use these, but I brainstormed a few class/bio-forms purely from the world of this scenario.

Programmers, whose leader type is Lead, has +2 create, +1 update, -1 read, -2 delete bonuses.
Users, whose leader type is Manager, has +2 read, +1 delete, -1 create, -2 update bonuses.
Data Entry, whose leader type is Analyst, has +2 update, +1 read, -1 delete, -2 create bonuses.
Admin, whose leader type is Superuser, has +2 delete, +1 create, -1 update, -2 read bonuses.

I don’t know what “leader type” means. Perhaps a leader type, a kind of Boss version of each type, would have +1 added to each of their natural actions. For example, a Lead would have +3 create, +2 update, 0 read, -1 delete bonuses to each action type, respectively.

Ice:

IC, or “Ice”, are Intrusion Countermeasures, or programs that are on the network to destroy hackers, like the heroes. In order to implement an Ice, just take any enemy from Core and remove the vowels, converted toupper(), then add an “.EXE” at the end of its name. Everything else functions as it would otherwise, but provide colourful narration to make the effects of actions have a “cyber” twist.

In the example, I used the Goblin from Core, renamed as an Ice GBLN.EXE program running on the network. In the example, I had a threat timer that spawned Ice at the ACC, network access point. Ice could be stationed or mobile, just as any monster would be. Additionally, I improvised that Ice can see activity in any adjacent node on the local network, for the purposes of going aggro, raising an alarm, or soever.

In my example run, all enemy Ice that spawned were GBLN.EXE, essentially identical to Goblins from Core, but a virtual “program” version. I also had BR_WRM.EXE (Bore Worm), BRN_HRR.EXE (Brain Horror), CRRDR.EXE (Corroder), and FLMS.EXE (Flimes; oh gods, not Flimes! Please, anything but Flimes! Send me to Detroit!) Ice held in reserve as other possible monsters to spawn, but didn’t end up using them.

IRL Tactics

One element possible, that I didn’t explore, is that the character were not being guarded IRL while they were jacked in. This could be an important aspect of play, which would necessarily “split the party” and allow various hijinks to ensue. In the first and third Moments of this Trial, the party might have to deal with various IRL confrontations before, during, or after the events occurring in the middle, online, Moment.

Also, IRL characters might have particular technological “decks” they must use to jack in, which could have advantages and disadvantages. In the example, I allowed the Mecha to have built-in means of connecting, or at least the Mecha Zurin had appropriate cables and dongles on his meditation chain. But, getting connected could require several IRL steps, a HEART challenge, and/or a kind of puzzle player must confront, especially for unfamiliar, or even literally alien to them, technology.

How to play the 1-2-3-4 I Declare A Mecha War Trial

I created this 1-2-3-4 I Declare A Mecha War Trial to play, as a follow-up to the Behemoth Trial, in a solitaire let’s play video which you can watch on my video channel. This is a micro scenario of three Moments for use in the Warp Shell setting of Index Card RPG Core. Here’s how you can play this Trial. You will need Runehammer Games’ Index Card RPG Core and may also want Index Card RPG Vol 3.

1-2-3-4 I Declare A Mecha War

A plague of Behemoths ravaged the planet, showing up like cicadas, all at once, in many different places. The heroes are awakened from their merely robotic dreamtime into sentient Mecha consciousness by the attempt to process this overwhelming chaos. Each hero was sent out to battle a Behemoth and survived, where so many others failed and fell. After their success, each was brought to the same lab where they were augmented in some mysterious way, and find themselves together as prisoners being used for these experiments.

Setup: Create 5 Mecha bio-form characters in Warp Shell. Overcome all three Obstacles. If you are killed, you can be rebuilt; but will have your mysterious augments removed and will have all your parts and pieces abandoned as a failed project, dumped on a pile of other robotic trash.

The Last Behemoth: Target 10. Suddenly an alarm is raised, and you are sent into battle. The last Behemoth has been sighted heading this way. Once in position, you feel something strange happen. Each individual hero starts to be drawn toward the others, and arms, legs, even bodies begin to alter and transform. After much contortion and connecting, the heroes have formed a Giant Mecha, a vehicle with 5 chunks. Each player takes their TURN, using Actions whatever they are able; but all must move together as one unit. Defeat the Behemoth, a 4 HEART creature, who will charge in order to ram, and then continue to physically attack the Giant Mecha until one or the other is dead.

When the Last Behemoth is killed, the next Moment begins. Optionally, start a Countdown Timer for the next Moment. The Death Droid will target the Last Behemoth until defeated, and then go after the heroes.

The Death Droid: Target 11. Frightened Powers That Be, not aware of the Giant Mecha project, have sent a Death Droid to track down and destroy the Last Behemoth. The Death Droid, a 5 HEART creature, with one ranged weapon, was programmed to locate and destroy its target, which has now become the Giant Mecha. The Death Droid will attack at range until its last HEART, at which point it will attempt to close distance in order to ram.

When the Death Droid is killed, the next Moment begins. Optionally, start a Countdown Timer for the next Moment. The Giant Robot will target the Death Droid until defeated, and then go after the heroes.

The Giant Robot: Target 12. Like the proverbial spider sent after the fly, frightened Powers That Be have sent a Giant Robot following after their Death Droid, to destroy each other after dealing with the Last Behemoth. The Giant Robot, a 6 HEART creature, with 2 ranged weapons and 2 attacks, will attack at range until it reaches its final HEART, at which point it will attempt to close distance in order to ram.

The Giant Robot can overheat, just like the Giant Mecha heroes, so that unit also begins with a 1d6 Heat Counter.

Optionally, when the Giant Robot is defeated start a final, end of scenario Countdown Timer for an explosion that inflicts Ultimate damage to all Near units as the Giant Robot is remotely and completely annihilated by the Powers That Be. (Heroes better hope they are not overheated and stuck unable to move out of the blast radius!)

Conclusion: Managing to defeat all opponents, the Giant Mecha formed by all five heroes disconnects, leaving each in a daze on the battlefield. Teams of technicians come to collect you while you are incapacitated, unclear how the Giant Mecha augment is activated or deactivated, and return you to captivity in the lab while they pore over the data gathered from this field test.

Ramming:

This Trial uses the vehicle rules provided in the Speed Kills adventure from Core as a mechanic for a Giant Mecha battle. When ramming, treat each as a vehicle with HEARTS equal to CHUNKS, and visa versa.

Taking Damage:

Damage taken by the Giant Mecha is spread evenly across all players, through some function provided by the augment connection. Giant Mecha will remain a 5 CHUNK vehicle until it takes 5 HEARTS of damage, at which point all characters will disconnect and become individuals with 1 HEART left.

Optionally, instead, as the Giant Mecha takes each full HEART of damage, one character is forced to disconnect from the whole, becoming an individual with only 1 HEART remaining. Disconnected characters act independently, and cannot reconnect to the whole.

Optionally, as a unit, Giant Mecha or other, takes damage, its number of remaining HEARTS also determines how many CHUNKS count for ramming. Thus, the more damage a unit takes, the less damage it is able to inflict. Otherwise, each unit retains its full initial CHUNK count when ramming.

Overheating:

As Giant Mecha and Giant Robot fire their energetic weapons, they increase their heat levels, similar to the Dynamic Dice rule for Spell Burn. For example, using a Duranium Blade will not increase heat levels, but firing a Pulse Rifle or using an Energy Blade will. Place a d6 on each unit, set to 1. Each discrete energetic weapon attempt roll, whether successful or not, will increase the heat counter by 1.

When the counter reaches 6, the unit must make a CON check against the Target. Success will reset the counter to 1. Failure on this check will overheat the unit for 1d6 ROUNDS, during which time the unit is incapacitated, neither able to move nor take action.

If a character holds all actions for their TURN, decrease the heat counter by 1. If a character takes any action, but does not fire an energetic weapon, the heat counter neither increases nor decreases.