kristoferssolo/maze-ascension
1
0
Fork 0
mirror of https://github.com/kristoferssolo/maze-ascension.git synced 2025-10-21 19:20:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
f79be932a3
maze-ascension/docs/tooling.md
Kristofers Solo f79be932a3 Initial commit
2024-09-17 20:19:16 +03:00

5.0 KiB
Raw Blame History

Recommended 3rd-party tools

Check out the Bevy Assets page for more great options.

Libraries

A few libraries that the authors of this template have vetted and think you might find useful:

Name Category Description
leafwing-input-manager Input Input -> Action mapping
bevy_mod_picking Input Advanced mouse interaction
bevy-inspector-egui Debugging Live entity inspector
bevy_mod_debugdump Debugging Schedule inspector
avian Physics Physics engine
bevy_rapier Physics Physics engine (not ECS-driven)
bevy_common_assets Asset loading Asset loaders for common file formats
bevy_asset_loader Asset loading Asset management tools
iyes_progress Asset loading Progress tracking
bevy_kira_audio Audio Advanced audio
sickle_ui UI UI widgets
bevy_egui UI / Debugging UI framework (great for debug UI)
tiny_bail Error handling Error handling macros

In particular:

  • leafwing-input-manager and bevy_mod_picking are very likely to be upstreamed into Bevy in the near future.
  • bevy-inspector-egui and bevy_mod_debugdump help fill the gap until Bevy has its own editor.
  • avian or bevy_rapier helps fill the gap until Bevy has its own physics engine. avian is easier to use, while bevy_rapier is more performant.
  • sickle_ui is well-aligned with bevy_ui and helps fill the gap until Bevy has a full collection of UI widgets.

None of these are necessary, but they can save you a lot of time and effort.

VS Code extensions

If you're using VS Code, the following extensions are highly recommended:

Name Description
rust-analyzer Rust support
Even Better TOML TOML support
vscode-ron RON support
Dependi crates.io dependency resolution
EditorConfig for VS Code .editorconfig support

Note

About the included rust-analyzer settings

This template sets rust-analyzer.cargo.targetDir to true in .vscode/settings.json.

This makes rust-analyzer use a different target directory than cargo, which means that you can run commands like cargo run even while rust-analyzer is still indexing. As a trade-off, this will use more disk space.

If that is an issue for you, you can set it to false or remove the setting entirely.

Other templates

There are many other Bevy templates out there. Check out the templates category on Bevy Assets for more options. Even if you don't end up using them, they are a great way to learn how to implement certain features you might be interested in.