Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move runtime assets to a separate repo #3

Open
TheManii opened this issue May 15, 2018 · 1 comment
Open

Move runtime assets to a separate repo #3

TheManii opened this issue May 15, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@TheManii
Copy link
Owner

the following folders/files are runtime dependencies, not build dependencies:

  1. tablenames/*.*
  2. monsters.lst
  3. hashlist.db

Additionally:

  • File explorer itself has an existing update notification system
  • hashlist.db has an existing update mechanism
  • both should be moved over to a custom update location, independent of the original (the more we drift away from the source repo, the more this matters)
  • Finally, 1. and 2. in the above list would benefit from being included in the update system

the following are better off in a dedicated docs repo:

  • research
@TheManii TheManii added the enhancement New feature or request label May 15, 2018
@TheManii
Copy link
Owner Author

TheManii commented May 22, 2018

The process of moving into a separate repo has begun, all the above are in the resources folder, and in the future this folder will be in the (tentative) FFXIV-Explorer-Data repo.

As these are simply runtime resources, it is entirely up to whoever is compiling to decide if/how they will include them, if they do not choose to build it in the way as outlined. File explorer already has the ability to gracefully fail and continue if they are not present.

A long term goal is to make adding data sources into it more manageable, as there are many sources of sources for file paths, such as root.exl -> music tables -> music file names that are what the game client directly uses (the above example is already handled by file explorer's tools -> find music hashes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant