Trouble organizing into scenes

[oaklandgit]

Hi all,

I'm stuck on a bug with my code and I'm not sure if it's my coding error or something with Kaboom. But maybe there's something I'm not understanding about scope within scenes.

In version A I am not enclosing anything in a scene scope and everything works (see the script.js file)
https://replit.com/@LarryStone/A-no-scenes?v=1

In version B, I am enclosing my functions in a scene scope and then calling the go function, and I get a mysterious "script error"
https://replit.com/@LarryStone/B-scenes?v=1

Thank you in advance for any nudges in the right direction!

[oaklandgit]

OK I figured out my issue, but it raises a question about how Kaboom should behave…

The problem was that loading resources (spritesheets for example) from within the scene scope leaves Kaboom unable to find those resources. But I expected those resources to be available at least from within the scene scope.

[slmjkdbtl]

Yeah the loader doesn't work mid-game now. But I think this should work:

Promise.all([
     loadSprite("sprite1", ...),
     loadSprite("sprite2", ...),
]).then(() => {
    add([
         sprite("sprite2"),
    ]);
})

[slmjkdbtl]

I wonder why do you have to load assets in scene scope, instead of global? Do you have a lot of assets and have memory / load time concern?

[oaklandgit]

No, it's not a memory concern. It's about organizing the code -- I'd like to keep the resource loaders with the game objects they are for.

But I'm ok loading then in the global scope.

[slmjkdbtl]

I am planning to support in-game loading assets tho

[oaklandgit]

Awesome!