This post is a little hyper-specialized in its focus, but it was a mechanical concept that was tickling my hindbrain so I decided to just pull the trigger on it.

Flexbot morphs are formed from multiple, shape-adjusting modules which can flexibly reconfigure themselves into a multitude of forms: Multi-legged walkers, tentacles, hovercrafts, and so forth. In addition, their individual modules are capable of sprouting fractal-branching digits (capable of breaking into smaller digits down to micrometer scales, allowing for ultra-fine manipulation).

Eclipse Phase: Transhuman introduces a new set of rules for flexbots allowing them to incorporate specialized modules. (For example, a Beekeeper module can be used to deploy nanoswarms.) In order to support these specialized modules, Transhuman also introduces a system for calculating the characteristics of a morph formed using various configurations of specialized modules.

In order to use these rules, however, you need the stats for a basic flexbot module. Transhuman provides stats for a Yeoman module which is supposed to replace the basic flexbot morph, but it actually results in a very different stat block. So what I’ve done is to create a basic flexbot module that you can use to build a flexbot morph virtually identical to the one described in the core rulebook. I’ve also tossed in a cheap flexbot module and also something nifty called a silvershot module.

NEW FLEXBOT MODULES

A basic flexbot morph (as described in Eclipse Phase, pg. 144) contains 5 basic flexbot modules.

(Following the rules for combining flexbots, this would actually result in a morph with Durability 24 instead of the Durability 25 found in the core rulebook. But that’s the closest you can mathematically get.)

BASIC FLEXBOT MODULE

This is the basic module found in a typical flexbot morph. In a typical configuration, one of those modules is the size of a small dog (roughly 75 centimeters high x 75 centimeters long x 25 centimeters long), but they’re capable of significantly compressing or extending their dimensions using their Shape Adjusting enhancement (see Transhuman, pg. 208).

Enhancements: Access Jacks, Basic Mesh Inserts, Cortical Stack, Cyberbrain, Fractal Digits, Mnemonic Augmentation, Modular Design, Nanoscopic Vision, Shape Adjusting
Mobility System: Walker (4/16), Hover (8/40)
Aptitude Maximum: 30
Durability: 8
Wound Threshold: 2
Advantages: Armor (4/4)
Notes: Small Size trait (Transhuman, pg. 95)
CP Cost: 4
Credit Cost: High

CHEAP FLEXBOT MODULE

Originally marketed by Starware, this cheap alternative to a typical flexbot module quickly gained an extremely negative reputation. Consumer advocacy groups leaked the full blueprints for the design in an effort to discredit Starware, but this ironically just resulted in a lot of people having access to it. Down-on-their-luck flexbots sometimes don’t have any choice but to substitute in a cheap Starware knock-off if one of their main modules is damaged.

Enhancements: Access Jacks, Basic Mesh Inserts, Cortical Stack, Cyberbrain, Mnemonic Augmentation, Modular Design, Shape Adjusting
Mobility System: Walker (4/16), Hover (4/28)
Aptitude Maximum: 20
Durability: 6
Wound Threshold: 2
Advantages: Armor (2/2)
Disadvantages: Lemon trait
Notes: Small Size trait (Transhuman, pg. 95)
CP Cost: 1
Credit Cost: Moderate

SILVERSHOT MODULE

Silvershot modules are designed with specialized, multi-channel connections using superconducting material to synchronize high-speed, cross-modular communication through massive redundancy. A flexbot formed entirely from silvershot modules can move like quicksilver, although the advantage debilitates rapidly if non-silvershot modules are introduced.

Enhancements: Access Jacks, Basic Mesh Inserts, Cortical Stack, Cyberbrain, Mnemonic Augmentation, Modular Design, Shape Adjusting
Mobility System: Walker (4/16), Vectored Thrust (8/40)
Aptitude Maximum: 30
Speed Modifier: +1 (Reflex Boosters)
Durability: 8
Wound Threshold: 2
Advantages: REF +10, Armor (4/4), Reflex Boosters
Notes: Small Size trait (Transhuman, pg. 95)
CP Cost: 8
Credit Cost: High (minimum 10,000)

COMBINING FLEXBOT MODULES

Unless noted otherwise, only physically attached modules should be considered when combining the modules of a flexbot into a flexbot morph’s stats.

Enhancements: In general, the flexbot morph is considered to have all of the enhancements and traits available to their individual modules. The exception would be any enhancement or trait that would require the entire morph to be augmented (unless, of course, all of the flexbot’s modules possess the enhancement or trait). (For example, a chameleon skin would only cloak the module possessing it.)

