innocentuslime / bevy-tilemap-editor-pls Goto Github PK

Currently, this editor can only handle tilemaps who have their tileset coming from a single file (TilemapTexture::Single). To make the editor more user-friendly, all other types of atlases should be supported.

Currently the plugin relies on the platform provided by bevy_editor_pls. However, it seems that making the plugin work on its own is:

• Not that hard to implement (assuming egui is still an required dependency)
• Makes the editor more usable (not all bevy developers are using bevy_editor_pls)

Tasks:

• Try to isolate the code from getting the &mut World reference
• While we are abstracting away from the from bevy_editor_pls, the whois tool can offer some tighter integration with it (clicking on the tile can force the inspector into viewing the tile entity)
• Consider placing bevy_inspector_egui behind the optional feature gate too
• Redesign the API to make it easy-to-use without bevy_editor_pls (probably just make State into a trait)
• Create the API that allows adding the plugin without bevy_editor_pls
• Integration with egui_dock
• Make some of the State API public

A little quality-of-life improvement -- freeing the user from having to locate the tilemap entity to make it invisible. This can be done by simply giving them an access to tile's Visibility component in the editor window.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update Rust crate bevy to 0.13
• Update Rust crate bevy-inspector-egui to 0.24.0
• Update Rust crate bevy_ecs_tilemap to 0.12.0
• Update Rust crate bevy_editor_pls to 0.8
• Update Rust crate bevy_egui to 0.27
• Update actions/checkout action to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Right now all extra components/bundles that should be inserted together with the TileBundle are stored in a special registry, that can't be modified through the editor.

Making this data editable will greatly boost the usability, freeing the user from having to edit the components manually after spawning a tile.

P.S.
It seems that to implement all that, the editor needs some reworking to work bevy's reflect module.

• Editing the bundle
• Reading it via the picker tool
• Refine the code and API
• Update examples and README

The editor needs the information about the tilemap. The way it access the components is all over the place. Unique to every place and hard to work with.

A better way to do that would be to make some sort of master query for accessing all the relevant components (the whole bundle of the tilemap pretty much).