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.

Sign up for GitHub

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

Jump to bottom

Monsters - Local Database #18

Open
WTIGER001 opened this issue Oct 19, 2018 · 2 comments
Open

Monsters - Local Database #18

WTIGER001 opened this issue Oct 19, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@WTIGER001
Copy link
Owner

Instead of using firebase for the basic monsters, since they should not change often, use a local file that gets released and downloaded from the storage. Maybe a bundle per type. Figure out how to edit them too... Maybe keep the pictures separate. This could be the start of an asset authoring system. Each package would be a zip file with the JSON stored. There would be a bundle registry that would list all of the bundles and their latest version. The version would be compared on startup and then the newer bundle would be downloaded if necessary.
@WTIGER001
Copy link
Owner Author

This could be used for all reference data.

@WTIGER001
Copy link
Owner Author

The reason for this approach is to conserve the firebase database for user data and to reduce the usage.

@WTIGER001 WTIGER001 added the enhancement New feature or request label Oct 19, 2018
@WTIGER001 WTIGER001 modified the milestone: Encounters Nov 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@WTIGER001