This document details the guidelines for creating scenarios for the Pathfinder Society Infinite and Starfinder Society Infinite programs. Scenarios must meet these guidelines to qualify as Pathfinder Society Infinite Scenarios or Starfinder Society Infinite Scenarios. 

Note that Pathfinder Society Infinite Scenarios and Starfinder Society Infinite Scenarios must still meet the usual requirements for being a Pathfinder Infinite or Starfinder Infinite product. See the Pathfinder / Starfinder Infinite Content Creator Questions for more information.

As usual, the only license that applies to products released on Pathfinder Infinite and Starfinder Infinite is the Community Content Agreement for Pathfinder and Starfinder Infinite. You may not append the OGL, ORC, or any other license to your title.

Pathfinder/Starfinder Infinite Generative AI Policy

Paizo is concerned about the ethical implications of AI-generated content and its impact on the livelihoods of artists and writers, as well as their ability to maintain control over the use of their work. AI-generated content, including both visual art (e.g., Midjourney, DALL·E) and written material (e.g., LLMs such as ChatGPT), is not permitted in Pathfinder Infinite / Starfinder Infinite community content titles. No permission is granted to use Pathfinder or Starfinder materials in connection with any training of any AI tools.

What is Organized Play?

Paizo Organized Play (OP) is a worldwide roleplaying organization where players can take their Pathfinder Society and Starfinder Society characters and play in any game around the globe, creating a consistent and reliable campaign with a drop-in, drop-out play experience. Pathfinder Society Infinite Scenarios and Starfinder Society Infinite Scenarios can be played at any OP event, as long as they follow the guidelines presented in this document. More information on the Paizo Organized Play Programs can be found at the following links. 

Pathfinder Society Page https://paizo.com/pathfindersociety or pathfindersociety.club

Starfinder Society Page: https://paizo.com/starfindersociety or starfindersociety.club

Lorespire (Guide to Organized Play): https://lorespire.paizo.com 

General Scenario Requirements

The following guidelines detail general requirements for Infinite Scenarios.

The Society

Paizo has two primary Organized Play Programs: the Pathfinder Society Organized Play Program and the Starfinder Society Organized Play Program. In the Pathfinder Society, players create Pathfinder Second Edition characters who are members of the Pathfinder Society. In the Starfinder Society, players create Starfinder Second Edition characters who are members of the Starfinder Society. 

To ensure these programs remain distinct from one another, content from one game can’t be used in the other game. For example, a commercial laser pistol from the Starfinder RPG is not permitted in a Pathfinder Society Infinite Scenario.

Regardless of program, the Player Characters (PCs) are assumed to be heroes. Infinite Scenarios must be written with this in mind. Do not write scenarios that encourage evil deeds or villainy, or that require the PCs to participate in villainous acts to complete the adventure.

Venue- Appropriate Content

OP events are often played in public locations, such as local gaming stores and conventions, where people not involved in the program (including children) are present. Infinite Scenarios must be playable in these spaces. Do not include content in your adventure that is inappropriate for public consumption. Examples of inappropriate content include sexual content, violence against children, scenes of torture, racism and other forms of bigotry, and overly detailed descriptions of gross or horrific events. You can learn more about the assumed Pathfinder or Starfinder Baseline in the corresponding GM Core product (page 7 in both cases).

Levels

Scenarios are written for 2-level ranges, which indicate that PCs of either of the two levels listed can play the scenario. All Infinite Scenarios must be written for one of these level ranges.

• Level 1–2
• Level 3–4
• Level 5–6
• Level 7–8
• Level 9–10
• Level 11–12
• Level 13–14
• Level 15–16
• Level 17–18
• Level 19–20 

Length

Scenarios are designed to be played either within 2–3 hours or within 4–5 hours. These are strict time limits. The typical wordcount of a 2–3 hour scenario is 4,000–5,000 words and the typical wordcount of a 4–5 hour scenario is 9,000–10,000 words (excluding non-adventure content, such as the table of contents and credits). Regardless of wordcount, we highly recommend you playtest your scenario to ensure it can be run within this time limit.

Because of this hard-coded time limit, we must limit the number of encounters within a given scenario. 

• For 2–3 hour scenarios: Your scenario should include either one major encounter and up to five minor encounters OR two major encounters and up to four minor encounters. 
• For 4–5 hour scenarios: Your scenario should include either three major encounters and up to five minor encounters OR four major encounters and up to four minor encounters. 

Major Encounters

