Skip to content
Snippets Groups Projects
Select Git revision
  • fix/dont_save_partition_table_of_mapper_devices
  • fix_11285
  • master default protected
  • debian
  • pristine-tar
  • upstream
  • backupninja_debian/1.0.2-1
  • backupninja_upstream/1.0.2
  • backupninja-1.0.2
  • backupninja_debian/1.0.1-2
  • backupninja_debian/1.0.1-1
  • backupninja_upstream/1.0.1
  • backupninja-1.0.1
  • backupninja_debian/1.0-1
  • backupninja_upstream/1.0
  • backupninja-1.0
  • backupninja_debian/1.0_rc1-1
  • backupninja_upstream/1.0_rc1
  • backupninja-1.0-rc1
  • backupninja_debian/0.9.10-2
  • backupninja_debian/0.9.10-1
  • backupninja_upstream/0.9.10
  • backupninja-0.9.10
  • backupninja_debian/0.9.9-1
  • backupninja-0.9.9
  • backupninja-0.9.8.1
26 results

backupninja

  • Clone with SSH
  • Clone with HTTPS
  • Forked from Liberate / backupninja
    Source project has a limited visibility.

    These config files make the BIND RPG books look and act the way they do.

    Usage

    To make a book, put this config folder into the same directory, and copy main.tex into the directory.

    Edit 'main.tex', and input your tex files by writing `\include{my_file.tex}.

    Creatures

    You can include pseudo-randomo creatures in your adventure by summoning the names from monsters.tex. For example, to place a random elf in your game, just write \elf, and an elf will be magically summoned unto your adventure. You can give the character a title and name by writing '\npc{symbol}{name}'. For example:

    
    \npc{\M}{Rincewind}
    
    \humanalchemist
    

    This would make a heading called Rincewind in bold with a male symbol, and provide pseudo-random alchemist-appropriate stats underneath.

    Syntax Symbol
    \M Male
    \F Female
    \G Group
    \U Undead
    \N Nura

    For a complete list of all the creatures and characters which can be used, see the 'monsters.tex' file. For more details on the syntax, have a look at examples in Adventures in Fenestra, or read the git's wiki.

    TeXnical Details

    This thing's handled as a subtree in the other documments, so changing it will change all BIND books.

    Personally, I keep it in a directory by the others. This allows you to do:

    git subtree -P config pull ../config master

    The configs also have one branch per repo, so when writing Adventures in Fenestra ('aif'), you can do a push to just that branch:

    git subtree -P config push ../config aif