Last post for the night.

When I started thinking about subsystems for games, I realized that a video would be much better for demonstrating the concept.

I have an old USB Camera, an old Linux computer, and OpenShot.

I think I'm ready. Just need to have a table downstairs. Bwa ha ha ha.

Work really lightened up the past week, so I have more brainspace to get things done. Woot!

    I haven't stopped working, but I haven't been able to write much.

The short version is that I am building infrastructure to make it easier for me to fully flesh out ideas and make well-structured PDFs for general consumption.

The long version started with my ideas from over a month ago to make short documents about subsystems for use in games. That led to searching for ways to easily to swap out one subsystem for a different way.

Specifically, if I decide to use playing cards (or UNO cards, or Rook cards) for initiative in The Black Hack, I wanted to swap out the initiative section of TBH for the card-based system. After the switch, I wanted to be able to quickly have my customized TBH in one document, ready to hand out to player and add to my GM screen.

The Black Hack is already available in markdown code, so it's easy to break it up into modules. Since all my TBH stuff began in markdown, I started working out a way to add in classes and magic items, swap out initiative, and replace the monster section. After that, I'd use a tool named pandoc to convert it into files for LibreOffice.

As I began doing that, I picked up a thread in the Basic Fantasy community that helped me finalized my process. I consider BF to be the closest thing to an open-source project. (The only thing missing is github.) I can get the entire source document and modify it. On a dare, I began to convert the entire BF rules into markdown. (I only have Chapter 8 left to convert.)

Not only did pandoc help me speed up the conversion work, but once it's finished, I should be able to convert it back into a LibreOffice file, with a specific template. The resulting file can then be imported into Scribus for layout work.

So I haven't stopped working, but I have come very close to having a process that works quickly and effectively.

    The rotating project that generated the martial arts brainstorm was a modularized version of Basic Fantasy Role-Playing Game. 

Why them? Frankly because it is run like an open source project. The only thing missing is a github account. 🙂

Since there is a source ODT file for homebrewing, it's possible to incorporate your house rules fairly easily. For people like me, however, it is not so easy to swap out entire subsystems.

So I am breaking up the ODT file into smaller documents. Using a Master Document in LibreOffice or Word, I can replace the smaller pieces and rebuild.

emerge -pU @World

Ultimately, the goal is to develop a workflow to produce games/houserules systematically:

I work up a playing card based magic item system, I fix the pieces describing magic item and rebuild the document.
I work up a martial arts system, add this new subsection, tweak the unarmed combat section, add a monk class, tweak multi-class rules, and then rebuild.

The entire workflow is similar to what I use now. The difference being the use of a master document to rebuild an entire game.

(I still use Typora to generate everything in markdown and pandoc to convert markdown to ODT/DOCX files. I still plan to use Scribus for layout.)