A major encounter is expected to take between 15–60 minutes of time to play out at the table, averaging between 30–45 minutes. The following are examples of major encounters.

• Combat encounters of Trivial, Low, Moderate, or Severe difficulty. Never include Extreme combat encounters
• Cinematic Starship Scenes of Trivial, Low, or Moderate difficulty. Never include Severe or Extreme cinematic starship scenes (For Starfinder Society Infinite Scenarios only)
• Tactical Starship Combats of Trivial, Low, or Moderate difficulty. Never include Severe or Extreme tactical starship combats (For Starfinder Society Infinite Scenarios only)
• Influence encounters using the Influence subsystem
• Long roleplaying encounters

Additional Advice: 

• Be cautious including Trivial combat encounters, as they often end before all of the PCs have a chance to act. 
• Don’t include Severe combat encounters in level 1–2 scenarios. 
• Never include Extreme combat encounters.
• For 2–3 hour scenarios: If your scenario includes two combats, we highly recommend using one Low combat encounter and one Moderate combat encounter. 

Minor Encounters

A minor encounter is expected to take up less than  15 minutes of time to play at the table. The following are examples of minor encounters.

• One complex hazard or two simple hazards
• Puzzles
• Skill-based challenges
• Short roleplaying encounters
• Chases using the Chase subsystem
• Hacking encounters using the Hacking subsystem (For Starfinder Society Infinite Scenarios only)
• Performing a ritual

Additional Advice: 

• Hazards work best when paired with creatures. When paired in this way, a hazard becomes a part of a combat encounter, meaning the hazard and the creatures it's paired with in the combat encounter count as a single major encounter.
• Simple hazards work best when foreshadowed earlier in the adventure, or when they serve a wider narrative purpose. 
• If the PCs are likely to explore three or more rooms or areas on a map that contain interesting features, treasure, or other details, but don’t contain encounters of their own, the exploration of these non-encounter areas likely occupies the same amount of time as a minor encounter and we recommend counting it as such.

Subsystems

Both the Pathfinder and Starfinder RPGs include a number of subsystems. These subsystems are of variable complexity and runtime. Use the following guidelines to manage subsystem use.

• You can use a maximum of one subsystem per scenario, and you can include a maximum of two encounters using that subsystem. 
• Never include or create custom subsystems.
• The influence subsystem is time consuming and complicated and always counts as a major encounter.
• The chase and hacking subsystems are swift to resolve at the table, and usually count as a minor encounter
• The remaining subsystems, including infiltration and research, take a variable amount of time to resolve based on their design. Be sure to test your subsystem-based encounters to accurately estimate runtime and determine if they qualify as a major encounter or minor encounter.
• Custom simple Victory Point encounters are permissible but must be designed to be a minor encounter. Such encounters are best used to quickly track the PCs’ effectiveness or progress at achieving or preventing a task or narrative stake, such as measuring how well the PCs assist an NPC with labor, how swiftly the PCs navigate a labyrinth, or tracking how many civilians the PCs save during an emergency evacuation. Do not make complex or long custom Victory Point encounters. 

DCs

Using the lowest level in your scenario’s level range, consult the Level-Based DCs table to determine the ideal DC for your scenario (Pathfinder/Starfinder GM Core 52). When you assign a DC to a skill check or saving throw that’s not determined by a stat block (such as a creature or hazard, which have their own guidelines), use this ideal value as the baseline. The DCs in your scenario should be this ideal value, with a variance of up to +/– 2. If a check is meant to be extremely easy or extremely challenging, you can instead have a variance of up to +/– 4 from the ideal value, but such inclusions should be very rare and the PCs should be able to progress through the scenario even if they fail all extremely challenging checks.

Building and Balancing Encounters

All encounters must be designed for a group of 6 PCs of the lowest level in the scenario’s level range. For example, the encounters in a level 1–2 scenario are designed for a group of 6 level 1 PCs, while the encounters in a level 5–6 scenario are designed for a group of 6 level 5 PCs. 

To determine the XP Budget of an encounter, use the Encounter Budget table (Pathfinder/Starfinder GM Core 75), select your encounter difficulty, take the XP budget for your encounter difficulty and add the Character Adjustment value to it twice. This results in the following values.

When selecting creatures and hazards for your scenario, follow the additional guidelines.