Mobility System: For each module which lacks a specific mobility system, the movement rate of the morph with that mobility is halved. (This penalty is cumulative for each module which lacks the mobility system.)

Flexbot modules can reshape themselves to possess any mobility system based on purely mechanical principles (hopper, hover, roller, rotorcraft, snake, submarine, tracked, walker, wheeled, winged). A module cannot have more than two mobility systems shaped at a time. Assume shaped mobility systems have a movement rate of 4 meters.

Aptitude Maximum: Use the highest maximum available for each aptitude.

Speed Modifier: Flexbots use the Speed of its slowest module.

Durability: Take the highest Durability among the flexbot’s modules and add half the Durability (round up) of each additional module. Calculate the morph’s Wound Threshold (Durability ÷ 5) and Death Rating (Durability x 2) normally based on the morph’s total Durability.

• Damage: Damage is assumed to be evenly divided between a flexbot’s modules. (As an optional rule, determine which specific module was hit and apply the damage accordingly. This would only become important if a specific module separates from the flexbot or if that module is disabled, in which case the flexbot would lose any enhancements or traits specific to that module.)

Advantages/Disadvantages: As with enhancements, a flexbot morph is considered to have all the advantages and disadvantages possessed by their individual modules.

• Ability Scores: Flexbots use the highest bonus for each aptitude. Multiple bonuses to the same aptitude from different modules do not stack.

• Armor: A flexbot’s Armor Value is equal to the average Armor Value of its modules (round up).
• Individual flexbot modules count as a small target (-10 modifier to hit in combat)

This is a quick reference. Refer to Transhuman (pg. 203-206) for the complete rules.

Since my last update, I’ve received about a dozen additional refund e-mails and all of those refunds have now been processed. The only people who should be currently waiting for a refund are those who requested a refund by check. (I’m going to be processing all of those refunds in one big batch.)

This update is primarily just a third and final call: If you are a backer who has not received a refund, it’s because you either haven’t sent me an e-mail or I haven’t received it. If it’s the former, please contact me ASAP at legendsandlabyrinths@gmail.com. If it’s the latter, please leave a comment here and we’ll figure it out (since there seems to be something wrong with our e-mail connection).

Many of you may be thinking to yourself: “I don’t freakin’ care. I wasn’t a backer for Legends & Labyrinths.” Good news! Even if you weren’t a backer, you can download a copy of the Black Book Beta which contains a totally playable version of the rules along with a lot of cool new tools for simplifying your 3.5 or PF game.

Tagline: The Accursed Tower is a fairly solid module, with a handful of potential problems.

R.A. Salvatore is best known for his novels dealing with the drow character Drizzt Do’Urden – one of the finest swordsman in all of literature. There are some who worship these stories; others who revile them. Personally, I find them to be possessed of both significant strengths (such as Salvatore’s outstanding description of fight scenes and some of the soul-searching for Drizzt found in the Dark Elf Trilogy) and significant weaknesses (such as the repetition of some of the plots and several weak characteristics to Salvatore’s writing).

Similarly these novels are set in the Forgotten Realms, a campaign setting which some worship and others revile. As with Salvatore himself, I find the Realms to be possessed of both significant strengths (breadth of the setting, the wealth of detail and support) and significant weaknesses (some ridiculously bad supplements, over saturation, and general silliness).

I therefore approached The Accursed Tower (an adventure for 4-8 characters of level 1-3) with a fairly open mind – Salvatore and his original gaming group (the Seven Swords) “return to the Savage Frontier” of the Ten-Towns in the Icewind Dale. The characters get a chance to explore a well known area of the Realms, while running into some well known characters of the Realms.

THE PLOT

The PCs are in Luskan, the City of Sails, along the Sword Coast (with that (in)famous “it’s up to the DM to determine how” that seems to be present in every D&D adventure I’ve ever read). They sign up to guard a merchant caravan which is going to the Icewind Dales. When they get there the caravan owner reveals that he has an opportunity for them to earn a great deal more money if they help him out with something.

It turns out that the caravan dealer is searching for a ruined tower where a mage died while researching a healing salve with the potential to help a great many people. If the PCs help him get the notes from that research, they will not only be helping in his humanitarian quest – but will also share in a significant portion of any recovered treasure.

The PCs track down the location of the tower with the help of a few familiar faces – Regis and Drizzt from Salvatore’s books – and then go off to obtain the diary. They do so. End of story.

Except, that’s not all that’s going on. The caravan driver isn’t actually a humanitarian — he’s an evil mage who has killed the actual caravan driver and taken his place. The research he’s after isn’t for any healing salve – it’s for becoming an immortal lich.

