i wanna improve my game organisation and i’ve seen these words many times but i never understood their purpose. could anyone tell me what they do and where i would need to use them?
They all basically mean the same thing. It’s just a name, you shouldn’t worry too much about it.
Some developer might name something handler while another names it manager. It all resolves to “a wrapper for x”.
Don’t worry about it. Naming is the least of your concerns in programming.
2 Likes
Got it! Could you please tell me more what they do and in what cases I should use them?
They don’t do anything. It depends on the developer’s naming convention. For example, if you have a datastore wrapper that simplifies data stores. You could call it datastoremanager, but datastorehandler or just datastorewrapper also work.
You pick when you want to use them, they mean the same thing. You can use them when you have a wrapper for something. If you have a new OOP class, it is best to name it the name of the class though. You can use them interchangeably.
Use them how you 
want them to be used. It’s like naming variables, you just pick one without thinking.
1 Like
Alright, thanks for the explanation! The wrapper modules really look like a useful thing, I feel really dumb for not using them before…
1 Like
If he solved your problem, mark it as a soloution.
Oh my bad. I forgot about that lol