These two generators were my first attempt and need to be rewritten to follow the conventions of the others; specifically ensuring data structures use "name" rather than "text" for colors on stars.

• Data needs to be normalized
• Handlers need to be added to megacosm.py
• new template needs to be created.

planets, countries, etc all need to have an add_*() method for their children, and it needs to be called by megacosm.py

This is best summed up here:

http://stackoverflow.com/questions/21766929/transforming-simplex-map-for-uv-mapping-on-a-sphere

Some things need to be generated in groups- for example, bonds, legends, even items.

How can we accomplish that?

Misfires have a large list of potential templates and data that need to be used.

Controls suck; I want to be able to zoom in and out without a scroll wheel.

22:47 < causative> most of them check out
22:47 < causative> Yesterday, Surplak imagined you without clothing on accident - "by accident"
22:48 < causative> Years ago, Gab Wobbjet discovered that you has a deep, dark secret.- have a deep, dark secret
22:51 < morgajel_> {{params.partyA}} discovered the deep, dark secret that {{params.partyB}} hid.
22:57 < causative> accidentally lead to the arrest of - should be "led"
22:58 < morgajel_> https://github.com/CityGenerator/Megacosm-Generator/blob/develop/data/bond.data
22:58 < causative> already looking at it
22:58 < causative> {{params.partyA}} camped together recently - one person camped together?
22:59 < causative> {{params.partyA}} claim to have given {{params.partyB}} something of value. - "claim" should be "claims" if params.partyA is not "you"
23:00 < causative> {{params.partyA}} cleaned {{params.partyB}} armor acter losing a bet. - it should be {{params.partyB}}'s armor, or "your" armor in the case of you
23:01 < causative> also "after" not acter
23:02 < causative> {{params.partyA}} dared {{params.partyB}} to do something stupid- ending in arrest, fines and community service. the hyphen should have a space on both sides of it
23:03 < causative> hey, you have things of the form {{params.partyB|capitalize}} - you can use that for verb tense, like {{params.partyB|was}} would give "were" if params.partyB is you
23:04 < causative> also you can use it for possessives
23:05 < causative> {{params.partyA}} nearly drown trying to save {{params.partyB}} - drown/drowns depending on partyA
23:05 < causative> actually just change it to drowned since you want past tense
23:07 < causative> {{params.partyA}} thinks of excuses for {{params.partyB}} when they're needed - I think you want past tense, "thought"
23:07 < causative> well, see, you want "thought" if it comes with a time prefix, but you do want "thinks" if there is no prefix
23:07 < causative> or "think"
23:10 < causative> {{params.partyA}} hums to drive {{params.partyB}} crazy - again present tense, and hum/hums
23:11 < causative> {{params.partyA}} likes to hunt with {{params.partyB}} - present tense
23:12 < causative> oh there's 3 that are "on accident" (should be "by accident")
23:13 < causative> {{params.partyA}} nearly killed {{params.partyB}}, and {{params.partyB}} knows it. - know/knows
23:13 < causative> {{params.partyA}} lock {{params.partyB}} in the bottom of a privvy. - locked, and privy
23:15 < causative> {{params.partyA}} peeped when {{params.partyB}} is changing. - was/were changing
off till tomorrow, what you can do the day after tomorrow]
23:15 < causative> permited -> permitted a few places
23:17 < causative> that's the last of em :)

When tunnels run across an existing tunnel, give them a 50% chance of stopping.

Not sure how to calculate this yet.

This should be easy enough to do, but the dungeons need some refactoring first.

I'm not real happy with all of the colors; specifically things like "banana" need to be renamed so that a "banana apple" is a "banana-colored apple".

What drives someone? Abstract it out.

is the religion growing or dying out? are they organized tightly or loosely?

Glimbo reports geomorph generator doesn't show tiles in firefox 28. I confirmed similar with FF 27.

If a country has a corruption level, that corruption level should influence(but not set) the corruption level of the cities within;

i.e. a very corrupt country will have more corrupt cities.

This goes for many generators and stats.

I think I'm going to end up with several different generators for dungeons, so some specificity should be added.

This may replace the need for .text, or may simply call it, but it needs to be consistent.

We need entries for how business is going, current troubles, etc. and to make sure the templates show all the values.

what other stats and feature would be useful for a business?

What races do we want to add? Here's a list of potential candidates. I'll admit, the hardest part is generating the name parts.

Crab People
Myconids
Tengu
Bugbear
Hobgoblin
Catfolk
Ratfolk
Merfolk
Gnoll
Centaur
Dragonborn
Satyr
Tiefling
Aasimar
Grimlock
Hagspawn
Yuan-ti
Warborn
Gargoyle
Troll

