GRAPPLE: You can attempt to physically wrestle and restrain an opponent by attempting a Might task. Once a grapple has been successfully initiated, all physical actions are treated as opportunity actions requiring a Might task to attempt. A character can attempt to break out of a grapple by succeeding on a Might task as an action (without needing to make the opportunity check). Characters in a grapple defend at +1 difficulty.

(So if you’ve been grappled and wanted to throw a dagger at someone, you would need to first succeed at a Might task in order to gain the opportunity to throw the dagger. If you’re grappling someone who wants to punch you in the face, you would get an opportunity action to attempt a Might task to prevent them even trying to punch you.)

If multiple characters are grappling a single opponent, you can use the standard rules for helping. (The bonuses from helping would also affect the Might task for the opportunity action.)

FOCUSED GUARDING: If you’re attempting to stop a specific character from attempting a specific action (“I tackle him before he can run out the door!”), you can attempt a Speed task at -2 difficulty. On a success, the character you’re targeting will be prevented from taking the indicated action.

DESIGN NOTES

There are no rules for grappling presented in the Numenera rulebook. The closest you’ll get is a special ability possessed by a monster called a chirog, which looks like this:

Chirogs do not use weapons or tools, usually attacking with a savage bite. However, they can also grapple a foe, which is just like a normal attack except that rather than inflicting damage, it holds the foe immobile. The foe can take only purely mental actions or struggle to get free (a Might task at difficulty 4). Both the grappling chirog and the grappled foe are easier targets for other combatants, with attackers gaining a two-step modification in their favor.

At first glance, this looks like a decent place to start if you’re looking to make a ruling for grappling in Numenera. Unfortunately, upon reflection it turns to be fairly unbalanced as a generic mechanic. For example, the chirog’s ability is even better than stunning an opponent: Stunning means that you can’t take an action next turn and you defend at +1 difficulty. Chirog-style grappling means that you can’t take an action next turn, you defend at +2 difficulty, and are at risk of having the effect continue unless you succeed on a Might task. There is a trade-off insofar as the person initiating the grapple also suffers a +2 difficulty to defense, but since stunning also requires a much greater expenditure of resources than the single action required by chirog-style grappling it’s pretty clear that chirog-style grappling would be broken as a generic mechanic.

So I instead took chirog-style grappling as a loose guideline and improvised on a similar theme. When I was done I discovered that I had inadvertently created something pretty reminiscent of my Super Simple Grappling rules for D&D.

The rules for focused guarding are a bit more experimental. My basic thought process there is that, by the rules as written, a character can perform a Guard action which allows them to specify an action and prevent anyone from attempting it by making a Speed roll at -1 difficulty. Ergo, I’m concluding that stopping only a specific character from preventing that action should be easier. (So you can stop that one specific guy from running through the door, but all of his friends will still be free to do so.)

It may be too powerful, though. I’m specifically eyeballing the scenario where the PCs are fighting a solo monster. I’ve suddenly made it flat-out easier to counter that monster’s actions. So something to keep an eye on.

Some quick mechanical background for people unfamiliar with Numenera: In this system, you deal flat damage based on the type of weapon you use. (A light weapon does 2 points of damage; a medium weapon does 4 points of damage; and a heavy weapon does 6 points of damage.) You can increase the amount of damage you inflict by exerting effort or by rolling well on your attack roll. And, finally, you subtract the target’s armor value from the damage inflicted before applying it to their health pool.

This means that the key armor values in Numenera are 2, 4, and 6: At armor 2, you can’t hurt it with a light weapon unless you use effort. At armor 4, you can’t hurt it with a medium weapon unless you use effort. And so forth.

Now, let’s talk about items: Items are assigned a health pool and an armor value. The armor value for an item can be 1 (hard objects), 2 (very hard objects), or 3 (extremely hard objects).

This means that, mechanically speaking, the game is asking the GM to make an assessment: Can you hurt this with a dagger? Can you hurt this with a dagger if you use some effort?

