<commit_before>Table of Contents
=================

  * [Table of Contents](#table-of-contents)
  * [dftools](#dftools)
    * [Introduction](#introduction)
      * [Compiling](#compiling)
    * [Sierpinsky](#sierpinsky)
    * [LSystem](#lsystem)
    * [Geometry](#geometry)
    * [Everything else (As of now)](#everything-else-as-of-now)
      * [Reactions and raws](#reactions-and-raws)
  * [Software used in this](#software-used-in-this)


dftools
============
Tools for Dwarf Fortress. 

It has come to many people's attention that Dwarf Fortress' gui leaves a lot to be desired. There exist plugins that improve its usability these days but often with intricate or large designs, it proves tedious to create these ingame. These tools are meant to remedy this.

Introduction
--------
The majority of tools in this repository are aimed at producing comma-separated-values files to use as input for quickfort or dfhack. Some of them are merely tests for functionality that has been written, so most of them probably won't be useful.

Some of them are however interesting and capable of being used for acts of great !!fun!!.

###Compiling

I've been developing this on linux, without any concessions to Windows or Mac, so there may be issues that are unresolved on both platforms, as there *are* issues unresolved on linux, but there aren't any libraries that are required other than a libc that has a unistd.h header with a ``getopt`` function

So typical instructions for linux looks like this:
```
cd dftools
make
```

magical, isn't it?

However there is no ``make install`` or similar utility to place them on your path. If you want that, then please consider moving the files that you want to a directory like `~/bin` which you would then add to the path.

Sierpinsky
----
Have you ever considered using a sierpinsky curve as the basis for your fortress? No, that's not surprising. In any case, it happens to be a starting point for the travelling salesman problem as it tends to provide a decent route for said salesman for no examination of the graph.<commit_msg>corrected typo<commit_after>Table of Contents
=================

  * [Table of Contents](#table-of-contents)
  * [dftools](#dftools)
    * [Introduction](#introduction)
      * [Compiling](#compiling)
    * [Sierpinsky](#sierpinsky)
    * [LSystem](#lsystem)
    * [Geometry](#geometry)
    * [Everything else (As of now)](#everything-else-as-of-now)
      * [Reactions and raws](#reactions-and-raws)
  * [Software used in this](#software-used-in-this)


dftools
============
Tools for Dwarf Fortress. 

It has come to many people's attention that Dwarf Fortress' gui leaves a lot to be desired. There exist plugins that improve its usability these days, but often with intricate or large designs, inputting these proves tedious and therefore is error prone.

These tools are meant to remedy some of these problems.

Introduction
--------
The majority of tools in this repository are aimed at producing comma-separated-values files to use as input for quickfort or dfhack. Some of them are merely tests for functionality that has been written, so most of them probably won't be useful.

Some of them are however interesting and capable of being used for acts of great !!fun!!.

###Compiling

I've been developing this on linux, without any concessions to Windows or Mac, so there may be issues that are unresolved on both platforms, as there *are* issues unresolved on linux, but there aren't any libraries that are required other than a libc that has a unistd.h header with a ``getopt`` function

So typical instructions for linux looks like this:
```
cd dftools
make
```

magical, isn't it?

However there is no ``make install`` or similar utility to place them on your path. If you want that, then please consider moving the files that you want to a directory like `~/bin` which you would then add to the path.

Sierpinsky
----
Have you ever considered using a sierpinsky curve as the basis for your fortress? No, that's not surprising. In any case, it happens to be a starting point for the travelling salesman problem as it tends to provide a decent route for said salesman for no examination of the graph.
{'fraction_non_alphanumeric': 0.08536585365853659, 'fraction_numerical': 0.0, 'mean_word_length': 4.21571072319202, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '153908', 'n_tokens_mistral': 1147, 'n_tokens_neox': 1057, 'n_words': 591}