How Pious is the npc? add a stat

We need holy symbols for deities; both initial images and variations.

The pattern should be changed to resemble the other add_*() methods.

Cuisines currently only have a rarity stat; imagine what else they could have- spice, presentation, flavor, dish size, etc.

"Down the path you see an old man packing and lighting his pipe. He does not appear too notice you. Leaning against his knee is a well used axe.

The old man is friendly and gruff but unwilling to give away information for free."

business age and neighborhood could both be stats.

I need to balance out classes with professions; should they be separate, or intertwined?

If so, should they be weighted?

loot generator would be a variation of the magic generator but just random non magic loots. I could put in a range of items to be generated say 4-7 items and it would generate them. Perhaps a small percentage chance of something magic could happen.

we need to rethink how geomorphs are stored on the FS and in redis.

I think

/static/images/geomorphs/[0-5]/*.png

should be changed to

/static/images/geomorphs/[author]/[tileset]/[0-5]/*.png

Which can then be stored in redis as

LPUSH geomorph_tile_[0-5] {"path":path, "author":author, "tileset":tileset }

pervert.

Sex is technically a stat, so saying a deity favors Charisma is ok, but saying a deity favors sex is misleading.

perhaps changing it to say favors men or women.

both generators use similar methods; I think this can be refactored.

Taken from
CityGenerator/CityGenerator#18

What do we want in a house?

Who is the head of household?
what is their race and profession?
What are their personality quirks and alignment?
if a business owner, is the business attached to the home?
how many children?
is their spouse alive? do any other family members live there?
how big is the house?
what is the quality of the house?
What rooms are there?
what possessions do they own?

Also note this will contain the physical description of the house- construction, number of rooms, layout, basements, etc.

As a DM, it's common for players to break into a house or otherwise need something similar. By having this information available via a separate generator, it adds flavor to the city. This would be most useful if it included generic/generated maps of some sort.

My goal is to eventually get back to the multi-flag view that citygenerator had:

http://citygenerator.morgajel.net/multiflaggenerator

Unlike most generators, this one had a large JS section that can more or less be ported directly over. It's the json connection that is the problem.

The only problem is the json data being passed to JS was based on a perl data structure that isn't easily replicable in Python. This gives us three options:

1. Bend over backwards to implement the perl data structure with no changes to the JS.
2. Rewrite the JS to fit with the current python data being returned.
3. Meet somewhere in the middle

I had begun the work in the flag branch (
https://github.com/CityGenerator/Megacosm-Generator/tree/feature/flags ) but quickly grew tired as I realized how messy the code was and how much I worked around what perl was sending me.

In addition, the data structure on the backend greatly changed between CityGenerator and Megacosm Generator with the xml-> data file conversion. I no longer have the simplicity of nested data structures to represent different patterns.

This whole thing should potentially be gutted and recreated :)

Can I simply detect class_* that is a zset? do I even need to create a star_foo entry like these?

data/planet.data:LPUSH stat_planet size
data/planet.data:LPUSH stat_planet temp
data/planet.data:LPUSH stat_planet atmosphere
data/planet.data:LPUSH stat_planet wind
data/planet.data:LPUSH stat_planet day

What should go into a region generator? size? city count? what else?

these use the old builders and arg filter style- rewrite it to be less kludgy

Megacosm-Generator\data\resources\locale.data line 3 "know" should be "known"
Megacosm-Generator\data\resources.data line 40 "know" should be "known"

The Region template only has a single sentence. That needs to be fleshed out.

mass and distance should impact orbital speed.

what else could be added to a starsystem?

phobias would be a useful generator by itself

many generators have content that is not documented in the template. Do this, and create tickets for each template that needs work.

I need real tests for magic items.

region or species associated with it would be a neat feature.

rather than using

return render_template('wanted.html', wanted=wanted )

do something more generic, like

return render_template('wanted.html', tempobject=wanted )

This will give me flexibility on includes- for example,

<ul>
{%for field in  tempobject.__dict__ %}
    <li>{{field}}  {{tempobject[field]}}</li>
{%endfor%}
</ul>

a gang generator would be great as an addon for wanted posters or encounters, or as a standaline

I have a lot of open tickets and new generator ideas that need to be document.

right now it's a rand(1,10). we can do better.

how rare are magic items?

MagicItemGenerator has it's own use of the filter/environment/template stuff; that needs to be merged down to Generator and cleaned out of the other classes.

There are so many menu items in misc. that we need to break it up; the next logical break is for oneliner generations.