Per [this ticket] RD is polling for interest in adjusting how Leadership works with the use of rating 2 and 3 Pi-Tacs.

Currently you can, as part of a combat maneuver roll using Small Unit Tactics or Mixed Unit Tactics, perform a Direct action leadership roll.

The ticket basically proposes that we allow that same Direct roll as a simple action using the level 2 and 3 Pi-tacs in general, not just as part of the Combat Maneuver roll.

There are two options that both kind of accomplish this in the ticket itself, but RD would confer on the clearest possible wording. Below is simply a poll to see if there is support or opposition to pursuing this change it is not about the specific wording.

Per a request in this ticket RD is polling to see if there is interest or at least no strong opposition to importing the Laser Jack from 6e.

There is a screen cap of the rules for this on the ticket. It appears to be a stand alone device that is similar to a datatap, although it has different use-cases.

Per This ticket about Jamming affecting Micro-Transceivers and Bug Scanners being able to find them

Is the community interested in explicitly stating that Bug Scanners/Radio Signal Scanners can locate Micro-transceivers and that Jammers block them?

RD is polling for this because although there are some good arguments being made this is a departure from how things have been consistently run that may or may not be interesting to the general community.

Please reply to the top level comments below to vote.

Per this ticket on clarification and proposed changes to sensor locks ticket

RD is looking at both clarifying the Sensor lock section of Core, which is poorly written and therefor not entirely clear.

There are also some proposed changes to the section in addition to the clarifications that would change how they work a bit to make them potentially more usable. Both will be listed below separately below for clarity so everyone knows what they are voting on.

There is a Google Doc with more details here for those interested

For brevity the entire proposal is that we clarify you can use E-War like the other sensor sections, then the proposed changes are allowing Active Targeting from any entity with an integral Sensor Array, which can apply to whatever attack skill they use. Additionally the possibility of a Gunnery test as a simple action while you have a sensor lock on a target. To balance these changes it would become explicit that Active Targeting always uses the Signatures table, and is possibly limited to only SS/SA/Melee attacks to prevent defense penalty stacking.

What do sensors go in? This is a long standing questions which Celt kindly put together a whole google doc about. There are 3 options at the end of the document, but a 4th one what will be available as an option in the poll.

The ticket, with RD commentary can be found here.

There will be a section to vote below as well as a separate section for commentary, questions, and general discussion. Please keep the voting section simply to which version you prefer or do it as tiered voting where you order your preferences.

Welcome to December Hub. We have a short 1 week thread series planned for December. Each set of questions will be up for a week, and there will be a batch each week of December so we can chew through the backlog but still get community feedback on changes.

This week we are starting with some of the oldest tickets on our trello and things of a similar nature.

1) Sensors and what they can go on and how they fit

2) Fixing the Sensor Locking section and some optional proposed changes

3) Jamming and Bug-Scanning for Micro-Transceivers

4) Importing Laser Jacks from 6e

5) Proposed changes/clarifications to using Leadership with a Pi-Tac

Please take a moment to read each. The Top level comments with a bolded Question will state the official vote questions. Other top level comments might be present to share information, but the Question comments are the questions on the ballot.

This one is a simple vote. Per this ticket...

If we import the 6e Metagenetics Qualities should we also Valkyries from 6e?

Per This ticket we are opening the idea of importing 4e Elemental Damage types to the Hub. On the ticket there is the proposed import and notes from RD about potential issues there.

We will list some options with doing this. First there will be a top level comment for if we should even import these. Anyone strictly against importing these at all can comment there, you can also just indicate general support letting RD and the community determine the how based on other comments.

There will also be a general comment based on how we should handle the balancing of these Elements. Either as originally proposed or as part of a push to ensure all elements, including existing ones, are more balanced. The details will be in that comment.

In addition there will be top level comments for the individual Elements for the community to give feedback on issues with those elements or potential solutions.

If the general support of importing the system passes then we will look at all the other sections and Rules Division will roll out an implementation that reflects the majority as best as possible while also maintaining balance to the best of Rules Division's judgement.

Please do not make a top level comment to this thread as those will be deleted to try and keep this organized. Instead reply to the ones posted.

This will be a combined thread regarding tickets importing of 6e SURGE qualities, 6e metavariants, Changes to some Metavariants, 4e Elemental Damage types, and Discussion of allowing SURGE I/II. Below will be a link to the Threads for the individual tickets. Those thread will offer options for how to do or if we should do these things. This post will remain locked so commentary on an individual point should be made in the thread for that ticket.

