• Content Count

  • Joined

  • Last visited

  1. Thanks a ton for the input guys. I'm getting the hang of webpack and have the modularity working for me. I didn't dive into typescript so that I don't have to take on too much new stuff at once and can get rolling on a game.
  2. Ohhhhk. I'm not very familiar with that workflow so I hadn't even thought of it in that way, but that makes a lot more sense to me. Thank you for clearing that up, I think I'll be able to make a lot of progress now.
  3. I've read through just about all of this guide (https://github.com/kittykatattack/learningPixi). I think I have a grasp of how to switch stages/scenes. There's one part that doesn't make sense to me however. If I wanted to create a separate .js file for every class and every scene's code, what's the best practice for loading those files? I've seen examples where the index.html file just includes all of the scripts, but isn't that possibly a slow and/or bad experience? A previous flow I read about was loading the bare minimum (a background, logo, and loading graphic) and then loading all other images and javascript files. Is there a best practice to load these separate javascript files through the Pixi loader so the splash screen comes up instantly and show a loading bar while I pull in all these extra assets?