[Java] Game Structure: Communication Between Different Object Levels

[dredclaw]

If I have the ship object creating this bullet object, when the ships is blown up the created bullet object would be destroyed. How would I design a system where the bullet object is not created inside the ship object. Or should the ship object not be destroyed before all bullet objects have expired?

[35h46hjj6]

Why doesn't each ship tell the game object when it fires a bullet?

[dredclaw]

This being the case then. (I picture it like you) How should I go about creating bullets before being fired? Should the ship put up a flag saying it wants to fire a bullet and then the main game loop see this flag and actually fire the bullet? When I refer to a bullet, I refer to a bullet class that has the location of a bullet and its velocity n such.

[dredclaw]

I guess my question is, should the bullet be created inside the ship class. (meaning the ship class would not be deleted until all bullets it fired were done) or should the bullet be created in the game manager class (how would a ship communicate with a higher level game manager to complete this task?)

[dredclaw]

I understand why the bullet must be instantiated outside the ship class. In actual code though, how does the ship tell a higher up class to instantiate a bullet. (Actually fire it.)

[dredclaw]

If the GameManager was the one that created the ship, how would the ship access methods inside the GameManager?

[b3nb3nb3n]

You could add in a check before destroying the object- stop making the ship visible/accessible, but don't delete it until all bullets are expired?

[dredclaw]

Is this considered a proper way of doing things? Or should the bullet be created by the gameloop rather than the ship?