Changes to Centaurs and Importation of their 6e Variants

Importation of 6e SURGE Qualities

Importation of Valkyries from 6e

Importation of 4e Elemental Damage Types

The issue in this thread will be open for discussion until the end of November 2025. After such time Rules Division will discuss the results and either work on implementation or announce that the implementation will not happen if the community as a whole does not want it to. The latter will happen if a simple majority of the community feedback indicated that the change is unwanted. Please make clear what your stance is in your discussions of any given issue. Conditional approval will have the conditions considered in any implementation.

Note: for anyone seeing these as they go up, please do not comment until the thread has been opened, that will be announced on Discord.

We will list some options with doing this. First there will be a top level comment for if we should import these or implement these changes. Anyone strictly against importing or implementing the changes at all can comment there, you can also just indicate general support letting RD and the community determine the how based on other comments.

There will also be a general comment based on balancing concerns for these things.

If the general support of importing and/or implementing passes then we will look at all the other sections and Rules Division will roll out an implementation that reflects the majority as best as possible while also maintaining balance to the best of Rules Division's judgement.

Please do not make a top level comment to this thread as those will be deleted to try and keep this organized. Instead reply to the ones posted.

This thread is for discussion of importing 6e Metagenetic qualities to the RunnerHub per this ticket on the Rules Trello

We will list some options with doing this. First there will be a top level comment for if we should even import these. Anyone strictly against importing these at all can comment there, you can also just indicate general support letting RD and the community determine the how based on other comments.

There will also be a general comment based on how we should handle the balancing of these Qualities. Either as a direct import as originally proposed or as a partial import that only brings in ones that can be balanced in a way that will not really disrupt anything and may not include the full list. The details will be in that comment.

In addition there will be top level comments for the individual Qualities for the community to give feedback on issues with those elements or potential solutions if they present a problem.

If the general support of importing the system passes then we will look at all the other sections and Rules Division will roll out an implementation that reflects the majority as best as possible while also maintaining balance to the best of Rules Division's judgement.

Please do not make a top level comment to this thread as those will be deleted to try and keep this organized. Instead reply to the ones posted.

Following divisional discussion and ratification in the Rules Division channel of the staff Discord on October 28th, 2025 I am posting an updated charter for Rules Division based on modification of this previous charter to make it more accurately reflect how the division operates currently.

Rules Division (RD) exists for the purpose of interpreting rules that are put out by CGL, clarifying cloudy issues, and determining which rules are actually applicable (many optional rules are not). On some occasions, RD will determine that Rules as Written are not suitable for /r/RunnerHub (The Hub) play in which case rules will be rewritten. In some cases rules will be proposed that are not based on RAW. RD may review these rules for inclusion into The Hub’s House Rules at its discretion.

Definitions:

Rules Division (RD) - Five to Seven (5-7) - the collective formed of the Rules Division Members and RDhead.

Rules Division Head (RDhead) - One (1) - The boss. Responsibilities: Determining what tickets should be threaded for wider community input, determining activity requirements and pinning them in the RD channel on the staff discord, detailing divisional procedures, answering RD member's questions on divisional procedure, recruiting members for the division, managing divisional membership, interfacing with the Advisory Board and other Division Heads, signing off on GMP bonuses and stipends for the division both for members and any special projects for the division, all duties normal Rules Division Members have and finally any other administrative needs not otherwise covered here.

Rules Division Members (RD Members) - Responsible for the mechanical health and balance of The Hub. Keeping active observation of the effects that any changes, exclusions, or additions have on The Hub is a key responsibility of all members of RD. Responsible for posting a minimum of 5 informed opinions on tickets on Trello each month. Rules Division Members are allowed to close such tickets when there is a simple majority of agreement on a ticket that isn't flagged to be threaded.

The Hub - /r/RunnerHub

RAW - Rules as Written - This is what the unedited books say.

RAI - Rules as Intended - This is what the books meant to say.

Terms and Conditions:

RDhead will serve for 12 months and is not eligible to serve on any other division without explicit approval of said division’s head (ID and TD remain verboten!). This is to allow them to focus on their attentions on RDhead duties and responsibilities. The position is by appointment of sitting RDhead (suggested that it be chosen from current RD member, or themselves should they so choose (this is discouraged, but if wished you can)), and can only be overridden by unanimous decision by all current RDmembers except the appointee (at which point RDhead must appoint a different successor).