• You can include creatures a maximum of 2 levels higher than the lowest level in your scenario’s level range. For example, in a level 1–2 scenario, you can include creatures of up to Creature 3. Using creatures of a higher level than this is very likely to result in the death of all lower-level PCs.
• We recommend using hazards of the lowest level in your scenario’s level range, or the lowest level –1. However, you can include hazards a maximum of 1 levels higher than the lowest level in your scenario’s level range. For example, in a level 1–2 scenario, you can include hazards of up to Hazard 2. Using hazards of a higher level than this is very likely to result in the death of lower-level PCs.

Adjusting Difficulty

Every combat encounter, cinematic starship scene, and tactical starship encounter must include an “Adjusting Difficulty” sidebar (following the format detailed under scenario organization) that provides GMs directions for making the encounter “Easier” and “Harder.” We recommend you also include these sidebars for other encounters, such as complex hazards, chases, and all other subsystem and victory point encounters.

Easier: The easier entry provides GMs directions for quick changes they can make to the encounter to reduce the difficulty of the encounter to suit a group of 4 PCs of the lowest level in your scenario’s level range. This usually includes removing creatures from the encounter, applying the weak adjustments to creatures in the encounter, lowering the DCs of hazards and skill checks, reducing the number of successes required to disable a complex hazard, or reducing the number of Victory Points required to overcome an obstacle or Victory Point threshold.

Harder: The harder entry provides GMs directions for quick changes they can make to the encounter to increase the difficulty of the encounter to suit a group of 6 PCs of the highest level in the scenario’s level range. This usually includes adding creatures to the encounter (of the same type already present in the encounter), applying the elite adjustments to creatures in the encounter, increasing the DCs of hazards and skill checks, increasing the number of successes required to disable a complex hazard, or increasing the number of Victory Points required to overcome an obstacle or Victory Point threshold.

For example, consider the following encounter. In a level 3–4 scenario, the PCs fight a Low encounter against three lumocanthas (Starfinder Alien Core 107) in encounter A. As this scenario is designed for a group of 6 level 3 PCs, a low encounter has an XP budget of 90 XP (60 XP budget + 15 XP character adjustment + 15 XP character adjustment = 90 XP). As a Creature 2, the lumocanthas provide an XP award of 30 XP each, for a total of 90 XP for three of them. The Adjusting Difficulty sidebar might look like this:

Adjusting Difficulty

You can adjust the difficulty of encounter A by making the following changes.

Easier: Remove one lumocantha from the encounter.

Harder: Add the elite adjustments to the lumanthas.

The easier adjustments are designed to accommodate a group of 4 level 3 PCs, which has an XP Budget of 60 XP. Removing one lumocantha from the encounter results in a 60 XP encounter.

The harder adjustments are designed to accommodate a group of 6 level 4 PCs, which still has an XP budget of 90 XP, but the lumocanthas are now only worth 20 XP each, not 30 XP. In this example, applying the elite adjustments increases each lumocantha to Creature 3, which increases the XP award for defeating them back up to 30 XP. Alternatively, you could add one lumocantha to the encounter (for a total of 80 XP) or add two lumocanthas to the encounter (for a total of 100 XP). Both of these alternatives are close to the 90 XP we’re aiming for, and would be suitable adjustments.

Using Creatures, Hazards, and other Content

Your scenario can include custom creatures and hazards created specifically for the scenario, with the stat blocks included in your adventure. Your scenario can reference 

creatures, hazards, equipment, spells, and other content from the following sources.

Pathfinder Society Infinite Scenarios can additionally reference: 

• Creatures and hazards of any rarity from Pathfinder Second Edition products that have been released under the ORC license from Paizo, such as Pathfinder Monster Core, Pathfinder Monster Core 2, Pathfinder NPC Core, Pathfinder Howl of the Wild, Pathfinder Hell’s Rebels Adventure Path, Pathfinder Society Scenario #7-01: Intro to the Year of Battle’s Spark: Enough is Enough, Pathfinder Quest #27: Within the Glacier, and more. 
• Spells, items, and other content of any rarity from Pathfinder Second Edition products that have been released under the ORC license from Paizo.

Starfinder Society Infinite Scenarios can additionally reference: 

• Creatures, starships, and hazards of any rarity from Starfinder Second Edition products that have been released under the ORC license from Paizo, such as Starfinder Alien Core, Starfinder Alien Core 2, Starfinder Tech Core, Starfinder Guilt of the Grave World Adventure Path, Starfinder Society Scenario #1-09: Abduction, and more.

• Spells, items, and other content of any rarity from Starfinder Second Edition products that have been released under the ORC license from Paizo.

Regardless of system:

