Factory in an instancied object

Questions
1

'lo.

Let’s say I have objects, starships for example, created by a (collection)factory.
I want those starships able to shoot bullets, bullets being objects.

Can I put a factory “create instances of bullet.go” in the script “starship.go”, while 'starship.go" is already an instance created by another factory “create instances of starship.go”.

Fact : There will be a LOT of starships simultaneously, and I fear the engine could not live with so much factories. Or is it the SAME factory for all the instancied objects ?

2

You can put a factory in an object created by another factory, BUT since each factory will create the same bullet.go instances it will be a waste of resources to have more than one bullet factory. I would move the bullet factory to some centralized game object.

3

A centralized game object ? I know for centralized input script, but what is a “centralized game object” ?

4

bullet_manager.go has bullet_manager.script and one bullet.factory - it’s the only way bullets are spawned in the game! That’s how I structure this stuff anyway.

1 Like
5

And I put bullet_manager as a child of starship.go (which is instancied, since I need more than one starship) ?

6

I don’t know the intricacies of your project structure, but the whole point of what britzl and I are saying is that you don’t need to do that. Every starship can factory.create(bullet_manager#bullet) and use the resulting bullets as it wishes. The factory doesn’t need to be on the same game object.

1 Like
7

It’s a more “top level” object.

E:g. it may live throughout your entire level, and never be destroyed until your level unloads.

For instance, you apparently have something that spawns starships, that seems more “central” than your current bullet factory.

8

Wait, you mean I don’t need to include the factory in the object where I want to create instances as childs ? That’s completely different that the tutorials says.

Here with another example :

Basically, Galaxy create a map of the galaxy, and need for that Stars, which are created by the collection factory StarSystem.collectionfactory.

Each star have planets (and planets can have moons).

main.collection   = That s the game scene
*  camera.go
*  curseur.go
*  galaxy.go

galaxy.go = play the galaxy (the map).
* galaxy.script
* StarSystem.collectionfactory   = Create the stars. Called in galaxy.script in Init

StarSystem.collection = called by StarSystem.collectionfactory (of course)
* StarSystem.go = Play each star (when created, then when triggered), contain components and a label object (this one put directly in the "outline" tab).

Now, each star has planets

I want to know if, in StarSystem.collection, I have to put a “planet.collectionfactory” that would call :
planet.collection = play the planet (if triggered)

  • planet.go (with components like script and sprites, of course).

Basically, each star is an object, each planet is an object.

You can see the project on github, here, If i’m not clear enough : https://github.com/Vampiloup/syzygie

9

Exactly. If your want to spawn bullets you spawn them from one factory on some top level/central game object. Not one bullet factory per ship.

Which tutorial are you referring to?

10

The videos about factories all put the factory where the instancied object would be if it was alone (non instancied), or here : https://defold.com/manuals/factory/.

There is nowhere a word you can put a factory anywhere “up” and call it freely (but it’s great).

Last question : When you say “top level” object, it means some parent, even if it’s not in the same collection ?
Like :

Main.collection

  • bullet.factory
  • game.collection
    ** game.go
    *** starship.collection
    ****starship.go
    *****starship.script

=> If the call for “bullet.factory” is in “starship.scrip”, the bullet will be created as child of starship.go, at the world position of starship.go ?

Sorry if I’m a little slow.

11

Put it in the game.collection.

You can easily change the parent using go.set_parent()

1 Like
12

Thank you, I’m doing to try all that.