Hi,
I would like to know how you organize asset bundles for your web applications.
For example, do you bundle UIs? Do you bundle only asset? Do you bundle levels? Any insight from your experience is appreciated. Thank you.
For my game, a level is described by an XML document which lists out the GameObjects/AssetBundles it uses and where they go. A database keeps the XML level files and the Asset Bundle files organised, along with a bit of other supporting functionality.
Since my game is cross-platform, my bundle export script outputs for all platforms at once, with a platform ID appended to the filename. Where applicable, each client appends their platform ID to their download URLs to get the right bundles.
The above is just for level data, as my game’s levels are expected to change a lot. The parts of my game which will stay consistent (UI, audio, characters, pickups, etc.) are all just built into the client.
thanks for your feedback.
I have just a doubt about the best unity practices to organize the separate levels.
The first thing I wonder is if it is common practice to let the separate levels being able to run independently.
I.E. if I was working on a flash project, very likely I had a “main container” holding most of the game logic which could load separate asset in form of swf files. Probably there would not be the concept of level as separate swf file, but the levels would be described by xml files or such.
In Unity I am not sure how to face the problem. Everything make me think that the levels should run independently, since theoretically I could use LoadLevel to run them.
Even if I use AssetBundles, I am not sure what I should put inside the AssetBundle, just Prefabs? Or it is wiser to load an entire Level that could run on its own?
This is important because I am not sure about how to organize my “framework” code, that is that code which is not bound to a view. Should this code be repeated for each level or I should go for the “main container” design?