• You can’t include content from books printed under the OGL, that come from other Infinite products, or that come from other 3rd-party publishers.
• You can’t include Pathfinder content in Starfinder Society Infinite Scenarios, and you can’t include Starfinder content in Pathfinder Society Infinite Scenarios. In Infinite Scenarios, the games must be kept separate.

Treasure

Every scenario gives out treasure. Remember that any treasure and equipment the PCs discover in your scenario can be used by them until the end of the scenario; they don’t keep these items beyond this scenario. At the end of the scenario, each PC receives a standard gp or credit payment for their labor, which is noted on their chronicle sheet. Use the following guidelines when including treasure and equipment in your scenario.

• You can give out any treasure you desire, so long as it meets the content inclusion guidelines mentioned above.
• Do not include treasure bundles. PCs always receive maximum rewards for completing a Pathfinder Society Infinite Scenario or Starfinder Society Infinite Scenario.
• After every mission briefing, the PCs must receive some items to use in the adventure. At minimum, we recommend giving out some healing potions or medpatches of a suitable level for the scenario. See Scenario Organization later in this document for more information on mission briefings.
• We recommend that most of the items and equipment the PCs can acquire in your scenario are of the same level as your scenario’s level range and lower. When including higher-level items and equipment, we recommend you do so rarely, and keep those items within 2 levels of your scenario’s level range. For example, in a level 3-4 scenario, most of the items you give out as treasure should be of item level 4 and lower and, when you give out a higher-level item, it should be of item level 5 or 6.
• Don’t create custom items or equipment in your scenario.

Maps

Every combat encounter in your Infinite Scenario must have a map clearly associated with it. You can associate other encounters in your Infinite Scenario with maps, if desired. You can create custom maps. You can include maps selected from any Pathfinder Flip-Mats or Starfinder Flip-Mats in the Infinite Society Map Assets package. The maps included must be low-resolution. All Paizo-produced maps must be clearly labeled with the product name from which it came so that Game Masters can seek out the physical product or higher-resolution digital versions for their own use. You can hire someone to produce a map for your scenario, but you can’t use stock maps that are released under any other license (including Creative Commons, etc.) It is your responsibility to ensure that you have the right to publish any map you include in your scenario.

Scenario Organization

The following guidelines detail how scenarios are organized, including which portions are required for Infinite Scenarios and which are optional additions. For a visual example of any of these sections, reference any recent Pathfinder Society Scenario or Starfinder Society Scenario.

Cover

You must use either the Pathfinder Society Infinite Scenario or the Starfinder Society Infinite Scenario template for your cover. Do not number your scenario. You must include the scenario’s title, author, level range, and play time (4–5 hour scenario or 2–3 hour scenario).

Legal Declaration

All Society Infinite Scenarios released on Pathfinder Infinite or Starfinder Infinite must include the following legal declaration in a clearly visible place, preferably the title page:

[[XXProduct_Name]] © [[XXYear]], [[Your name or company name here]]. All rights reserved. Paizo, the Paizo golem, Pathfinder, Starfinder, and other trademarks owned by Paizo are property of Paizo Inc. This work is published under the Community Content Agreement for Pathfinder Infinite and Starfinder Infinite. This [[Pathfinder or Starfinder]] Society Infinite scenario adheres to the Pathfinder and Starfinder Society Infinite Scenario Guidelines at the time of publication.

If you are using content through another license that requires attribution, such as Creative Commons CC-BY, you must include all attributions that such license requires. Note that use of content from Open Licenses or Share-Alike Licenses (those that require you share your derivative work in a similar fashion, like the OGL, ORC, and CC-BY-SA licenses) is not permitted under the Infinite License.

Credits and Table of Contents

You must include credits and a table of contents. The table of contents must additionally include the following: 

• How to Play: This portion clearly notes the play time of your scenario (which must be either 2–3 hours or 4–5 hours), the level of your scenario (which must be one of the level ranges), and the number of players who can play it (which must be 3–6)
• GM Resources: This portion lists the campaign home page link, the books GMs require to run your adventure, the flip-mats GMs require to run your adventure, and the online reference document link for the associated game system.
• Level and Difficulty: This portion must include the following text, with the character levels adjusted to match your scenario’s level range. “This scenario can be played by characters of 1st or 2nd level. The encounters in this scenario are designed for a group of six characters of 1st level. You can use the Adjusting Difficulty sidebars to make the adventure easier or harder, to accommodate groups of various sizes and levels. For more information, see the Guide to Organized Play at https://lorespire.paizo.com/ “
• Summary: This portion is a very brief summary of your scenario.
• Content Warning: This portion is optional. If you believe your scenario requires a content warning, include the following text, with the content warning adjusted to reflect your scenario. “This scenario contains themes related to [insert your content warnings here]. Before you begin, understand that player consent (including that of the Game Master) is vital to a safe and fun play experience for everyone. You should talk with your players before beginning the adventure and modify descriptions of the narrative as appropriate.”