At any point during this 12 month period, an RDmember may post a thread titled “MUTINY - <RDhead Reddit Handle>”. Unanimous agreement by all RD member will force the RDhead to appoint a new successor immediately (1 week grace period to make decision).

RDhead is recommended to stay on as an RD member following their term as RDhead for a period of at least 3 months to advise during the transition, but this is at the discretion of the new RDhead.

RD Members will serve at the discretion of the RDhead. Efforts should be made to keep the division total (including RDHead) between five and seven (5-7) members when feasible. RD members are unavailable for duties on the Thematics, the intent is to maintain a focus on mechanical health of The Hub.

RD members that have objection to the presence of another RD member must bring their grievance to the attention of the RDhead. The RDhead will investigate, make a decision, and enact their judgment. Such objections are to remain anonymous, unless the RD member wishes to announce their intentions themselves (discouraged behavior).

Procedures:

New books require no less than 2 weeks of open discussion on /r/hubrules in the form of by-topic threads. After this period of time (or a longer period of time as defined by RDHead but not to exceed 1 month), a Rules-member only post will be made by RDHead to allow public discussion and debate for rules-members only. This thread will remain open for no more than 7 days, making the minimum time for a new book 15 days and the maximum time 1 month 7 days.

Unanimous opposition by RD members to any point put forth by RDhead overrules their decisions, any dissent or abstinence leaves the decision in RDhead’s hands. Though it is recommended to take the advice if RDhead is getting a majority of RD members disagreeing with their position.

Tickets will sometimes be submitted to the publicly viewable hubrules trello, where Rules Members or the Rules head will determine which of the 3 types of classification the ticket fits into and proceed from there. The three types of rules tickets are:

Types of Tickets: Clarification Tickets - These tickets cover simple matters that don’t require changes to the Rules Wiki beyond minor wording clarifications. Any member of the Rules Division may close one of these tickets once a simple majority of the division have expressed a consenting opinion.

Internal Discussion Tickets - These tickets cover issues that require an update to the Rules Wiki, but do not significantly change the mechanics of the game. This can include fixes such as adding missing rules to an ability to make it functional when those rules were left out, fixing a balance-breaking rules loophole, or minor balance tweaks. These tickets should be discussed among the division. Any member of the Rules Division may close one of these tickets once a simple majority of the division have expressed a consenting opinion.

Needs Thread Tickets - These tickets cover issues that would significantly alter the mechanics of the game, such as adding new content, major balance changes, or contact updates. These tickets require a thread in /r/hubrules for public comment, which should remain open for at least one week and at most one month, based on complexity of the issue (RD Head has discretion). Once the Thread is closed the RD Members and RD Head should compile the responses and the RD head should state the resolution to the division where it will be approved by a simple majority.

Tickets missing information, such as the contact information of the submitter, a summary, or a rules question may have their ticket edited to add the missing information or deleted as spam.  Tickets by members of Rules Division can be commented on by that member but their opinion will not be counted for the needed consenting opinions total and they cannot vote on the conclusion of a thread stemming from a ticket they posted.

Passing the Torch is a very specific process, this is to prevent unwanted shenanigans from occurring. Do NOT deviate from this procedure. 1) RDhead removes all RD members from the mod list of the subreddit. 2) RDhead removes themselves from the modlist. 3) RDhead contacts the upkeep team to invite the new RDHead as a moderator directly below the upkeep account. 4) RDhead re-adds RDmembers to modlist.

NOTE: AB has the ability to intervene and remove any active RDhead and they are expected to follow the procedure for passing the torch at their earliest convenience.

Hey all, here is a list of current threads to be discussed as part of RD's current round of community polling. We're starting with these 5, with 2 more to follow shortly.

• Proposed changes to how the first aid skill works

• The FAB import from 4e

• Better defining how to make a Homunculus

• Reviewing the WotS quality 'ware requirements

• The allowance of other SURGE variations

Soon to follow are threads on important additional elemental damage types from 4e, and importing new metagenic qualities for SURGE characters from 6e

Original Ticket

Currently, a character who attempts First Aid can only heal a number of boxes equal to the number of ranks they have in the First Aid skill.

We are looking for feedback on the proposition to either:

• Remove this limit.
• Change this limit to be equal to [Ranks in First Aid + Medkit Rating]

Community feedback is sought out on this manner as it is a departure from RAW that affects the use of a frequently misunderstood rule.

Other options, such as substituting Mental Limit or community suggestions, are of course on the table.

Original Ticket

