I never did get why you guys chose the name jamming. I keep thinking that it supposed to mean to jam radio signals. Looking up the definition on google, I get things like "Squeeze or pack (someone or something) tightly into a specified space.". The urban dictionary even goes so far as to define it as a bunch of people to play music together without being part of an official band. Then there are sites for making fruit Jam... I don't know why you guys choose "Jamming" as the name for the most direct forming of remote control over a shell, but perhaps you should reconsider the name.

Quote:

Remote Control and Jamming The following rules clarify, expand upon, and supersede the rules for remote control and jamming shells (p. 196, EP). “Shells” refers to any morph, bot, vehicle, smart animal, or gear that is equipped with puppet sock augmentation.

Note that a puppet sock alone can't run an AI operator. This is important for smart animals. Also, this definition of shells is unnecessarily restrictive: what about vehicles without puppet socks? Under the old rules they worked fine (because puppet sock was not a requirement for being considered a shell), but under this revision it doesn't work as they are no longer shells and there are no rules for non-shell vehicles.

Quote:

Shell Aptitude Maximums Non-morph shells are normally designed to be operated by AIs. Unless otherwise noted, they area assumed to have an aptitude maximum of 20.

Typo: 'area' should be 'are'. The maximum of 20 seems a bit low. I would bump it up to 30 (same as most synth morphs). Also: some shells, mostly robots, have aptitude bonuses. Examples include the guardian angel (+5 REF), dwarf (+10 SOM), and Creepy (+5 COO). You should clarify that these bonuses work as augmentation bonuses (applied after caps), not morph bonus (applied before caps). Either that or raise the aptitude limit as I suggested above. This is especially important for the guardian angel which has a +5 REF bonus.

Quote:

Shell AIs Most shells come equipped with an AI operator. For robots and vehicles, this is a bot/vehicle AI (p. 331, EP). This gives them a base REF of 20, with 10 in all other aptitudes (unless modified by the shell). For smart animals, this is an animal keeper AI (p. 155, Panopticon). Keep in mind that AIs have an aptitude maximum of 20 and cannot default on skill tests.

Note that a smart animal needs mesh inserts to run an AI and only two animals actually come with one (swarm cat and guard dog from panopticon), so it seems silly to say that all smart animals come with an animal keeper AI.

Quote:

May be issued more complex standing orders, up to an arbitrary length and level of detail. Orders that are complex enough to confuse a transhuman might require the AI to succeed in a COG x 3 Test or get some parts of the order wrong or confused. To bypass confusion, a character can program the AI with complex orders by succeeding at a Programming Test with a timeframe of 1-120 minutes, depending upon the complexity of the instructions (gamemaster's call). It's recommended that the gamemaster make the Programming Test in secret for the character leaving the instructions. On a failed test, the gamemaster should record the actual die roll and give the option of expending Moxie only if and when a situation arises where the AI's flawed instructions would become an issue. As with simple standing orders, it will revert to these orders if not following any specific instructions.

The Interfacing Skill states that it is used to "otherwise interact with and command ... other computerized devices". I think that should apply here to help the bot interpret complex orders. (perhaps a mod to the COG x 3 test, after all the base is only 30).

Quote:

Uses the teleoperator's base (ego) Reflexes and Intuition for Initiative. Reduce this by any Initiative penalties suffered by the shell (such as from wounds).

I do not like this. The old system was much better (the AI and the operator go on the same initiative). It is simpler and easier to keep track of (one number instead of 2+). The added complexity is not worth it. Also, look at what you wrote above "The operating character manipulates the shell via an entoptic interface, much like a video game." Would someone playing a video game (say a shooter with a physical controller) benefit from enhanced reflexes? Yes. Then so should someone using direct control.

Quote:

Uses its own Speed. If its Speed is higher than the teleoperator's, it can operate in autonomous mode for any Speed actions remaining after the teleoperator acts. Mental speed, neurachem, and other augmentations that increase the teleoperator's Speed in their own morph do not apply to the shell's Speed. If the teleoperator's Speed is higher, they may use their extra Speed actions as normal with their own morph, but they cannot directly control the shell with those extra actions.

I also do not like this. Again the old system was better: the shell uses the lesser of it or its operator's speed. Note that I am only objecting to the second sentence of this part, everything else is fine. Also: you need to clarify whether the autonomous actions go which initiative (requiring of course yet another initiative score: are you trying to keep people from using drones by making them keep track of a billion initiative scores?).

Quote:

Uses the teleoperator's base (ego) aptitudes and skills for all tests. No aptitude bonuses apply (including the teleoperator's own morph and the shell). The shell's aptitude penalties and aptitude maximum do apply.