Note: Infinite Scenarios don’t have tags so tags shouldn’t be included on the Table of Contents.

Adventure Background

Every scenario must include an adventure background section, including a header and any background information a GM requires to understand and run your scenario.

Additional Advice:

• Whenever you use a proper noun, regardless of whether it’s a custom creation or from the Pathfinder or Starfinder setting, we recommend you include a short description or explanation of that noun. The Pathfinder and Starfinder RPGs both have expansive settings and lore, and no reader or GM will immediately understand all the nouns in our setting. Including a short explanation ensures they can use your adventure without looking up a lot of nouns.
• The first time you mention a named character in your scenario, regardless of whether it’s a new character or an existing one from the Pathfinder or Starfinder setting, we recommend you include a mini-stat line for that character. These are formatted as follows: Character Name (personality-descriptor gender ancestry career-or-role). Aim to make the information included useful for GMs roleplaying that character. For example, Eliza Petulengro (astute female human diviner) and Venture-Captain Arvin (friendly male damaya lashunta mentor).

Getting Started

Every scenario must include a getting started section, including a header, mission briefing, treasure, and hero points. These portions are detailed below.

Mission Briefing

A mission briefing is a mandatory part of the Getting Started section and isn’t separated with its own header. It begins with a short description that clearly indicates where the scenario begins and who the PCs’ point of contact is for this scenario. This is followed by a read-aloud boxed text that includes some dialogue spoken to the PCs by their point of contact. This point of contact is usually a prominent member of the Pathfinder Society or Starfinder Society, such as a venture-captain. Keep this boxed text clear and concise; if it’s long, players are more likely to lose track of what’s being said or become confused. By the end of this boxed text, the PCs should know enough to proceed with the scenario and complete their assigned mission.

Q & A

During the mission briefing, the PCs have an opportunity to ask questions of their point of contact. While it’s not required, we highly recommend you include a list of the most likely questions the PCs will ask their point of contact, and include the answers to those questions as spoken by the point of contact, in a question and answer format. This Q&A portion is located after the boxed text in the mission briefing.

Recall Knowledge

During the mission briefing, the PCs have an opportunity to attempt skill checks to learn more about their mission. Usually, this includes a Diplomacy check to Gather Information and several skill checks to Recall Knowledge. While it’s not required, we highly recommend you include the results of such checks here for the GM, with information sorted by the degrees of success, including false information the PCs might learn on a critical failure.

Treasure

During the mission briefing, the PCs are given some equipment by their point of contact to use during this scenario. They don’t get to keep this equipment when the scenario ends. You must include a list of items the point of contact gives the PCs. Ensure the items given are useful during your scenario and meet the treasure guidelines from the General Scenario Requirements portion of this document.

Hero Points

At the end of the mission briefing, include a subheader that reads “Hero Points” followed by the following text: “Once the PCs are ready to proceed with the scenario, remind the players

that they each have 1 Hero Point available.”

Location Sidebars

Every scenario must include a location sidebar that provides GMs information on where the scenario takes place and in what sourcebooks they can find more information on these locations. The specifics of this sidebar vary by programs. In either case, the first paragraph details the specific place that scenario occurs in, such as a building, city, district, or geographical region, and the second paragraph details the nation (in Pathfinder) or planet (in Starfinder) that place is located within. At the end of this second paragraph, include a list of sources the GM can reference for more information on these locations.

Where on Golarion

Pathfinder Society Infinite Scenarios have a “Where on Golarion” sidebar.

Where in the Universe

Starfinder Society Infinite Scenarios have a “Where in the Universe” sidebar. In addition to the previously noted information, you must indicate the location’s gravity and atmosphere. If the scenario takes place on a planet, you must include this additional information as part of a planet stat block in between the two paragraphs. This stat block includes the following information. 

Planet Name

Planet Nickname (if applicable)

Gravity level (such as standard, low, or high); Atmosphere type (such as standard, thin, or thick)

Day length (such as 12 hours); Year length (such as 18 months or 2 years)

Headers and Subheaders

After the mission briefing, present the rest of your scenario. Use headers and subheaders to clearly organize the different parts of your scenario. The headers you use throughout the rest of your scenario are up to you, with the following guidelines.