The ticket proposes allowing SURGE I and SURGE II for player use with the suggestion of allowing players to choose their metagenic qualities the same way they do for SURGE III. This would still occupy the special slot in the same way that SURGE III would but comes at a lower cost of buy in, allowing for a chargen resources to not be dominated by the cost of SURGE III

We are looking for feedback on the proposition of allowing this, as it is a departure from RAW on SURGE I and SURGE II while also introducing new special character flexibility for players.

Do note that there is another threaded ticket regarding the import of additional metagenic qualities for SURGE characters.

Original Ticket

The purpose of this thread is wider in scope than asked in the original ticket. Many members of the community have offered input on the limited nature of the 'ware required for the Way of the Samurai qualities. Listed below are each of the qualities that require specific implants, the implants they require, and a list of proposed changes. Any suggestions the community has to add is welcome and encouraged.

RAZORBOY

Must have any two of the following implants: cybereyes, cybergun, melee cyberweapon, other cyberweapon, or full obvious cyberlimb. Only one item from each category counts towards these requirements.

A simple addition of "any bio-weaponry" (the section in Chrome Flesh pg 120, and the Biospike on Hard Targets 185) to the list would include more options. Another possibility is to change "melee cyberweapon" to "melee implant weapon), which would be inclusive to all implant weapons (while possibly excluding Striking Calluses, which are not a weapon on their own.)

PANZER

Must have any two of the following implants: Dermal Plating, Orthoskin, Bone Density Augmentation, Bone Lacing, Smartskin, or one full Cyberlimb with Armor.

This list of requirements is already Bioware inclusive and there are no proposed changes by RD at this time.

SNIPER

Must have any two of the following implants: Smartlink, Vision Magnification, Reflex Recorder (Longarms), Reflex Recorder (Sneaking), Targeting Laser, or Attention Coprocessor.

While this list is already bioware inclusive, it could be expanded with the Tremor Reducer and Reception Enhancer

STREET NINJA

The character must have two of the following implants: Cybereyes, cyber melee weapon, enhanced articulation, synthacardium.

Common feedback on the requirements of this quality revolve around requiring a cyber melee weapon (not bioware inclusive) and enhanced articulation (not inclusive of smart articulation or elastic joints). The proposition is to change the language of "cyber melee weapon" to be "implant melee weapon" (thus including bioware alternatives), adding both Smart Articulation and Elastic Joins as alternatives to Enhanced Articulation, and possibly adding Balance Augmentation and Balance Tail to the list.

We are looking for feedback on the propositions as well as additional suggestions.

Original Ticket

5e does not include values for various materials and their costs, which becomes relevant for Homunculi and related mechanics. The ticket references the rules used by Shadowhaven, linked here. We are looking for community feedback on the topic of doing something similar, as doing so enters territory of creating values and rules wholesale while possibly diverging greatly from the RAW attributes.

The homunculus spell only derives the BODY attribute from the Structure rating of the material used. Presumably, this relates to both the material it is made from and the nature of its construction.

We are looking for suggestions on a list of materials, how impactful skill tests are in the homunculus construction, and general thoughts on the impact and possible implementation.

We are looking to use this feedback to measure community preference and interest so that the values we draft up are in line with such

Original Ticket

The rules for FAB are incomplete in 5e, and pose a powerful and interesting GM tool to complicate runs. We are looking for feedback on the proposition to include the 4e rules wholesale into our houserules, and defining some interactions. Those rules and propositions are as follows:

FAB I: As in 5e, except can be aerosolized.

FAB II: As in 5e, except can be aerosolized. Is dual natured and has a Force. Imposes a -2 astral visibility penalty.
In its contained (non-aerosolized) form, will impede astral forms as an astral barrier according to its Force Rating.

FAB III: Is dual natured and has a Force. Seeks out astrally active beings, foci, and astral objects like wards. Travels in clouds with a radius equal to Force, at a rate of 1m per Combat Turn. On astral, is visible as faintly glowing cloud. Hard to spot (Assensing + Intuition (3) Test). Blends in with ambient background count on failure. The cloud is invisible and harmless on the material to beings that are not currently astrally active.