Why do you get dumber, less socially apapt, and weaker willed just because you are operating at a distance (COG, SAV, and WIL respecively)? You should use the teleoperator's aptitudes including the morph bonuses for COG, INT, SAV, and WIL at the very least. Also consider it for REF.

Quote:

Uses the controller's Pilot skills for movement tests. Note that if the controller lacks relevant Pilot skills, such as Pilot: Anthroform for a bipedal pod morph, they must default to their base REF aptitude.

You should also clarify whether Gunnery skill is required for firing weapons.

Quote:

Requires the teleoperator to expend the same type of action that would be required of the shell when following instructions. E.g., the teleoperator must expend a Complex Action to instruct the shell to perform a Complex Action, and so forth.

This contradicts the existing rules, but it seems reasonable.

Quote:

Uses the teleoperator's Reflexes and Intuition (including their own morph's aptitude bonuses) for Initiative. Reduce this by any Initiative penalties suffered by the shell (such as from wounds).

This should include initiative penalties suffered by the operator as well. Especially those from traumas.

Quote:

Uses its own Speed, though if its Speed is higher than the teleoperator's, it can operate in Autonomous Mode for any Speed actions remaining after the teleoperator acts. Mental speed, neurachem, and other augmentations that increase the teleoperator's Speed in their own morph do not apply to the shell's Speed. If the teleoperator's Speed is higher, they may use their extra Speed actions as normal with their own morph (though they must disengage first), but they cannot directly control the shell with those extra actions.

You should not use the words 'directly control' as direct control is a thing. You should use 'control' or 'jamming'. Also I do not like the 'it can operate in Autonomous Mode for any Speed actions remaining after the teleoperator acts'. It is needlessly complicated: either the operator or the AI should be in control, not both at once.

Quote:

Uses the controller's Climbing, Flight, Freerunning, Free Fall, or Swimming skills for movement tests (not Pilot skill). For example, a teleoperator jamming a winged morph uses Flight. Jamming a groundcraft uses Freerunning skill, and so on.

You should clarify whether the gunnery skill is used or not as well.

Quote:

Since jamming overrides the character's sensorium, it may also not be used in the same Action Phase with other mental actions that require a Complex Action. This includes extra mental actions, such as those gained from mental speed or multi-tasking implants.

This is needlessly restrictive and counter-intuitive: Why does overriding the character's sensorium cause his forks in a multitasking implant to not work? Also does using VR or XP (which also overides the character's sensorium) also prevent the use of extra mental actions? Does a fork in a multi-tasking module using VR stop you from using any actions? You should get rid of this.

nothing has really changed, depending on how you read the rules in the core book.

Depends on how you read page 196. What does "limited by the shell's speed." mean? if the shell is a case or synth then the speed of the case or synth is 1. If the shell is a worker pod with neurachem then the speed of the shell is 2. if the shell is a guardian angel then the speed of the shell is 1. so your examples are wrong by [i]my[/i] reading of the rules in the core book. The speed of the AI's or the info morph controlling the shells have speed 3. How does that fit? IDK but I'm pretty sure that morphs are what provide a speed stat. But have fun and make it as complex as you like :)

