It’s weird, I know what I want to implement however im stuck trying to figure out what I need to implement , I have a lot of options but then I get stuck because I have to implement something else that requires something else.
all the way down the rabbit hole.
It sounds like you need to break your problem down into smaller individual pieces.
Instead of trying to solve HUGE_PROBLEM_XYZ, then trying to keep track of all the things you need to do for that, break it down into small_problem_x, small_problem_y, and small_problem_z.
Approach each problem as if it was independent of the others- and if they aren’t independent, then you need to break them down even further. Focus on one problem at a time, and don’t even think about the others until you’re finished with the first. That way you can focus on one small detail at a time instead of the hundreds of things you need to do to solve your original problem.
Only when you have each separate problem solved, completely individually, then you should start thinking about combining them to solve your first big problem.
… also, when you see the little pieces in front of you, you will ofc understand the big picture better - but also, once you reflect on a thing from different views, you will come up with new ideas, which will be be better due to the deeper understanding of the rabit.
I’ll just leave this here, on a slight tangent 
http://techcrunch.com/2014/10/18/you-too-may-be-a-victim-of-developaralysis
Cas
This is why I never look at the big picture.
I must learn (and use!) LISP one day. Or Scheme or something. I had proper fun with it 20-odd years ago at University.
Cas
Clojure would be the obvious choice wouldn’t it?
Yes, perhaps it is. Though a grasp of its great granddaddy can’t be a bad place to start.
Cas
I think ill just let it settle down for a week , go back to programming in c++. Great book c++ primer 5th edition for anyone who wants to learn it.
Nothing worthwhile is ever built by someone who looks at the big picture.
Go away from your computer. Grab a piece of paper and start writing out what you want to do. Can you think of a prototype or minimal version of a game with minimalistic graphics and barely functional gameplay you could take as a starting point? Take that, then try to break it up into smaller parts, as Kevin suggested. 
Just think less. It’s as simple as that.
- Jev