This is a writing tool inspired by the Celestial Forge; a similar system born from the Jumpchain fanfiction format. These writing tools center around a technological 'power set' for a character, in which they are bestowed with knowledge, skill and supporting powers randomly from a pool of abilities. The March serves as both a tool for automating the process of generating 'rolls' for such a writing project, but also as a similar framework without the IP complications of the original Forge. The base version of the March is available under CC-BY here, and can be used for any writing project, including commercial works. All 388 perks in this version of the March are original creations by yours truly (with a contribution from Blood_Librarian on SpaceBattles) and does not contain any material that I do not hold the copyright to. The extended version of the March is not yet available, but will introduce perks that directly reference media and specific fandoms.

Each roll on the March grants a hundred steps and then attempts to grant a random perk. If the perk has reached its repeatability limit, a new perk is rolled. Once a perk that can be granted is found, the cost is compared against the current number of steps. If the steps are insufficient, the roll fails. The March was designed with a series of 'dependencies'. These are perks that will be 'rolled' if a perk dependent on them is rolled. These are related perks or grant necessary abilities to use the perks in question. If a perk has any dependencies, these are resolved first, with their own dependencies resolved recursively. If there are not enough steps for a dependency, the dependent perk also fails. However, if the perk has simply met it's repeatability limit, then the depenedent perks still operate normally. Once all dependencies are resolved, the perk is once again evaluated for cost and should there be enough, the perk then is added to the successful perks for a roll. Some versions of the Forge that inspired this tool allow for perks to be held for later once enough points are accumulated or refused should they not be desired. The lack of such features is deliberate.

The version control is not yet set up, so please await such functionality, but the base March is functional. When loading, a random seed will be assigned to you. press the roll button in order to progress the March one roll. Feel free to roll whenever you wish. Traditionally, the rolls are made based on the wordcount of the story - a roll ever 1,000 words or so - but you can use whatever system you wish to decide when rolls are made. Some make use of milestone-based progression system, while yet others might roll for a set amount of time passing in the story. Each roll grants a hundred steps, and will randomly probe the collection of perks until it selects one that has not passed its receive limit. Any dependencies are resolved and then the perk is displayed according to the format specified in the options area. The formatting is fairly simple; the variables {{name}}, {{cost}}, {{description}}, {{times_recieved}}, {{reason}} will be replaced with the relevant information sourced from the perk. Then, all perks in the roll will be combined by placing the contents of the 'between perks' option between them. Note that if this is empty, no line breaks will be placed between the end of one perk and the start of the next. Finally, once all the perks in the roll are combined, the entire log of rolls are joined together with the Between Rolls option between them. The reverse options change the order in which the perks/rolls are joined. These should update automatically, so feel free to experiment with it however you wish. You can also edit the seed manually, and set the March to advance to a certain position. The download option generates a save file that can be stored in case you want a backup, but an updated copy is stored in your browser so the March should persist between sessions. The upload button similarly can load the contents of a save file. Save files are forward compatible within a single set. Additionally, while Core saves can be accepted by Extended Marches the reverse is not true.