DaddyFreedom wrote:Mate, you wouldn't believe it, but one simple little mistake that I manage to pick up from another member here in the forum, in another post posted earlier today regarding L3+ Set up. I was able to pick my simple mistake. Instead of having the url as: stratum+tcp://prohashing.com:3333
I had it as: stratum+ltc://prohashing.com:3333 No wonder I couldn't get it going. lol
But of course with your help I also added in the password field: n=worker1 a=scrypt and the "k=" for the API key requirement.
Also now I notice that the Average Mining Efficiency is 100% which is awesome, as last time I was only getting around 97%, I guess cause I had it set in the password field with a lower "d=" value.
I really appricate your help. Cheers!! Let the L3+ mine like a pro. 
You don't really need a=scrypt in there because if that wasn't in there, it'd default to scrypt. As far as i understand, a= is only necessary if you are mining x11. Per prohashings own help page:
"a: selects an algorithm for mining. Supported algorithms are "scrypt" and "x11." If this argument is not provided, the default algorithm of scrypt is used. "
Not saying you SHOULD take it out, since it'll work, but you don't need it.
As well, k= isn't a requirement unless you make it a requirement. Ironically enough, if you make it a requirement, it means no one else can make money for you without you giving them the API. Now, i'm not sure WHY someone would make money for someone else, but i just don't see any value at all in using k= since again, it doesn't hurt you if someone else decides to work for you and give you money, it only hurts you if you prevent it with k= and someone, for some unknown, illogical reason decides to work for you and give you money lol