Lack of information about using dynamic prototype setting for collection factory

[Ilyas]

I’m trying to generate level consisted of different rooms. Rooms are just collection of different object and enemies in it. I tried to use collection factory to generate new rooms on the fly. But when I want to change prototype of collection factory from script using collectionfactory.set_prototype() function, I receive this error “Failed to load collection factory prototype /game/levels/room_001.collectionc”. Tried to follow example listed in Collection factory manual, but looks like it not working. On other hand changing prototype for OBJECT FACRORY work fine. What I want it’s create pool with different rooms named like room_001, room_002 etc. and pick random one and spawn.
My project structure

Collection factory properties

Outline of main collection

Error

Factory script

[schlista]

I do something similar but I use multiple collection factories. Randomize which one gets called.

[britzl]

The documentation for collectionfactory.set_prototype(url, prototype) expects prototype to be a project path. In your case it looks like it should be /game/levels/level_2.collection.

[Ilyas]

I tried that too and its not helped, because for some reason when building the project all other collection not build into collectionc, only one collection defined in collection factory does.

[AGulev]

Please, take a look at this old post about the Dynamic Prototype feature to make sure you use it in the way it was initially designed:

Defold 1.4.3 BETA

I wouldn’t recommend such usage of the feature. Our build system counts components in a world (the collection spawned using collection proxy). If some component’s count is static - then this collection will allocate this exact amount of memory, if some components are dynamic, then count will be taken from game.project. So, fo example: Collection (world spawned with collection proxy) -go --sprite --factory with `Dynamic Prototype` unchecked ----go ------label will allocate 1 sprite and labe…

Our build system builds only linked resources. If you never link the resource anywhere, it will not be built. A ‘linked resource’ in this case means being specified in a factory or in some other place specific to that resource. It’s not enough to be in the project folder.

If you want to have a few levels in your game, just create a few collection proxies (or collection factories).