Having some issues.
When switching from collection 2 to collection 3 I get the following error:
ERROR:GAMESYS: The collection /Screen-2-Title/Screen2.collectionc could not be loaded since it was already. Message ‘load’ sent from level:/loader#loader to level:/loader#proxy_level_2.
The error tells you that you are trying to load a collection that has already been loaded. You must either unload it before trying to load it again or manually track that it is loaded in which case you can skip loading it again. I would recommend unloading any collection that isn’t needed, at least if it uses many unique resources.
Given that error message I think you should assume that you are actually not trying to load collection 3. Why don’t you put in a print()-statement with the actual proxy you are trying to address before the load? You could also fire up the debugger and inspect your variables.
Used: “print()” and you are correct, it’s trying to load collection 2 when collection 3 should be loaded?
This messaging system confuses me still, so perhaps I am doing something wrong…
I’ll hit it with a hammer later, thanks!
One thing that might help you is looking at message passing. Have you looked at this page? What confuses you, in particular about it? Feel free to post a question about anything that confuses you about it - even better, since it is definitely quite confusing to people who are used to different approaches, chances are that someone has asked the same question before, which you can find by searching the forums!
If you post every error you encounter along the way on the forums without searching for previous questions that ask the same thing, or reading the documentation, or trying the tutorials, despite many, many answers suggesting these very things over and over, are you really learning anything?
We really want to help you enjoy Defold, and I firmly believe that this is best accomplished by solidly understanding the engine from the ground up. By all means, starting with a bigger project and learning by doing is a great way of learning, but that will always necessitate some sort of grounding in documentation and tutorials when things go awry. We’ll continue to answer your questions, precisely because they are questions that you don’t have the answers to, but we will also continue to provide you with the places to find the answers yourself for the future. If you don’t look at these places, then you are shooting yourself in the foot by always placing a ceiling on what you can accomplish with Defold.
Not only that. You end up taking a very laborious path. One example, I took a quick glance at your project and there are several repeated chunks of code that could (and should!) be replaced by one-liners. This link should give you a very clear hint: https://www.defold.com/examples/animation/tween/