Conversation
|
Thank you! so much for the PR. I'll review within the next few days. |
|
Hiya @Nub \o/ - I started reviewing and I have a few quick questions:
|
|
Another thing I noticed is that in the PR, OmagariProject is used to |
|
Regarding exported projects, looks like the PR also removed the export functionality altogether - was that intentional? |
|
Hi I was working with the author on this PR. the exported parenting is not currently supported. the reason that I hope that answers some questions, I am interested in working with you to support this crate if you are interested! |
Starting with the most important thing :) Absolutely interested \o/
This is my fault - I omitted the part hexroll is using to load the exported asset file. I now pushed a branch with this code organized into let blood_effect: Handle<EffectComplex> = asset_server.load("blood.hanabi.ron");
let magic_effect: Handle<EffectComplex> = asset_server.load("magicburst.hanabi.ron");
let explode_effect: Handle<EffectComplex> = asset_server.load("explode.hanabi.ron");
let defense_effect: Handle<EffectComplex> = asset_server.load("defense.hanabi.ron");
let vapor_effect: Handle<EffectComplex> = asset_server.load("vapor.hanabi.ron");Which in turn can be spawned by accessing vec This also supports hierarchical effects. Keeping in mind this code is not perfect, what do you think about this strategy? (Edit: the reason I use |
Began a light refactor to move omagari to use more rust-ful patterns.