Just read Lax's post... the only one I'll bother reading and/or responding to. Lax, when I saw that childish bullshit pop up on my screen, I thought "Man... Somoeone's gonna be in deep shit when Lax sees that." I was so confident in your abilities to manage this project and keep adding use...
hahaha word to to the wise all newcomers... GOD FUCKING FORBID you EVER overlook something or ignore ANY piece of information you are given. Read EVERY FUCKING LAST LETTER of every document you are EVER given PERIOD on here. In fact, do everything you can to make the learning experience as inconveni...
Well, I didn't bother reading any of the above posts, as I'm sure they're about as helpful as changes.txt... As soon as I saw they were more than 3 sentences long I immediately lost interest considering they have nothing to do with the task at hand... You can't believe I didn't read changes.txt? I c...
Do you read changes.txt twice a week (sometimes more) as new builds are posted? Regardless of your response, I know the answer is "no" so no response is needed. I never dreamed I would have to disable a "feature" of MQ to get it to operate (or at least show debug messages) normal...
What's with the "RTFM JESUS CHIRST MONKEY FUCKER" garbage coming up with debug messages now? When I go to convert old macros to MQ2Data I have to scroll and scroll and scroll to find out what the problems are and what the parser doesn't like so that I can fix it, and every message is surro...
Just quick FYI... /define KitePath array2 @KitePath(@Param0,${Math.Calc[@i+1]}),@KitePath(@Param0,@i)) ...caused me to lose a couple pretty decent-sized clumps of hair. The parser does *not* like to evaluate MQ2Data calls while referencing array elements... quick fix... /varset tmpy ${Math.Calc[@i+1...