crawltracker
commented
2 years ago Note - Lxran#2292
I made a mockup image (with inspect element <:kekw:930834155971940362> so it lacks some tags): https://files.catbox.moe/lor78s.png
Open crawltracker opened 2 years ago
crawltracker
commented
2 years ago Note - Lxran#2292
I made a mockup image (with inspect element <:kekw:930834155971940362> so it lacks some tags): https://files.catbox.moe/lor78s.png
Feature Request: Add Encounters page and homebrew support.
Extra Information There are many different types of encounters in the books and homebrew files, but there aren't an easy way of browsing through them other than going into the book itself or importing them to VTTs (or the DM screen). This feature request tries to come up with a page and data structure for supporting this. Who would use it?: Everyone really, but mainly DM Screen and Foundry/Plutonium enjoyers How would it work?: Add a new
"encounter"top-level array of objects for creating and editing objects."name"would be the name of the encounter,"source"and"page"are standard,"type"would be an object for filtering with such options as"battle", "social". The"level"object would contain the"start"and"end"objects, and the whole object would be for displaying the suggested level range for the encounter."environment"would also be for filters, and it would take string entries and populate a filter list."creatures"array of objects would contain all the creatures involved in the encounter, with a simple"type", "name", "source", "count"list of objects if the type is"creature". If it is"player"(for people that really want to bring their characters into their brews) it would be"type", "name", "hp". The contents of the"creatures"would also fill aCreatures Involvedfield in the rendered output. The"areas"array of objects would include either"bookId"or"adventureId"and"areaId"to indicate which areas within the book or adventure this encounter is from, and would populate a list of filters (Why would a homebrew source reference an existing book? I have no idea, but I'm sure someone would ask for it). A"skillsInvolved"object would hold all the skills that is used in the encounter as booleans. This could also be changed to an array of object, and each object would be"skill": "string", "dc": integerif we want to also populate filters depending on DCs. A"spellsRequired"array of objects with"name": "spellName", "source": "spellSource"could be added for encounters that cannot be resolved without a specific spell being cast. This would also populate a"Spells Needed"field in the rendered output. An"entries"array would hold the descriptions, text, the general stuff. A"fluff"field is for adding images and other fluff. I guess at that point it also needs"hasFluff"and"hasFluffImages"as well. It could also have some filters, such as"Requires Spells Cast","Reduces Hit Points","Big Consequences","Small Consequences","Results in Important NPC Death","Special Event","One-time Event","Regular Encounter""Random Encounter", etc.This whole thing would be a one click import to Foundry through Plutonium. The unique monsters would import as actors, the spells need not be imported, and the contents of the
"entries"and"fluff"import into a journal entry. The encounter's combatant data can be imported to (or rather, selected in) the DM Screen's Initiative Tracker. Why should this be added?: I think the ability to browse just the encounters only would be a great boon for fostering creativity and ease of navigation around the books/adventures. I know this is a very convoluted feature request and I don't expect it to happen anytime soon (as there is a mountain of books to go through and convert the encounters from) but if it were, it might be worthy of a major version bump I feel like (probably not though, I'm not a programmer).Votes: +46 / -0 / ±4