Okay, so any int will get floored. That's what I thought, but I thought maybe it would just carry that as declared instead of resolving it before moving on. Does this mean I have to do book keeping on extra zeros all the way through until the final calculation then divide? I of course will need to keep them under the 65,535 limit or assign them as long if they are over that value.
I was afraid the declarations would have to be made in order of use. I was hoping to keep the code organized in a meaningful way so if and when other folks use the code they can easily alter the values to suit their application. Is there a way around this? Maybe something like making a library so I can insert all of the values and relationships in a header then change the values in the code? My inexperience with coding leads me to struggle with seemingly simple things like this. I am sure there is a way to resolve things like this and have it make sense to end users.
For the value of Pi I just looked up how to define Pi in arduino. I found it here. There is a <math.h> library, should I just include that to reference Pi using M_PI?
So if I understand correctly appending a value with UL forces it to be an unsigned long? Is it just good practice to do so? If not why bother writing const unsigned long variable = ### when I could just write const int variable = ###UL?
Why would I multiply stepperOutputPulley by 1000? Is that to inflate the value so as to avoid decimals, and book keep in the naming? Thanks for the guidance, sadly I feel like you probably could have written this code quicker and more succintly than you could help me figure out how to write the code 
. I appreciate it nonetheless.