I guess I didn't read your post closely. My understanding of what makes you most unhappy about the rewrite of the rule is that it creates extra initiative rolls for a single actor--the shell--in an action phase when the Shell AI has a higher SPD stat than the operator. Re-reading now, I see that your concern is with the different initiative Scores of the operator and the shell AI. (I'm willing to ignore that issue I'll explain how I do that within the rules in a bit.) My concern is with the different SPD stats of the Operator, the Shell and the Shell AI. I don't see that the rewrite supersedes the text of the core book. "When under direct control, the shell’s AI (or resident ego) is subsumed and put on standby. The drone acts with the same Initiative as the teleoperator, but is still limited by the shell’s Speed." Standby still works because the AI of a shell doesn't do anything without a command from the operator. In a situation where the Shell AI would act on an initiative pass higher than the operator then it stands by untill it gets a command. It can do this using the rules for delaying actions and it can be assumed that this is automatic. When the operator's initiative comes up he can direct control the shell or shoot it an action command with a quick action. In either case the shell acts on the operator's initiative. This has been my understanding of how standby works with the mechanics of initiative. Shells have always had thier own Reaction, Intuition SPD stats and initiative scores. There has always been the option of allowing an autonomous Shell to act on it's own initiative score rather than that of the operating character. Nothing has changed here. My issue is failure to address the Speed Stat of the Shell vs. the speed stat of the AI or the Operating Character. Morphs--including; Pod Morphs, Synth Morphs and, Info Morphs including AI--have a speed stat. Shells--including; Bots, Vehicles, and Exoskeletons--do not have a Speed stat because none has ever been listed. It's obvious to me that, like Morphs that can be remote operated and Jammed, the Speed Stat for Bots, Vehicles, etc. is 1 [u]unless those shells have SPD boosting gear[/u] like the Guardian Angel Bot with it's Neurachem. However there is an argument to be made, one that I occasionally have to re-refute, that the speed stat of an Autonomous Shell is that of it's AI; which would be 3. It doesn't seem to be a common issue but It would be nice if i could point to a sentence somewhere that says; "Shells without neurachem or reflex boosters have a speed of one. Machines are not faster than meat people in this universe so just stop bringing it up!"

Rearranging your post a bit to make it easier to respond to:

Quote:

My concern is with the different SPD stats of the Operator, the Shell and the Shell AI. My issue is failure to address the Speed Stat of the Shell vs. the speed stat of the AI or the Operating Character. Morphs--including; Pod Morphs, Synth Morphs and, Info Morphs including AI--have a speed stat. Shells--including; Bots, Vehicles, and Exoskeletons--do not have a Speed stat because none has ever been listed. It's obvious to me that, like Morphs that can be remote operated and Jammed, the Speed Stat for Bots, Vehicles, etc. is 1 unless those shells have SPD boosting gear like the Guardian Angel Bot with it's Neurachem. However there is an argument to be made, one that I occasionally have to re-refute, that the speed stat of an Autonomous Shell is that of it's AI; which would be 3. It doesn't seem to be a common issue but It would be nice if i could point to a sentence somewhere that says; "Shells without neurachem or reflex boosters have a speed of one. Machines are not faster than meat people in this universe so just stop bringing it up!"

I see what you are saying here and agree with you. I interpreted the sentences (from 195, EP): "Note that the difference between a robot, vehicle, and synthetic morph is in many ways semantic", "Like synthmorphs, bots and vehicles are treated just like any other character: they roll Initiative, take actions, and use skills". and "Just like synthmorph characters, certain bot and vehicle stats (Durability, Wound Threshold, etc.) and stat modifiers (Initiative, [b]Speed[/b], etc.) are determined by the actual physical shell." as saying that shells have a SPD stat similar to other characters. However, I [b]agree completly[/b] that having it clearly spelled out would be useful.

Quote:

I don't see that the rewrite supersedes the text of the core book. "When under direct control, the shell’s AI (or resident ego) is subsumed and put on standby. The drone acts with the same Initiative as the teleoperator, but is still limited by the shell’s Speed." Standby still works because the AI of a shell doesn't do anything without a command from the operator. In a situation where the Shell AI would act on an initiative pass higher than the operator then it stands by untill it gets a command. It can do this using the rules for delaying actions and it can be assumed that this is automatic. When the operator's initiative comes up he can direct control the shell or shoot it an action command with a quick action. In either case the shell acts on the operator's initiative. This has been my understanding of how standby works with the mechanics of initiative. Shells have always had thier own Reaction, Intuition SPD stats and initiative scores. There has always been the option of allowing an autonomous Shell to act on it's own initiative score rather than that of the operating character. Nothing has changed here.