It’s time to insert the dramatic music.

THE GOOD STUFF

The set-up is intriguing and provides a solid base for the adventure. Salvatore and his gaming group construct a complex plot with several different hidden agendas and machinations going on behind the scenes – wheels within wheels is the order of the day. First, you’ve got the dual nature of the NPC who hires the PCs. Plus, one of the people the PCs get to help them out is actually an ancient barbarian sorceror, who once fought against the evil mage who owned the Accursed Tower and was responsible for his downfall.

The adventure is also blessed with some remarkably strong NPCs. Drizzt and Regis, of course, get an extra boost thanks to their literary background, but there are several others – including the father-son team from the caravan who befriend the PCs, the barbarian sorceror, and several others.

I was also impressed with a number of hooks which were left open for future expansion at the DM’s discretion – such as a scroll the PCs find half-buried in a snowdrift, with no ready explanation as to how it got there or why.

Finally, the entire package is strong one. As per usual for a TSR book the production values are high, the art is of decent quality, the book has been thoroughly proofread, and the lay-out is clear.

THE BAD STUFF

First, there’s no excuse for recycled art in a 32 page book – even if you are just filling up the quarter page of blank space left on that second-to-last page. This is particularly true if you’re TSR. They’ve published hundreds of books. Surely there was a piece of art from some other book they could have recycled instead of copying the art from page 17.

Second, the book suffers from that perennial Realms problem: Silly names. Maybe some people don’t have problems with names like “Peddywinkle” in their fantasy campaigns, but I do.

Third, random encounters are not a substitute for meaningful plotting. Although the first part of this adventure deals with a caravan trip, absolutely nothing happens on that caravan trip of any significance. The only planned event is a goblin encampment, and that only happens if the PCs follow a specific set of tracks. Everything else is a random encounter. I wasn’t too impressed with this – you could just as easily have said “the PCs are in the Icewind Dales” instead of “the PCs are in Luskan”.

Fourth, the “healing salve” cover for the archmage’s true intentions was a little annoying. It is described as “healing any wound and curing any disease”, and the guy goes on to say how he wants to “make this salve known to all, so that the world would be free of sickness”. Yeah, right. Did the Realms suddenly become devoid of healing potions?

Fifth, the map on the inside front cover is of the caravan route. Along this route are numbers. What these numbers are supposed to be is never mentioned, but you can interpolate and figure out that these represent how far the caravan gets on each day of the journey. This has relatively little importance (after all, it is a set path), especially considering the complete unimportance of the caravan drive to the overall adventure in general. The book would have been better served with a map of the Icewind Dales, where the PCs have to trek all over the place to figure out the location of the tower.

Finally, the early part of the adventure is fairly railroaded (except for those sections where nothing of importance is happening). The last part of the adventure, where the PCs have reached the tower, is nothing more than a standard event-by-location dungeon.

CONCLUSION

The primary appeal to The Accursed Tower is going to be for those familiar with Salvatore’s writing. The basic plot and elements of the adventure are nothing to get excited about (and are, in fact, possessed of several drawbacks) – but this can be mitigated when the PCs run into characters well known to them from their favorite books. It’s the same kind of rush you got from the line, “Anakin Skywalker… meet Obi-Wan Kenobi.” Or from those Howard stories where you’re following some unfamiliar character and suddenly they run into Conan.

So, The Accursed Tower gets an average rating overall. Those with an interest in Salvatore’s writing might want to pick it up; those with an undying hatred of Salvatore, Drizzt, or the Realms should avoid it at all costs.

Style: 3
Substance: 3

Author: R.A. Salvatore and the Seven Swords (Mike Leger, Brian Newton, Tom Parker, David Salvatore, Gary Salvatore, and Jim Underdown)
Company/Publisher: Corsair Publishing, LLC and Sovereign Press, Inc.
Cost: $25.00
Page Count: 168
ISBN: 0-9658422-3-1

Originally Posted: 1999/08/16

I honestly have no idea what my problem with the name “Peddywinkle” was.

For an explanation of where these reviews came from and why you can no longer find them at RPGNet, click here.

Essentially every character in Eclipse Phase has a personal muse: An AI that serves as their companion and personal assistant from the time that they’re a young child until the day that they die. Their persistent presence and collaboration in every facet of a person’s life is one of the transformative elements of the Eclipse Phase setting which creates the unique exotic flavor its science fiction.