Once you express it in those terms, it becomes pretty easy to see that, objectively speaking, the system is producing really unrealistic results. (If you’re wielding anything larger than a dagger, you’re going to be able to break literally anything in the game world. And you are probably going to be able to break it very quickly and with very little effort.) And from a mechanical standpoint, it would be much more interesting for the GM to have a richer panoply of assessments to trivially choose from.

My recommendation is to set the object armor values at the key armor values indicated above:

When characters want something in the Eclipse Phase universe, they hit up their social networks: PCs will make a Networking test to reach out through their friends, associates, and the sophisticated software that binds society together in the year 10 AF. And if they find someone who can help them, they’ll ask for help based on the reputation they’ve built for themselves.

In short, they’ll call in a favor.

But if the PCs are constantly reaching out to other people, doesn’t it make sense that people would also be reaching out to them? They’re skilled, well-connected, and possibly even well-known. Just the sort of people you’d want to ask a favor from.

The system presented here is a tool I’ve designed for an open table Eclipse Phase campaign I’m currently developing, but it should prove useful for almost any Eclipse Phase GM. The idea is to create unexpected complications (and synergies) by having the social networks of the PCs organically interrupt their lives.

RANDOM REPUTATION FAVORS

Rep Network Check: Each PC has a 2 in 10 chance of being contacted for a favor each session.

The GM should make this check at the beginning of each session and note which PCs will be receiving a request. These requests won’t necessarily happen immediately: The GM should decide during the course of the session when the call comes.

Optional Rule: If the initial rep network check indicates that a PC will be contacted for a favor, immediately roll another check to see if they’ll be contacted for a second favor. Continue rolling until they actually fail a check.

GENERATING THE FAVOR

1. Determine Reputation Network. Randomly determine which of the character’s reputation networks is making the request.

2. Determine Solicitor. Determine who’s requesting the favor by rolling on the Solicitor table. Note that this can be an opportunity to develop the PC’s personal life for play. For example, if the table indicates that the request is coming from a friend that doesn’t necessarily mean that it’s a friend who has been part of the campaign before.

3. Determine Favor Level. Determine the level of the favor being requested by rolling on the Favor Level table.

4. Determine Type of Favor. Roll on the Type of Favor table to determine the type of favor being requested. The exact nature of the favor is heavily dependent on the particular circumstances of the character and the campaign; the table is merely designed to provide a general idea that can help serve as a creative seed for the GM. Reference the favors tables on pages 289-290 of the Eclipse Phase rulebook to determine the scope of the favor being requested (based on the level of the favor).

Information: This can either be information that the character already knows or information that they are capable of finding out. (It could also be information that someone just thinks they know or can find out.)

Introduction: The solicitor would like the PC to introduce them to someone they know. At trivial levels, this is the digital equivalent of passing business cards. At higher favor levels, a physical meeting is likely (and, obviously, the person they want to be introduced to will be of some importance). If the PC agrees to make the introductions, don’t be afraid to let the consequences splash back on them. (“What the hell did you get me into?”)

Skill: Somebody would like the PCs to use their unique skills. You can randomly determine which of their skills is desired or simply choose one. Obviously this can range from the benign (“can you prepare a précis on the most recent discoveries in xenoarchaeology?”) to the criminal (“I need you to rescue my sister who’s indentured in a brothel”). Make sure to take note of the terms of service listed on the Acquire Services table (EP, pg. 290) – this favor could actually be a long-term job offer.

Delivery/Pick-Up: At low favor levels, this is most likely going to be a matter of convenience. For example, the PC happens to be standing outside a Coffee Star franchise and somebody a couple blocks away wants a latte. At higher levels, it becomes increasingly likely that the pick-up or delivery requires some special skill the PC possesses.

