Is your feature request related to a problem? Please describe.
With #876 there will be a cross references feature, but at the moment, there are pretty much only cross references for a small subset of cases.
Describe the solution you'd like
Ideally the other documents can have internal references as well as references to the SRD. I think there will be a choice to be had for a given document, e.g. does a reference to "Frightened" point to srd-2014 to srd-2024?
A few other important items: There are a LOT of very simple objects which are names like "book" and "combat" that are extremely permissively matched. I think some basic logic would help here:
- Don't match on "rules" period.
- Don't match on mundane objects.
- But do match on weapons and armor, and probably shield.
- Don't match on weapon properties.
Those could likely be added into the existing logic and make solid improvements quickly.
Describe alternatives you've considered
There will be some editorial work and some troubleshooting work associated with running the existing crossreference django commands. I think there's a couple of code changes in allowing cross-document crossreferences, and there will likely be some false positives that should be blacklisted.
Is your feature request related to a problem? Please describe.
With #876 there will be a cross references feature, but at the moment, there are pretty much only cross references for a small subset of cases.
Describe the solution you'd like
Ideally the other documents can have internal references as well as references to the SRD. I think there will be a choice to be had for a given document, e.g. does a reference to "Frightened" point to srd-2014 to srd-2024?
A few other important items: There are a LOT of very simple objects which are names like "book" and "combat" that are extremely permissively matched. I think some basic logic would help here:
Those could likely be added into the existing logic and make solid improvements quickly.
Describe alternatives you've considered
There will be some editorial work and some troubleshooting work associated with running the existing crossreference django commands. I think there's a couple of code changes in allowing cross-document crossreferences, and there will likely be some false positives that should be blacklisted.