I know you aren't going to like this answer, but don't worry about it.
What you want to do is do it the wrong way for now, then learn from your mistake on the next pass. We can tell you a better way to implement what you want, like frob just did, but until you understand why one way is better than the other, there isn't much value.
In other words, you need to learn from your own mistakes.
Very nicely said Serapth and I have to agree 100%. Programming is the art of understanding core features and functionality of a language and finding the best way to implement them into solving the issue at hand. It is good to ask for and take advice on how you can better something but you should always try a few different approaches yourself before doing such. We may be jumping to conclusions and you might have already experimented with a few different ways, if so and this is the best you have found so far, well most of us don't agree and Frob's idea of centralizing objects for re-usability is a good start. Now it's up to you to take his suggestion and apply it to your game and find if it works better for you (and WHY). The most important part is WHY. Make sure when asking for help that you question the WHY every single time. Not to challenge the suggester of the possibly better technique but to truly understand yourself WHY their method may or may not be better. So like Serapth said you need to actually be learning why things make a difference not just being handed the proper answers.