Questions i can't figure answers due to the map/entities design yet:

What happens later when for an example NPC would have to attack player?

How from the NPC class the logic knows where is the player located or if he (NPC) can move right ? - having no idea about the map. Should i pass the MAP pointer to the AI logic ?

Which is the proper way to go to separate the logic and make all of the above simple ?

Questions This sounds simple but that initial design has an effect on later development. Examples:

What happens later when for an example NPC would have to attack player?

How from the NPC class the logic knows where is the player located or if he (NPC) can move right ? - having no idea about the map.

Should i pass the MAP pointer to the AI logic ?

Which is the proper way to go to separate the logic and make all of the above simple in future stages of development ?

Which is the proper way to go to separate the logic and make work simpler?

Questions i can't figure answers due to the map/entities design yet:

What happens later when for an example NPC would have to attack player?

How from the NPC class the logic knows where is the player located or if he (NPC) can move right ? - having no idea about the map. Should i pass the MAP pointer to the AI logic ?

Which is the proper way to go to separate the logic and make all of the above simple ?

The same question applies for rendering, When rendering. With the initial design i would have to

1. Render the map first
2. Render entities next

instead of

1. Render the map + entities in one (for... loop)

What's your opinion / suggestion - any pitfalls you see that can show up later?

Which is the proper way to go to separate the logic and make work simpler?