As I mentioned when I posted my Eclipse Phase system cheat sheet a few days ago, however, it initially proved difficult for players to properly utilize their muses as an integral part of their lives. Literally front-paging the muses helped, but something I also started experimenting with was the idea of letting another player run the muse. Thus everyone at the table would control both their PC and the muse of another character.

The recent Eclipse Phase: Transhuman sourcebook makes a similar suggestion. There are multiple advantages: First, it forces the roleplaying relationship between the PC and their muse into the open. Second, it encourages the muse to have its own independent personality. Third, it can also make it a lot easier to split the party because many or all of the players who aren’t present may still have a muse to play in the scene.

As I mentioned a couple of days ago, however, I’m currently developing an open table Eclipse Phase campaign. Unfortunately, an open table disrupts the idea of having a second player run your muse: Since the players at the table are constantly in flux, there would be no guarantee that the player running your muse would be at your next session.

Loosely inspired by Shock: Social Science Fiction, therefore, I’m going to experiment with the idea that your muse is always played by the player to your left. (Basically a structured troupe-style play in which the muses form the body of communal characters.)

This obviously sustains the advantage of the muse always being portrayed by a separate player. The disadvantage, however, is that there would be a constant flux of different players portraying your personal muse (leading to potential continuity problems). To mitigate these problems, what you need is a quick briefing sheet that would introduce the new player to your muse. This needs to be insightful enough that the essence of your muse is communicated, but focused enough that it can be quickly assimilated at the beginning of the session.

Fortunately, I already have a template like this that I use when designing NPCs for social-intensive scenarios. I’ve tweaked it slightly to customize it for troupe-style muses. I think you might find it useful even if you’re not contemplating this style of play.

When designing your muse, I also recommend checking out “Maximizing Your Muse” in Eclipse Phase: Transhuman (pg. 166-169). There’s a lot of good ideas in there.

MUSE TEMPLATE

Name: Self-explanatory. As limited artificial intelligences, muses have their own identities.

AR Avatar: A description of the muse’s “physical” appearance when it appears in AR (or VR).

Roleplaying: This is the heart of the briefing sheet, but it should also be the shortest section. Two or three brief bullet points at most. You’re looking to identify the essential personality traits or mannerisms which will serve to unlock the muse.

Motivations: Like any other character, muses should have three personal motivations (Eclipse Phase, pg. 138). These may mimic, support, or even contrast the motivations of their owner.

Background: This is likely the only section of the briefing sheet which is likely to need frequent updating. I recommend a single bullet point for each significant scenario the muse participates in (and keeping each bullet point to no more than two or three sentences). The point isn’t to be encyclopedic: It’s to provide an essential overview of key facts. (If the muse’s current player needs clarification about something, they can lean over to their right and ask.)

Notes: A miscellaneous category of key information that wasn’t hit in the previous sections. For example, if the muse is currently holding the encryption keys for an important data store or is hiding the fact that they know what happened to their owner during a span of lost time, this is probably a good place to note it.

Stat Block: Include the muse’s stat block at the bottom of the briefing sheet for easy reference. Most muses will use the standard muse stat block, but they’ll still be customized by selecting three Knowledge skills. Some muses might be commonly housed in a bot (in which, case include that stat block, too); others, of course, may have received custom upgrades.

AURORA – SAMPLE MUSE

AR Avatar: A young girl with yellow hair so bright it seems to glow lemon. She usually has a cigarette drooping out of the corner of her mouth.

Roleplaying:

• Refuses to take any shit from her owner, but is also fiercely protective of her.
• Her owner cannot understand her obsession with celebrity gossip.
• A dry, sardonic laugh that often breaks apart into a fake “smoker’s cough”.

Motivations: +Open Source, +Wealth, -Alien Contact

Background:

• Aurora was originally licensed on the likeness of a child star named Sundrop. Around the time her owner turned 17, “Sundrop” got tired of that identity and started referring to herself as “Aurora”.
• Aurora was actually the one first contacted by Firewall based on a research project she was working on for her owner.
• Aurora’s owner deleted her and restored her from a backup that was three months old. Her owner refuses to explain what happened, which completely infuriates Aurora.

Notes:

• Aurora was infected by a “dormant” strain of the exsurgent virus. It hasn’t had an visible effects yet, but she’s been spending her down time secretly researching a very strange and seemingly random set of topics. (List anything she researches on the back of this sheet, please.)

Aurora: Aptitudes: 10, INT 20. Skills: Academics: Psychology 60, Art: Simulspace Design 30, Hardware: Electronics 60, Infosec 30, Interest: Celebrity Gossip 30, Interface 40, Professional: Accounting 60, Programming 20, Research 30, Perception 30.

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.