| Website | https://dekirisu.com/ |
| GitHub | https://github.com/dekirisu |
| Discord Server | https://discord.gg/G2RmYPmM6b |
@natuchips Surely possible if you don't mind reading docs or code in the bevy repo.
That said, using one of the 'big 3' engines will prolly be 'faster to release' and more tutorials are available. 
🪿 using my new grid base
🦜 a few shading changes
🐇 own embedded DB system (kinda)
🐇 ..linked with my own asset loader (for the world only)
🥷 a bunch of other changes™
🦜 still reworking tile/grid base
🦫 ..(experimental) custom texture mapping
🪿 ..this is ONE material
🐿️ reworking my own grid/tile system
🐇 improved tile merging
@laund I mean I'll still use mevy 
Other than that I'll just see during 0.19 what makes sense, I'm a bit out of the loop atm.
Do you have thoughts about it, since you asked? 
Migration to #bevyengine 0.18 done! 🐿️
🐬 ..luckily less work than expected
More Migrations...
✨ Updated my #rustlang macros for #bevyengine
🐿️ Added feature "0.18" for mevy_ui & mevy
🐬 ..which handles the changes to BorderRadius & LineHeight
Late to the party, but slowly migrating to #bevyengine 0.18 🦆
Already migrated my bevy_gltf fork!
I still like a #rustlang trait to configure those. 😶🌫️
https://github.com/dekirisu/bevy_gltf_trait
