Closed WalterLPearson closed 3 years ago
This needs to be rebased off of the development branch before merging can be considered.
Also, don't bump version numbers while making PRs. Version numbers will get bumped during Release Candidate branch drafting.
Agreed, I will not touch version numbers in the future.
Here is what I believe I need to do for a pull:
I will issue separate Pull requests for merge.py and annotate.py These are the only two files I really need to change. In the future my branches will have more focused small changes, and I will issue Pull requests more frequently. This started out just as tinkering, so I did not follow my typical professional practices. I apologize.
Thank you for your time, attention, and advice!
That's a good summary of changes. No need to apologize, I can certainly appreciate tinkering, especially with intent to improve. 😛 Closing this PR.
Like it says. Small changes to merging, large changes to annotation. Much more data is searched to give information to modders. Also laid the groundwork to track relationships (ie. foreign keys) between different sections and files, to create reports I've been dreaming up.
Eventually I want to export HTML for the wiki, spreadsheets, diagrams, and maybe even a MySQL database that modders could run queries.