[Organic Towns] New Sheet

[WilliamBarkerCoC]

Organic towns by Headless Hydra Press

Submission Checklist

Warning

Submission Checklist
Failure to complete this checklist in its entirety will result in your Pull Request being dismissed. If you have any questions, please feel free to create an issue.

Note

Draft Pull Requests
If you are unclear about any of the rules regarding the creation of character sheets, or need assistance from the Roll20 team, please feel free to create a Draft PR and request feedback. We'd much rather provide assistance than reject a PR.

Pull Request Title

Please format your pull request in the following way: [Sheet Name] Change Type: Description. For example: [D&D5e] New Feature: Adding dragons to dungeons.

• The pull request title clearly contains the name of the sheet I am editing.
• The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).

Pull Request Content

• The pull request makes changes to files in only one sub-folder.
• The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)
• The pull request does not, without express prior permission from affected parties, include any material that could be considered to infringe on a Publisher's intellectual property rights, such as logos, images, rules text or other rules content.

New Sheet Details

Please complete this section if you are adding a new sheet to the repository.

If you are submitting a new sheet to the repository, please fill in any empty spaces indicated by [ ].

• The name of this game is: [ Organic Towns ]

  (e.g. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

• The publisher of this game is: [ Headless Hydra Press ]

  (e.g. Wizards of the Coast, Evil Hat)

• The name of this game system/family is: [ Organic Towns ]

  (e.g. Dungeons & Dragons, FATE)

• The rules for this game can be found at the following location: [ DriveThruRPG ]

  (e.g. a link to purchase, ISBN, Half-Price Books)

• I have followed the Character Sheets Standards when building this sheet.

• I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.

Select EXACTLY One:

• This game is a traditionally published game.
• This game is not a traditionally published game.
• This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system. [ ADD DETAILS HERE ]

Changes / Description

New Sheet based on Headless Hydra Press's RPG

[roll20deploy]

Character Sheet Info Roll20 Internal Use only.

[WilliamBarkerCoC]

Based on a commission in the forums for Organic Towns, the requestor and playtester - Mirna - and myself have tried, unsuccessfully, to contact Headless Hydra Press, the publisher. They seem to have gone out of business, and thus we are unable to gain their permission. So no artwork was used on the sheet but there may still be content issues.

The concept of Organic Towns I found quite innovative. In this RPG, the party’s home base’s settlement is the character. The tag line could have been: “ Hey, did you hear? While the party was adventuring…”. There are multiple tables for random events based on Population, Defense, Crime, Morale and Trade. The party must balance resource gathering amongst Food, Water and Housing, while constructing buildings to meet those needs. Settlements can even go to war.

The problem, on a theoretical level, is that the game is almost exclusively about ‘character’ (i.e. the settlement) advancement, which on a surface reading, would violate guidelines. But taking a broader view, the sheet does not contain any of the lovely random event tables (which would be the only ‘rollables’ in the game). So the rulebook is still vital. What has been automated are three things: population growth (formula: Population = Population * (1 + PopGrowth/100)), MonthlySP = ceil(population/10), and the Monthly Budget based on expenses and incomes from buildings. This last one is definitely on (or over) the line about incorporating table values. Why was this chosen? Because I cannot imagine a gamer thinking: “Yes, what is really missing from my fantasy adventure is the need to manually calculate profit and loss for an entire town!” This could possibly be worked around by having a fourth sheet for known building types and their monthly expenses and having the player punch in the numbers from the manual, but, should we not try to minimize tedium? There are plenty other things to angst over: getting the resources to build, eliminating the bandit camp, solving that sudden drought…

On a personal note, this the first time spreading my wings, trying to anticipate players' needs with a Guildhall Registry and the ability to build unique buildings (such as a certain Chocolate Factory for Charlie to visit). And the tedium attenuating Maintenance Report.

[kfroll20]

Hey @WilliamBarkerCoC!

Thank you for submitting your work to the community repo and explaining the situation. I've reached out to our partner relations team to see if we can get more information since we are partnered with the publisher on DriveThru. I'll put an awaiting verification label on this PR and let you know of any information I receive!

[NBrooks-Roll20]

Hey @WilliamBarkerCoC, so far we also haven't had any luck reaching out to Headless Hydra. As this isn't an official sheet and you're not using any graphics, we should be good to submit this as a new sheet anyway - is that your intention? This PR is still a draft, so you'll need to move it into real PR status for us to handle it.

[WilliamBarkerCoC]

Thank you for your efforts in trying to reach the Publisher.
I am unsure of the steps needed to turn a Draft Request into a real request. Is it as simple as pressing the [Ready for Review] button? Or should the branch be closed and another opened with a new Request?
I'm still on unsure footing with GitHub processes

[kfroll20]

Thank you for your efforts in trying to reach the Publisher. I am unsure of the steps needed to turn a Draft Request into a real request. Is it as simple as pressing the [Ready for Review] button? Or should the branch be closed and another opened with a new Request? I'm still on unsure footing with GitHub processes

Yeah, you can go ahead and click "Ready for Review" button :)