All Projects → A-Series-of-Dice-Based-Events → RiseOfTheRunelords

A-Series-of-Dice-Based-Events / RiseOfTheRunelords

Licence: other
A repository to hold tools for those wishing to run and convert RotR to Pathfinder 2E.

Programming Languages

Rich Text Format
576 projects

Projects that are alternatives of or similar to RiseOfTheRunelords

vscode-dmbinder
Visual Studio Code extension for managing campaign documents.
Stars: ✭ 53 (+23.26%)
Mutual labels:  pathfinder-rpg
Luminari-Source
Current Source Code for LuminariMUD - A Pathfinder/D20 Multi User Dungeon
Stars: ✭ 37 (-13.95%)
Mutual labels:  pathfinder-rpg

Rise Of The Runelords - 2E Conversion

A fan built repository for the conversion guides for those wishing to run and convert RotR to Pathfinder 2E. The README.md files for each book are the conversion guides. While the Statblocks folder for each book holds the individual monster/NPC stat blocks which are linked to from the guide.

Join us

To join us just ask @mirkorainer on GitHub or in the A Series of Dice-Based Events Discord

Once you're added as a member then you can add and approve changes. All the changes are tracked so if we make a mistake, we can refer back to the old version.

Recommended Tool

We generaly use the PF2 Monster Builder to create NPCs and Monsters. This uses JSON, PNG and PDF files, that can be easily imported/exported.

This repository holds those files publicly sourced and created, as well as other tools/files.

No Copyright Materials

Please do not submit PDF files or entire texts, or any images or maps from the AP. Only submit modifications necessary to convert to 2E, such as the DCs and 2E builds of NPCs/Monsters/Hazards/Items plus XP and 2E level based treasure. Please include a location number or name for each encounter or item so GMs can cross-reference with the original scenario.

Using Github

How does this even work?

What is Github?
On GitHub, you can share text files (and code) and collaborate with others. The nice thing is that README.md files display as you're browsing the folders of a GitHub Project using GitHub Markdown.

Making Changes

There's an in browser editor that makes it easy to change the files you see and submit a request to chave them permanently changed. There is also a Github Desktop app that allows you to work using standard desktop tools.

Just click into the file you want to change and select the edit button in the top right.

editor icon on GitHub After changing, there will be a button at the bottom of the browser editor to "Propose file change", feel free to include a message on why it was changed.

typing changes

submit changes After clicking that button, it will show you the changes you've made and have a new button near the top of the page to "Create pull request".

create a pull request

open pull request This sends the changes in to become permanent record in the repository.

submitted pull request Now you can comment on the changes and discuss with others that change before it's solidified.

comments section Members can now approve your changes.

where PRs go

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].