I’ve seen various video tutorials with their own project structure and was just wondering if there is a recommended (preferred) way of setting up such games.
All my projects have this structure, but it’s up to a developer to set up structure the way they like it better
8 Likes
Where are .script files there? In their own collection folder?
Oh, those are gui_script. I meant .script files. Next to their .go files?
Usually, it’s the same as for popups—each scene has its own entry point (a script file) and then only Lua files:
In some rare cases, it makes sense to have isolated logic in a script, in which case it goes into the modules folder. For example, this script for particles “play once”:
I think you have something similar to what I’be been pondering these past days (asking here Data management in games with lots of items/enemies/objects - #9 by playmedusa)
So what about your gameobjects? I understand anything you are showing on screen is a go, but you can have some kind of ‘generic go factory’ and then configure each instance with its atlas and sprite?
I’m trying to figure out if I can move as much code to basic Lua modules as possible, but then there are unavoidable parts like input, particles, sound, sprites, gui and so on that are on Defold’s side.
No, I don’t use generic GOs except in very basic situations.
I still want my game designer to be able to configure whatever they want.
But… How do you draw sprites without a GO with a sprite component?
If I could draw like I do in Pico8 or Löve I would be happy 
Edit: oh wait. You mean you don’t use generic GOs, but I guess you do use specific GOs
Exactly. Most of the time, I use specific GOs, and only in very rare cases do I use a generic one—when it’s enough to just change the sprite.
1 Like