Hello Gamedev Forums!

I am a Computer Science student who is currently learning C#. I would like to sharpen up (see what I did there?) on the language by writing an application that could be helpful to the community (and free of charge too!). If there is enough demand, I could possibly develop a Java version which could be used on Macs as well. My idea came from a conversation with a friend about Lore. I would love to write a Lore Helper tool, which would keep Lore neat and organized.

The idea so far, is to have Tree-like structures that would keep the Lore organized. For example creating a Parent that could be called "Humans". In there you could write all the lore about Humans in general and their history etc. Under "Humans" you could have a child called "Factions". In there you describe the human factions. You could also have another child called "Relations", and describe how Humans cooperate with other species etc. Each child could also become a parent for several smaller children.There would of course be Text Editing so that the text could be formatted and prettified. Perhaps even insertion of pictures along the way.

All data would be saved for an .LH extension but the data could be exported as PDF and/or DOCX files as well when you are done. My question to the community is:

Would you like a tool like this?

And if yes, what other functionality would you like to see?

Thanks for Reading!

Oh, so very much like a character flowchart?

That definetly seems like something that would be useful to organize large overarching stories that have their own lore and various complex characters. I'd imagine potential RPG makers would appreciate it.

Some two cents that may be good to add would be perhaps to add would be perhaps:

- "Organizations" : For example guilds, clubs, etc. I'd imagine it'd be programmed similar to a visual "list" or "group" to put objects (or "humans") in even when they don't have a direct relationship with one another other then by associations like these.

- "Items" : Comparable to a "human" object, except it would be associated with a "human". Useful especially for example with special objects that perhaps change hands constantly.

Oh, so very much like a character flowchart?

That definetly seems like something that would be useful to organize large overarching stories that have their own lore and various complex characters. I'd imagine potential RPG makers would appreciate it.

Some two cents that may be good to add would be perhaps to add would be perhaps:

- "Organizations" : For example guilds, clubs, etc. I'd imagine it'd be programmed similar to a visual "list" or "group" to put objects (or "humans") in even when they don't have a direct relationship with one another other then by associations like these.

- "Items" : Comparable to a "human" object, except it would be associated with a "human". Useful especially for example with special objects that perhaps change hands constantly.

Ah but the user of the program would specify this themselves you see! They get a clean slate, and then they can just add and name the parents/childs they want.

However your post gave me an idea to add some common Templates perhaps.

I think it's a great idea. It essentially sounds like you are making a flow chart/tree that can handle large amounts of text with a label for each section.

I think it's a great idea. It essentially sounds like you are making a flow chart/tree that can handle large amounts of text with a label for each section.

Something along those lines yes :)

To be honest, I can't see why I'd want a tree-like structure for this. Trees have been generally found to be lacking when it comes to organisation because it's rare that everything can fit into a strict hierarchy. I would probably prefer either a normal word processor document (which is easier to edit and move things in) or a wiki (which has the benefit of arbitrary cross-referencing).

To be honest, I can't see why I'd want a tree-like structure for this. Trees have been generally found to be lacking when it comes to organisation because it's rare that everything can fit into a strict hierarchy. I would probably prefer either a normal word processor document (which is easier to edit and move things in) or a wiki (which has the benefit of arbitrary cross-referencing).

If you don't want to share the things you write before it's ready, making a Wiki is not an option.

Abitrary Cross Referencing could be nice to add though, if I can.

I'll try and see if I can make a tree structure that works. But thanks for the input!

If you don't want to share the things you write before it's ready, making a Wiki is not an option.

False. You can host your own on your own computer and edit it that way, or on a server only those who need to work on the project have access to.

However, having multiple trees would work for the items that don't fit in the regular structure.

If you don't want to share the things you write before it's ready, making a Wiki is not an option.

False. You can host your own on your own computer and edit it that way, or on a server only those who need to work on the project have access to.

However, having multiple trees would work for the items that don't fit in the regular structure.

Well true I guess, but I wouldn't think that it's what the normal user would do.

Multiple Tree Structures would be part of this, yes.

Game developers are not 'normal users'. :)

If I'm working as part of a team, we'll have internal systems for collaboration, usually including a wiki.

If I'm working alone... then maybe I'd find a use for a standalone tool like this, although most likely I'd just use OpenOffice Writer. But if the tool was comprehensive enough in terms of search, cross-referencing, indexing, etc., it could be useful. I still wouldn't want an explicit tree structure though.

One thing to bear in mind is that game development documents are communication tools. Is this tool for communicating with the writer, ie. as a memory aid? Or is it to communicate with others, ie. to provide documents to work from? If the latter, what benefits does it offer, given that it will just export to a file similar to that created in a mainstream app?