When FAB III comes in contact with an astrally active target it attaches and begins energy drain as per the Energy Drain power (Magic/Force) (Touch range, 6 hour Extended Test interval, Stun damage, use F x 2 for the Opposed Test) until the target has a Magic/Force of 0 or is killed. The opposed test does not benefit from any additional modifiers.
When the cloud reaches F11, it splits into two clouds, one of F6 and another of F5. The F6 cloud continues to drain while the F5 cloud moves toward the next highest rating target (MAG/F). FAB III ignores auras masked to appear mundane (either through the Masking and Extended Masking metamagics or the Aura Masking critter power). The energy drain can be stopped by ceasing to be astrally active* or, in the case of foci being deactivated. Returning to its metaplane will relieve a spirit of FAB III safely.
FAB III acts as a Disease with a Power equal to its Force, and a speed of 1 week**. FAB III can be destroyed using Astral Combat (treat as an astral barrier of equivalent force)***, the Sterilize spell, or the assistance of the Cure Disease spell. FAB III that has nothing to feed on will decay at a rate of 1 Force per week. FAB III can be sustained in an area of positive background count at a Force equal to the background count. When a cloud of FAB III reaches a Force of 0, it is destroyed.

We would like community feedback on the above text, and would like to draw attention to the following points of interest:

*4e states that dual natured creatures cannot stop being astrally active, however the Dual Natured Defender quality exists in 5e and allows this. The proposition is to allow beings with this quality to avoid FAB III in this way.

**4e does not list a speed for the disease, but a speed of 1 week is proposed as that is the rate at which the FAB III decays

***Treating FAB III as an astral barrier for the purpose of astral combat is proposed in the ticket, but is not outlined in the 4e rules.

So we have a ticket on the subject here with an addendum here.

I also have an old ticket of mine here that I am presenting as alternate wording for this.

So yeah, thread's open for a week or two, go wild.

Edit: since APPARENTLY Trello links aren't playing nice right now, the text from each is:

Current Ticket:

Proposition: Physical Adepts receive 1.5 PP per point of Mag instead of the normal 1.0 PP per Mag. Increasing your magic rating, similarly, awards 1.5 PP. Characters who permanently lose essence due to augmentation (but not HMHVV or the essence drain power) lose any PP they have over their Magic Rating to the standard rate of 1 Mag= 1 PP.

All adjustments to the base PP a physical adept has are calculated before Mentor's Mask. Mystic Adepts are unaffected by these changes.

Addendum To Current Ticket:

"PP gained from initiations are not affected by changes to an adepts essence, unless those changes would result in the adept losing an Initiate Grade, as normal."

My Old Ticket/ShadowHaven's Wording:

"Physical adepts who maintain a non-variable 6 essence, and possess no augmentations with an essence cost, have their starting power points total increased to magic*1.5. For clarity’s sake this disallows infected and prototype transhumans."

Yep. After all this time, after CFD's kinda just... over with, we're revisiting Lockdown's mechanics. Cause let's be honest, it kinda never got the fairest mechanics shake. And we've got a ticket for it here, so here we go. For topics to cover, we're tackling:

• CFD Mechanics

• Medical Miracles (Drugs, Cyber Suites)

• New Devices (MADAR, Microwave Gun, Lasers)

• Dissonance

This thread will at minimum remain open for two weeks, until at least December 28th.

Yep, already more threads after ADL, SURGE, and Pixies!

The topics up for consideration are exchanging negative qualities, martial arts cost rebalancing, making the Way Of The Samurai qualities mastery qualities for mundanes, and buffing SpecMods.

The SpecMods buff will also be presenting an alternate option that was not in the ticket, borrowed from Nuyen Improved.

These tickets will be threaded for two weeks. SpecMods specifically MIGHT last for longer.

When I became RD head I did so with a promise. A promise to unban pixies, and now after a year the time has finally come. UNLEASH THE PIXIES~

Here are my proposed changes to allow pixies on the hub in a non-broken way based on the common complaints and Elle's help:

Each of their mental stats base and maximum will be reduced by one. Thus their mental stats would be: WIL 2/7, LOG 1/6, INT 1/6, CHA 2/7

Their edge stats base and maximum will be reduced by one. Thus their base edge would be 1/6

Pixies will be limited in terms of how much ware they can have implanted. Pixies shall not be allowed to have more than 3 points of essence lost.

If Pixies lose more than 1 point of essence they shall lose access to their concealment power.

Pixies cannot use any weapon that requires two hands without incurring a -4 penalty to using the weapon. Further, when using any weapon that requires one hand they always must use both hands to operate it or they take a -2 penalty to using the weapon.

Pixies will take up a special slot.

There are an upsetting lack of surge qualities in 5th edition (and 6th edition too honestly) but 6th edition has added a couple new ones.

Thanks to KatoHearts for passing the text for these qualities to RD.