Ah, it looks like you interpreted "subsumed and put on standby" as the AI is still active but delaying. While I had the reading that the AI is basically inoperable: its actions have been 'subsumed' by the the actions of the operator, and it is on standby the same way that a computer is in standby (mostly shut down but ready to quickly reactivate). My definition is, naturally, correct :). Not only because I say so, but in the context of the next sentence, which clarify's the meaning of the preceding sentence: the AI no longer has its own actions and it acts like an extension of the teleoperators (though still limited by it's own speed). However, If you ignore the subsumed part of the sentence and the next sentence, I can totally see why you might get your interpretation from the reading of the rules. And of course it seems to be the interpretation that whoever wrote this section favored (incorrectly, as it leads to partial actions which bork up the system something fierce). You are also correct that all the actions can be delayed to one initiative (exactly like the old system). What has changed however, is that this is no longer necessarily the case, and the rules quickly go pear shaped if someone doesn't delay. The old system forced the initiatives to be the same (because it essentially turned off the AI) and didn't rely on the characters to know that they needed to delay so that their characters and drones actions are all on one initiative in order to not break the system. Note that I am not saying that the old system can't be improved (I like things like direct control requiring a complex action to perform a complex action) I am just say that: a) the new system is different, not just a clarification, and b) the new system has some serious flaws (which I hope to get resolved by pointing them out).

Quote:

I guess I didn't read your post closely. My understanding of what makes you most unhappy about the rewrite of the rule is that it creates extra initiative rolls for a single actor--the shell--in an action phase when the Shell AI has a higher SPD stat than the operator. Re-reading now, I see that your concern is with the different initiative Scores of the operator and the shell AI. (I'm willing to ignore that issue I'll explain how I do that within the rules in a bit.)

