MacroQuest64

Okay, this is going to be controversial, but i really don't care.

What was wrong with the variables as they were? In reality, nothing.
What has the variable change given us? In reality, nothing except a huge headache converting over a years worth of macros.

Plazmic, Kudos for the mapfilter, that is an outstanding addition. You are someone who has the respect of everyone here, myself included - but the language change was too great, and too sudden.

Having spoken to many people on this subject - i'm only iterating what people are thinking, but arn't saying.



MOTD

We've been chopping wood for hundreds of years, using axes, who needs a chainsaw saw anyway?

Congrats.... pointless response #1.

Re-read the post, taking note of the two points made.

<deleted>

Quality reply Kaitain, appreciate that.

I assume you mean #define (no flame intended). Yeh, it wasn't perfect, but by no means was it difficult to code. The lack of variables could have been a pain (although having >99 global variables would be bad in anyones 'book', even with the code update).

Without resorting to examples involving axes, chainsaws, arrows and shotguns, I think it's fair to say that people are, have been, and always will be, reluctant to change. Especially when its not totally unconceivable that the change is simply for changes sake (ie if it ain't broke). Backwards compatability>ALL, this has been proven time after time.


MOTD

sorry, I just considered it appropriate to answer a cliche with a cliche. :)

But if you want a specific example that, I believe, justifies the whole var change.

I htink ther changes will be more beneficial overall but to be honest i had just got to groips with the previous code and had 3 macro's whihc work, now as there is no documentation that is currently worth anything. I have no working macros

This change (specially the map - awesome) would be even better if people knew or could teach themselves how to code with it...

It took time for people to learn the last language too, and too often people were complaining that it didn't make sense to use something so archaic, rather then a standardized language. In other words, no matter what you do, someone is going to complain.

Yes, it's annoying to have to change the existing macros -- I've got around 6,000 lines of macros i've been _dreading_ going thru (and now have to thanks to 9th/10th patchs bleh).

But it's _worth_ it. No more worrying if i've assigned v50 to something else in some include file somewhere. This is a good change.

ok I know im new here and this is my first post....but I am interested in macroquest and I do read these forums alot.
I like most of you dislike the changes for the same reasons as everyone dislikes them, my macros dont work anymore haha.
HOWEVER I am not against the changes. Perhaps I am not looking in the right spot or am so ignorant that I couldnt find it, or maybe just lazy but I wouldnt mind the change so well and could accept it if at least there were a manual or help file that is updated to reflect current code standards and commands/keywords.
Ill take a look through the directories again and see if I just missed something but thats the only thing about the change that leaves me down.
Also, i would like to thank the people that actually put time and effort into macroquest not only for hteir own use, but for the benefit of all of us leeches who just use and barely contribute. It was up and running within 24 hours of the patch and as I dont know much about code(I can understand simple scripts to make my own macros) I have no idea if making it work again was easy or hard but I thank you for your effort either way.

I view it this way. Im just gald to have mq. What ever the devs want to do then Im game.

I find my self not playing eq when mq is down. So if I spend a few hours learning something new good for me. If i spend a few hours fixing my macros so be it. Just so long as I have my MQ!!

Good job Devs.

There aren't any help files in the MQ download that will help you convert to the new format, but there are plenty of posts on the boards (from Plaz as well as many others) that point out exactly what needs to be changed. And, like always, reading other people's working macros is the easiest way to see what needs to be done.

So far it seems the vocal people like the change... how many of the quiet don't like it? and if they don't like it so much, why have they been quiet for the last 2 weeks?

I myself love the change. The v# system was archaic and you had to use arrays to get over 100 (I had to rewrite more than one of my macros due to this). Unlimited timers, unlimited arrays(1 and 2 dimensonal), and unlimited paramiters are all great additions. The $declared saves me a boat lod of lines. Another nice thing is having $ vs @. With some syntax highlighting you can now see which variables are user defined at a glance.

All in all I give the change 2 thumbs up.

Thanks

I'm all for it as well, tho having to rewrite some macros is a small price to pay.