Transportation: Similar to the delivery, except in this case it’s someone needing to be delivered themselves. If the PC doesn’t have access to a vehicle, then it might be someone looking to hitch a ride in their ghost rider module. Or asking them to deliver a portable server filled with enslaved infomorphs.

Use of an Item: The PC has something somebody would like to borrow for a bit. They’ll give it right back. (Honest.) At trivial levels this is again likely to be a matter of convenience. (“Hey, I’m just across the plaza. The local spime spotted that you had a utilitool. Could I grab that really quick to fix my glide sneakers?”) At higher levels, it’ll be something expensive or the use of which the PC might need to supervise.

Buying an Item: The PC has an item that the solicitor would very much like to purchase. Pretty straightforward.

Selling an Item: The solicitor has something that he thinks the PC might be interested in. Wait… why does he think the PC is the sort of person who needs large amounts of explosives?

Borrow Money: 50 credits for a trivial favor; 250 credits for a low favor; 1,000 credits for a moderate favor; 5,000 credits for a high favor; and 20,000 credits for a scarce favor.

REWARDS AND PENALTIES

Cyberpunk Alley Pub – Brosa

If a character refuses to do a favor, there is a 10% chance that they’ll suffer 1-2 points of reputation loss. (Feel free to modify this chance depending on exactly how the PC handles the interaction: If they’re a real prick, their reputation is more likely to take a ding. If they apologize for being too busy at the moment and recommend someone who might be able to help, they might even gain a rep point. But, in general, most people don’t feel entitled to assistance and won’t ding someone for a simple refusal.)

Characters who fulfill a favor, however, will be rewarded with a reputation gain. Of course, characters who say they’ll do something and then fail to carry through on their promise are going to get hit with a reputation loss. See page 385 of the Eclipse Phase core rulebook for more information.

Had a quick thought for handling bribes last night as I was slipping off into sleep:

1. Set a “bribe value” for the NPC.

You could put together a set of charts based on income, wealth, sense of duty, and/or potential consequences. But mostly you can just make a judgment call on “that sounds like about the level where this gal might be influenced by the offer of money”.

2. If a bribe equal to the NPC’s bribe value is given, grant a +1 circumstance bonus on associated checks.

Keep this in mind when setting the “bribe value”. It’s not the value at which the NPC immediately buckles like a well-worn belt. It’s the value at which they think, “OK. That’s slightly tempting.”

3. For each doubling of the bribe value, grant an additional +1 circumstance bonus.

So if the bribe value of the NPC is 1 gp, then a bribe of 2 gp gives you a +2 bonus; 4 gp gives you +3; 8 gp gives you +4; and so forth.

There’s no functional limit to the size of the bribe the PCs can offer, but obviously this exponential system does provide a practical limit. Start with a bribe value of 10 gp and you’d need a bribe of 10 billion gold pieces to get a +10 bonus. (Again: This is another reason to keep the initial bribe value at the “slightly tempting” level and not the “likely to accept this bribe” level.)

Note: The system assumes that you don’t tell the players what the bribe value of the NPC is. (Although maybe they can find that out through Gather Information or Sense Motive checks.) With that in mind, use some common sense and rounding while adjudicating the system. For example, pure math might say that you need to bribe 256 gp to get a +9 bonus and 512 gp to get a +10 bonus. If a PC bribes 250 gp, though, they should get the +9 bonus and if they bribe 500 gp they should get the +10 bonus. This is all meant to be an easy-to-use mental guideline for your benefit, not a binding contract written in blood.

Keep in mind that offering a bribe is risky: If the resulting Diplomacy check is blown even with the bribe in play, the target may become insulted or angry in response.

I’ve been watching After Life: The Science of Decay, which is a really fascinating BBS documentary. The link there will take you to a point in the middle of the video which showcases a couple of interesting real-life fungi which, with a little fantasy twist, could be made very interesting challenges for your PCs.

