Question: Is it possible to code it so we can combine tables?

[revloc02]

yml syntax would look something like: <table some_existing_complete_table&my_tweaks_to_it>

This would allow utilizing already complete tables (maybe they are official core D&D tables that we don't want to change) and then adding a few more items to them, or maybe I want to skew the percentages somehow, or maybe I just simply want one result that came from two or more tables.

Utilizing some sort of combine syntax would help prevent duplication of table data in order to make adjustments to it.

Currently this is just a thought, not a high priority.

[revloc02]

Okay sooo...., sometimes my Happy Meal is short a few french fries, this can already be done.

See what is currently named weapons.yml for an example. The probabilities are a little weird, but even that can be worked around with the current functionality (see weapon_equal_probability_single). It is not elegant, but doable.

I am not sure if I am ready to close the issue until we've discussed further.

[danlangford]

so what you did there was make a pseudo table of sorts that referenced the existing table and another table with your tweaks to it. that isnt a bad workaround.

back to the original question: if both tables were oneOf tables then it would be easy to just make the list bigger. if the tables were not oneOf tables then we could assume the existing table is already complete. so it begs the question: what would your tweaks look like? would the dice roll range need to match exactly? what if it didnt match exaclty?

i think we dicussed one time an interface to assist in creating your own tables. if that interface let you build your own table by first copying a built in table maybe thats all the customization options needed? they could tweak to their hearts content and the entire table would be their own.

we can continue to discuss

[revloc02]

Yeah, great question. I was steeped in oneOf tables when I was thinking of this. It wouldn't really work with results tables.

But this idea still has merit for oneOf tables I think. It is nice having separate tables for each type of weapon (Simple Ranged or Simple Melee, etc.) in case you need a random one of those. But it would also be nice to have a random weapon of any type with an equal chance of getting any single weapon. If the ampersand become an operator to combine oneOf tables one could easily piece the four weapon tables together, and then add another oneOf weapons table or two of their own.

Maybe the syntax looks like:
<table core/simple_melee_weapon & core/simple_ranged_weapon & core/martial_melee_weapon & core/martial_ranged_weapon & revloc02/sundry_custom_weapon>