Areas

The term “area” denotes a mapped location. The first area in your scenario is area A, followed by area B, and so on. The header for area A should begin with the area letter, followed by the name of the area. For example, “A. Bandit Hideout” or “B. GeneTech Laboratories.”

Each area should include a description of the associated map’s important features, such as light levels, ceiling height, areas of difficult terrain or cover, elevation differences, whether any doors are open, closed, or locked, and so on.

If the area has multiple smaller rooms or areas within it, each of those rooms is labelled alphanumerically, such as area A1, area A2, area A3, and so on. Each of these areas should be clearly described within the broader location, usually with each under its own subheader.

Events

The term “event” denotes an encounter, event, or cutscene in your scenario that is triggered not by location, but by time or the actions of the PCs. Events are named numerically, beginning with Event 1, Event 2, and so on. The header begins with the Event’s number, followed by the title of the event. For example: “Event 1: Ambush” or “Event 2: A Glamorous Entrance”

Running Text Headers

The following subheaders are common in running text and are used to further organize your adventure’s encounters.

Hazards: Include information on any hazards in the encounter after this subheader, such as why the hazard exists, what area it affects, how it might be triggered, and any other complications or details that are important. 

Creatures: Include information on any creatures in the encounter after this subheader, such as what creatures are present, their motives, their tactics, where they begin the encounter, the conditions under which the creatures might flee or be defeated, and any other details that are important. 

Other common running text subheaders include treasure, rewards, and developments.

As before, ensure any included boxed text included in your scenario is clear and concise. Use boxed text sparingly.

Conclusion

The final part of your scenario is the conclusion, under a conclusion header. This should include information on what happens immediately after the final encounter of the scenario, the point of contact’s response to the PCs’ success or actions, and any other relevant details and information.

Reporting Conditions

Don’t include reporting conditions in Infinite Scenarios.

Primary and Secondary Success Conditions

Don’t include primary and secondary success conditions in Infinite Scenarios.

Faction Notes

Don’t include faction notes in Infinite Scenarios.

Event Reporting Form

Don’t include an event reporting form in Infinite Scenarios.

Chronicle Sheet

Include a Pathfinder Society chronicle sheet in Pathfinder Society Infinite Scenarios and a Starfinder Society chronicle sheet in Starfinder Society Infinite Scenarios. These chronicle sheets are provided in the Infinite Society Asset Pack. On the chronicle sheet, fill in your scenario’s title, levels, gp/credits, and summary. The gp/credits are based on character level, as noted below. 

Monetary Rewards by Level

For Pathfinder Society Infinite, you may additionally fill out the items section on the chronicle sheet. To do so, list all of the items PCs might collect in your scenario which are of the highest level in your scenario’s level range or higher. In parentheses after each item, list the item’s level, cost, and source (only include a source for items not from a Core book). 

For example, in a level 1–2 Pathfinder Society Infinite Scenario, you would list all included items of level 2 and higher, formatted as follows:

lesser healing potion (level 3, 12 gp)

siege shield (level 3, 60 gp; Pathfinder Battlecry! 124)

silver salve (level 2, 6 gp)

tatzlwyrm’s gasp (level 2, 6 gp; Pathfinder Howl of the Wild 111)

Boons

Pathfinder Society Infinite and Starfinder Society Infinite Scenarios may include one boon on their Chronicle Sheet, if desired. This boon must be tied to the events of your scenario and must do one of the following:

• Make the earning PC liked or hated by a specific NPC or organization in your scenario. The NPC or organization can’t be the Pathfinder Society, Starfinder Society, or a member of these groups. 
• Give the earning PC a non-unique title (meaning a PC could be a lord, but not a king) within an organization, nation, or region; or provide property (such as a residence, business, plot of land, or asteroid).
• Provide the earning PC a +1 typed bonus on a specific action or save (e.g. +1 circumstance bonus to Recall Knowledge about fiends or a +1 item bonus to Will saves against fear).
• Add a reward that has no tangible in-game benefit, such as adopting a pet or getting a souvenir from a festival.

Boons can never:

• Grant access to content prohibited from use in the campaign, including content from a different roleplaying game.
• Create new rules content, such as items, spells, archetypes, feats, ancestries, or similar.
• Create untyped bonuses, stacking bonuses, or bonuses higher than +1.
• Harm PCs without their informed consent (e.g. applying a curse to a PC who did not knowingly and willingly receive that curse).