Confusion Spike (CR 4): Characters within an area infested by the airborne spores of the confusion spike must make a Fortitude save (DC 15) each minute or become infected. Once infected, the spores will grow rapidly within the character’s mind, creating alchemicals that control and disrupt the victim’s behavior. 2d6 rounds after exposure, the victim will become confused (as per a confusion spell). 2d6 rounds after that, they must make a second Fortitude save (DC 15): On a success, they have recovered from the infection. On a failure they die.

Characters who die while under the effects of the confusion spike (either due to the effects of the fungus or otherwise), rapidly exude the fruiting body of the fungus. 1d4 rounds after death, this takes the form of a long, narrow spike which bursts through the character’s skull and grows rapidly to a length equal to roughly three times the character’s body length over the course of 2d6 rounds.

4d6 minutes later, the top of the fruiting body will explode spreading spores in a radius equal to the length of the fruiting body. These spores create a new infection zone, which can linger in the air for years or even decades. (Although they dissipate more quickly in outdoor environments.)

Dwarfbane (CR 1): This magical fungus, reportedly a tainted byproduct from certain rituals used to enchant magical arms and armor, breaks down metallic items in a cycle of decay. It was named dwarfbane after a strain of the fungus infested the rich veins of Dharballa and completely destroyed the dwarven city’s mines. Efforts to contain the infestation failed and eventually — broken and impoverished — the entire city of Dharballa was abandoned. Today there are many dwarven cities that will still refuse entry to any dwarf of Dharballa out of fear they will bring banespore with them.

Metallic items that touch dwarfbane become infested. Magic items made of metal can avoid infestation with a successful Reflex save (DC 17).

Although a great threat to dwarven cities, dwarfbane poses little threat to adventurers as long as they are wary of the danger: 1d4 hours after exposure to dwarfbane spores, a successful Knowledge (nature) check (DC 15) or Spot check (DC 25) will allow the owner of an item to notice spots of the distinctive green patina formed by the fungus. After 4d6 hours, the item will suffer 1d6 points of damage per hour until destroyed.

Objects affected by dwarfbane are rendered into a green, mossy rust. (Which, of course, seethes with dwarfbane spores.)

Fungal Snare (CR 2): These large, strong fungal growths form large loops around subterranean corridors. When a creature passes through the loop, the fungus snaps shut in a vice-like grip. If the target fails a Reflex saving throw (DC 14),they are caught by the snare, suffer 1d6 points of damage, and become stuck and entangled. The snare has AC 16, 10 hp, and requires a Strength or Escape Artist check (DC 15) to escape. A fungal snare can be detected with a successful Search check (DC 15).

Goblins have been known to specifically foster and grow fungal snares as lair wards. The goblins will carry small bags containing cuttings from the fungal snares, the presence of which prevents the fungal snares from snapping shut.

Fungal Web Droppers: Fungal webs grow on tall stalks to the ceiling of a cavern or into the lower foliage of a forest’s canopy. Once they have reached this height, their fruiting body spreads a wide, web-like indusium. When creatures pass beneath the indusium, the fungi drop their webs.

The table lists the size of the web and the maximum size of the creature that can be trapped by the web. Creatures beneath the web are affected as per a web spell, except using the DCs listed on the table. The web is also coated with a contact poison, afflicting anyone caught in the web or trying to tear it apart with their bare hands.

The tall stalks of fungal web droppers are usually easily noticed, although a Knowledge (nature) check (DC 18) is required to recognize the danger. Some fungal web droppers have stalks which camouflage themselves as stone columns or tree trunks, requiring a Spot check (DC 20) to notice. A Spot check (DC 30 – 2 per size category) will suffice to notice the overhanging webs.

Fungal Snare Webs: Fungal snare webs are similar fungal web droppers, except their webs remain attached to the fruiting body of the fungi and will attempt to draw those caught in the web up into the air. Characters who fail their initial Reflex throws are drawn a random distance into the air. Increase the Escape Artist and Break DCs by +5.