-
Notifications
You must be signed in to change notification settings - Fork 9
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
User metrics with optional platform specific db persistence #66
User metrics with optional platform specific db persistence #66
Conversation
…rs incremented during the game
…e the layout later
…All mutations handled by 1 bevy plugin and reset on each new game
…ame_metrics to disk rather than doing a sqlite op whenever a mob is killed. This allows us to bulk increment the mob kill count sqlite table, which is fewer sqlite ops
…r of our plugin that handles separate resources. The game over screen now pulls from those newer structs with the current game stats
…t certain plugins into separate crates. This aids in conditional compilation and platform-specific functionality. Wasm is a bear
… hoist the db to another crate
…when the feature is not available. Hoist the db model/func return type to an interface to be used by the game over ui.
…ional compilation and doing more platform-specific behavior
…ches: (mobs killed, userStats) x (currentGame, completedGame)
…more 1-at-a-time increments.
…ng whenever we start a new game so that we can keep metric counters across games even without a database
…re actaully updating that now
counter metrics plugin
… things as resources
…eOver rather than OnUpdate
…e used by the plugin test
…me we write to the db for a given user and not log an error
… the game over screen
0279781
to
738dcc3
Compare
version = "0.1.0" | ||
edition = "2021" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use consistent package version for all crates in the workspace.
bevy_ecs_macros = "0.11.0" | ||
bevy_ecs = "0.11.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use consistent bevy versions across all deps. Ideally we only update 1 place when they release a new version.
thiserror = {workspace = true} | ||
derive_more = {workspace = true} | ||
rusqlite = { version = "0.29.0", features = ["bundled"] } | ||
dirs = "5.0.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think directories
is slightly higher leveled. Use that instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good one 🤣
Like #58 but with a massaged commit history.
thetawave_interface
crate to be used as something like a "service registry" with schemas+typedefs.