Hello all,

I want to create a new bullet when I press 'space'. The easiest way to do it is to put all the logic in the Player class.

On the other hand, I must follow OOP concepts, which means that all entity creation should be handled in one place only and not scattered in different classes because later I may create something in my NPC class and then somewhere else and I will have object creation all over the place.

Now if I want to do everything in the World class, I need to pass a lot of different parameters like playerPos, playerDir, isProjectileLaunched, etc. to the World class, which doesn't look good.

How is this normally done? I want to have object creation in one place and also make the code pretty.

Thanks for reading. Any suggestions are appreciated.

World could have a reference to player (since the player is in (or on?) the world, right?) then you can just grab the needed values player->getPos() etc.

If you have some external class handling your game objects, that one should be what creates the projectile.

Player input shouldn't be handled inside the player class. The input should drive the player from the outside, something like if(is_key_pressed) { player->move(dir, speed) }

I want to create a new bullet when I press 'space'. The easiest way to do it is to put all the logic in the Player class.

For bullet creation, that could be the case, but is bullet movement then also in the Player class?

In general, you follow the principle of responsibility. Something in your program is responsible for handling these small, fast flying objects from birth to death and everything in-between, and it makes sense to move everything related to those objects to that spot. Player doesn't sound like a logical spot, nor does world (world is more like 'glue' to keep everything together to me), but ymmv.

On the other hand, I must follow OOP concepts

This sounds restricting. You basically assume that everything can be properly modeled in OOP, which is not true. If something can be nicely modeled in OOP, then by all means, do that, but if not, imho don't be afraid to deviate to a better solution than OOP would give you.

As for getting access to the object that manages the bullets, you can either give a reference to it during construction of the player (it won't change during the game anyway), or you can ask the world for the object, and then interact with it in your player class.

Why would a bullet care about a 'Player'. The bullet just needs an origin and a direction of flight of flight. The system itself shouldn't care about where those come from. So say you put, the bullet handling code in your player, then further along you decided that now you want to handle bullet impact, audio, effects etc. are those going to be stuffed into the player class too. Although OO principles is not the be cure for everything, there is no substitute for good 'functional decomposition'. Your system should be broken down into functional blocks of a small enough granularity to simplify implementation, and allow it decoupling with the other system(s) it interacts with. I don't know the extent of your project or the other pieces involved, but I suggest you think about how the bullet will interact will all these components and from there you will see where to best locate it.