I actually was trying to illustrate both these things. My biggest gripe however, is that they took the shell remote controls rules, which were somewhat flawed but a least playable, and they kept all the flaws while removing the parts that made them playable! Let me try and redo my above examples and add a couple more to hopefully be more clear as to what I am complaining about: [b]Example 1:[/b] This example illustrates that the new rules create much more work when determining initiative: [b]Example 2:[/b] This example illustrates the complexity and ambiguity generated when splitting a characters actions across multiple initiative numbers (as required by the new rules which separate the initiative of the drones and the teleoperator, but not the old ones which used the same initiative for both because the drone AI was off): [b]Example 3[/b] This example illustrates one of the problems with having the AI and the teleoperator both in control of the drone (which didn't happen because the old system turned off the AI). [b]Example 4[/b] A short example illustrating another problems with having the AI and teleoperator both in control of the drone. Also while I am at it, here are examples of the other things that bug me about the new rules (in hopes that repetition of the problems with the new rules will lead to them actual fixing the problems :) ): [b]Example 5[/b] This example illustrates the problem with the new definition of shell. [b]Example 6[/b] This example illustrates the problem with the third bullet point under direct remote control. There are of course, many other problems with the new rules. But I am going to stop here: it is much easier to criticize than create and I feel like a heel doing so much criticism of the designers hard work :(. Instead, I think I will try to revise the rules myself and hopefully create a positive example of what to do as opposed to telling people what not to do. Also because I am getting a little incoherent and ranty, and I don't think I am representing myself well :(

Okay, If I were me (and I pretty sure that I am) I would want something like this out of the Jamming rules patch: [h1]Control and Jamming[/h1]The following rules clarify, expand upon, and supersede the rules for remote control and jamming shells (p. 196, EP). For the purpose of these rules, the term “shell” is used to refer to bots, vehicles, and synthetic morphs alike. It also refers to any smart animal, morph, or piece of gear that is equipped with a puppet sock. [h2]Shells and Stats[/h2]Shells have all the physical stats of morphs (see p. 121). This includes Speed, Durability, Wound Threshold, Death Rating, and Damage bonus. These stats use the normal rules for morphs and are always separate from the operator of the shell unless the operator is sleeved into the shell (in which case the Shells physical stats are used). For example: if a shell with speed 2 (from neurachem) and a DUR of 100 is being remotely operated by a menton with speed 3, a mental speed implant, and a DUR of 35. The shell still only has speed 2, does not receive the extra mental actions from the mental speed implant, and has a DUR of 100. [h2]Shell Aptitude Maximums[/h2]Unless otherwise noted, non-morph shells are assumed to have an aptitude maximum of 30. Some shells, such as robots, indicate they have bonuses to certain aptitudes. Unless otherwise specified, these bonuses are treated the same as morph bonuses and applied before the caps (p. 124, EP). As normal, aptitudes enhanced by external factors (such as cybernetic or robotic enhancements) may exceed the aptitude maximums, but may not exceed a total value of 40. [h2]Shell AIs[/h2]Most shells not intended to sleeve a transhuman Ego and that have computer systems (including the cranial computer included in standard mesh implants) come equipped with an AI operator. A shell without the necessary computer systems (such as most smart animals) does not have an AI operator included in the purchase price and the AI operator (and something to run it on) must be purchased separately. For robots and vehicles, the included AI operator is a bot/vehicle AI (p. 331, EP). This gives them a base REF of 20, with 10 in all other aptitudes (unless modified by the shell). For smart animals, the included AI operator is an animal keeper AI (p. 155, Panopticon). Keep in mind that AIs have an aptitude maximum of 20 and cannot default on skill tests. AI operators may be issued commands by their owners (or hackers pretending to be their owners):

• Issuing commands via a communications link to an AI operator is considered a mental action.
• An AI operator may be given specific instructions to perform any Quick, Complex, or Task action with a Quick Action. If given more instructions than it can perform in a single Action Turn, an AI operator will continue to carry out instructions on subsequent Action Turns unless it receives new instructions.
• As normal, a characters may send the same message to as many AI operators as they like using the same Quick Action, provided that they have some means of communicating with each AI operator .
• An AI operator may automatically be given simple, one-sentence standing orders such as, “Guard my allies and me,” “Prevent anything from passing this doorway, using deadly force if necessary,” or, “Kill anything that enters a perimeter with a radius of 10 meters from our present position.” Issuing such orders is a Quick Action. If the AI operator isn't busy performing any specific instructions, it will revert to its standing orders.
• An AI operator may be issued more complex standing orders, up to an arbitrary length and level of detail. Orders that are complex enough to confuse a transhuman require that the issuer make an Interfacing Test with a modifier based on the complexity of the order. Alternately, to bypass confusion, a character can program the AI with complex orders by succeeding at a Programming Test with a timeframe of 1-120 minutes, depending upon the complexity of the instructions (gamemaster's call). It's recommended that the gamemaster make the Programming Test in secret for the character leaving the instructions. On a failed test, the gamemaster should record the actual die roll and give the option of expending Moxie only if and when a situation arises where the AI's flawed instructions would become an issue. As with simple standing orders, the AI operator will revert to these orders if not following any specific instructions.

[h2]Control of Shells[/h2]There are three ways of controlling a shell: sleeved mode, direct control, and jamming. Each is detailed below: [h3]Sleeved mode[/h3]A shell in sleeved mode is controlled by an Ego or AI sleeved into the shell (which requires a brain or cyberbrain for a full Ego and at least a computer system for an AI). When in sleeved mode, the shell acts in all ways as a normal character. An AI operator running on a system that controls a shell is not considered to be an infomorph, but rather to be sleeved into that morph. If an operator AI or Ego that is not sleeved into a shell (such as an operator AI running on an external Ecto or as an infomorph in a ghostrider module) is attempting to control the shell, the AI or Ego must use direct control or jamming (see below). [h3]Direct Control[/h3]A directly controlled shell is operated either by physical controls (such as a car's steering wheel) or through a communications link. Using direct control via a communications link requires that the shell have a puppet sock. Direct Control is the method used to control exoskeletons when wearing them. Direct control has the following rules:

• If the shell has an AI or Ego sleeved into it, while the shell is under direct control that AI or Ego is subsumed and on standby. This means that the AI cannot take any actions, makes no tests, and does not roll for initiative at the start of the Action Turn.
• In an exception to the above rule: if the shell has a full brain or cyberbrain, then the Ego or AI in that brain may, on the operators initiative, oppose control of the shell with an InfoSec test (see p. 261). If at the start of an Action Turn, the operator cannot take any actions (usually because they are dead) and the Ego or AI can oppose control, then the Ego or AI regains control automatically and rolls for initiative as normal.
• Under direct control the shell uses the same initiative as the operator. It is still however, limited by the Speed stat of the shell. If the shell is faster than the operator, it loses any extra actions as it waits for operator input.
• Being limited by the speed of the shell means that if the shell cannot take more actions than it normally could if it was not direct controlled. This includes exoskeletons, which may limit the physical actions available to those wearing them. Example: A male Jovian with speed 3 is wearing an exoskeleton with speed 2. On the first and second phases he may act normally by direct controlling the exoskeleton (his physical complex action is spent to move the exoskeleton), on the third phase the exoskeleton cannot act (as it is limited by its speed of 2) and thus the Jovian cannot take physical actions such as aiming and shooting his weapon as he is trapped within the slower exoskeleton. The Jovian may take his mental actions normally.
• Establishing direct control generally takes a quick action unless opposed by an AI or Ego, in which case it is a complex action and requires an opposed InfoSec test (see p. 261). Control begins at the start of the next Action Turn. As the AI or operating Ego is subsumed and on standby under direct control, this means that they do not roll for initiative on that Action Turn.
• Relinquishing direct control generally takes a quick action. Control ends at the start of the next Action Turn. The shells AI or resident ego then rolls for initiative normally.
• If the character does not or cannot relinquish remote control (the operators communication link has been disabled, for example), then generally direct control does not end and the shell does nothing as it waits for further instruction. However, it is possible to have a keep alive signal: if the signal from the operator is cut off, the shell's sleeved AI or Ego begins operating on the next turn as if direct control had been relinquished.
• Having the shell perform an action requires the operator to expend the same type of action that would be required of the shell. That is, the operator must expend a Complex Action to have the shell to perform a Complex Action, and so forth. This includes Automatic Actions such as Fraying.
• When operating the shell, the operator uses their normal aptitudes and skills for all tests, with the exception of Knockdown Tests which use the shells SOM. The operator takes a -10 penalty to all physical tests taken by the shell . If the shell has a penalty to COO, SOM, or REF then the operator takes that penalty as well. (ALSO CONSIDER CAPING COO, SOM, AND REF BY THE SHELLS CAPS).
• When moving the shell using direct control, the operator uses the relevant Pilot skills for movement tests, unless the shell is an exoskeleton being physically worn by the operator (p. 344, EP). Note that if the operator lacks relevant Pilot skills, such as Pilot: Anthroform for a bipedal pod morph, they must default to their base REF aptitude.
• When making ranged attacks using the shell, the operator uses the Gunnery skill.

[h3]Jamming[/h3]A jammed shell is operated via a communications link and is similar to direct control. However, when jamming the operator subsumes themself in a VR simulation of the shell's body and sensorium. Though this offers a finer quality of control than direct control, it is still a simulated experience and not as intensive as actually sleeving into the shell. Jamming is considered a mental action. An operator may only jam one shell at a time and jamming requires that the shell have a puppet sock. Jamming differs from direct control as follows:

• Jamming requires a complex action by the operator to engage or disengage from jamming mode, not a quick action.
• Jamming uses the controller's Climbing, Flight, Freerunning, Free Fall, or Swimming skills for movement tests (not Pilot skill). For example, an operator jamming a winged morph uses Flight. Jamming a groundcraft uses Freerunning skill, and so on.
• A jamming character uses an appropriate weapon skill when making ranged attacks. For example attacking with a laser pulser uses the Beam Weapons skill.
• While jamming a character suffers a -60 penalty on all physical actions taken with any morph other than the jammed one.
• If the communications link is severed while jamming (which might happen if drone is killed or destroyed), the operator suffers 1d10 mental stress.

Note that under these rules, jamming is a specialized form of Direct Control and as such, unless noted above, it uses all the same rules for direct control. Edit: Clarified some edge cases.

A comment:

RobBoyle wrote:

DivineWrath wrote:

I never did get why you guys chose the name jamming.

We wanted a term for it, didn't have a good one, and it was the best we came up with at the time. Too late to change it now :)

I see. I guess that can be something to worry about come time to write revised or second edition.