If we are to teach NickLee1983 to "fish", I believe that it is best to start at pseudo code.
This is where you write out what you want your program to do step by step. When you do this, try to avoid loops (except for the main one with the Arduino). This helps fault finding later on.
When I post pseudo, I always start it with (pseudo) and end it with (/pseudo), so that everyone knows where it starts and finishes.
To get you started, I believe that this is the way to go:
If button is being pushed
if button is still being pushed
set flag high
wait for button to be released
if flag is high
increment button counter
if counter is more than the maximum value (4)
if counter is 1
(what would be in loop1...)
if counter is 2
(what would be in loop2...)
if counter is 3
(what would be in loop3...)
if counter is 4
(what would be in loop4...)
Back to start
This goes through and updates the counter every "loop" (from "start" to "back to start".
The parts "(what would be in loopx...)" only get run if the counter is on the right number.
Notice that I do not take what the button is saying on face value (to avoid Impulse noise and bouncing)
The "flag" is just a Boolean variable.
Does this make sense?
Teach a man to pseudo, and he can code for life. Don't teach him pseudo, and he can't catch fish... or something like that...