more troubles then fixes ... DOH!

azwildfire · Post by **azwildfire** » Tue Nov 04, 2003 1:46 am

I wanna voice my opinion but not sure where this goes...

I appriciate Lax's efforts in making MQ more wonderful for everyone and knows he had great intentions....

however... a lot of us who use MQ fit the profile of people who HATE being FORCED to do anything

i hated being foreced to use the window, but now you can turn it off, great feature. same with Max FPS etc... and now, the new who... uses colors that are not the same i had setup before.... i am sure there was a reason to change who color in MQ... but... i LIKED being able to change MQ colors in everquest.... now i cant. i have to manually edit code and re compile blah blah... just to change a color? phewy

also, i liked being able to send MQ text to diffrent chat windows.... cant do it anymore and my guess is related to MQ chat window. mq text will ONLY go to active chat window *my UI uses 4 *

soooooo i was hoping that this big ol' mess of a week with MQ would perhaps motivate some of the devs to try something out first before putting it in the zip? and just load it up. i am sure all of us could have waited a few days for the MQ window to avoid having soooo many crashes, whining people *like me

* and etc.

and has anyone tried to /echo %t or any "%" command that is EQ related? like %t %s etc.... they dun work

sooo... that is another thing i used a heap that is all poopy... i myself rather type %s then $target(gender) or %r rather then $target(race) etc... i used /echo blah blah in my macros and ... now they all pop up with the %s etc.

these are not "feature" requests... but they were existing features i loved and was happy with and now all fuxxored

and the default for /face fast made me look at z radius too... i dont give a crap about z radius. you know how irritating it is to use an auto fight macro and fight a giant when shrunk and your char is looking up at the giants head? sure i was able to go through and re edit my macro to work... but i am sure down the road it will change AGAIN and again i will have to edit all my macros.... do ya see what i am saying?

i guess the solution is to never recompile... but then when EQ is re patched and i want struts... i enter em by hand... or i download the irc.zip along with all these new features that mess with my CHI

i think my hope is... maybe when all these new great features and changes come out we can have some backward compatability? that seems to be what most of my "issues" are...

thanks for your time.
i am NOT dissing anyone. as i said the work here is fantastic... just my input and my feelings that have evolved over the last week or so

Cheers!

Lax · Post by **Lax** » Tue Nov 04, 2003 2:07 am

K well, my turn I guess.

I use custom colors in EQ. Let me explain a few problems with that and the old MQ system. Relying on WriteChatColor for colors and filters is bad. You couldn't differentiate between a filter and a color. Lets say you want to filter something to another window that MQ happens to be using as "concolor blue". . MQ's blue gets sent to that window. You could have a /who display going to 6 different windows, and some of them not displayed at all.

The solution to that problem is to use the actual colors instead of an EQ chat filter. This is the direction we're heading with MQ. The functions that call WriteChatColor and use the color as the filter should still keep the old color, but I think we lost that somewhere (it needs to be put back).

Next, GM's have the ability to read any visible text in your chat window, most notably if you use /report at all. Obviously, don't use /report. But as a more realistic solution any window they don't have access to is safe.. this is solved by the MQ chat window... which you can turn off.

The final thing needed for this system is to create a MQ filter system, to display things in other windows, etc etc. Trust me, it's being worked on.

MQ is an open source, ever evolving project. You take the bad with the good, and if you are accustomed to something and like it a certain way, expect to have to do some degree of modification. Quite simply, there are hundreds of people who like it one way and hundreds who like it equally opposite. There's no possible way to accomodate every person's nitpickiness, not in this project or any other. All I can really say is, if you are so vocal about wanting things to not change, don't get involved in open source.

In the meantime, we're working on things that will make you happy in the end. I'm working on a lot of UI related stuff, and eventually a lot of MQ options will be integrated into the UI system. Chat filters, etc should be integrated into context menus (right click menus). You can wait patiently and be happy with the good things that come, but I really can't say I think anything good comes out of complaining that MQ is evolving.

Sorry if things change in a way that you don't like, I think you will like it in the long run.

Slice · Post by **Slice** » Tue Nov 04, 2003 9:00 am

Also, you don't have to download every new version of the cvs that's posted. I'm still running with the Oct 12th build which was a stable release after the last patch. I won't be upgrading until the next patch and then I'll read up on the new changes since Oct 12th and make any modifications. Give the devs time to tweak their new features. You don't have to recompile every day to see what the latest and greatest changes are.

Plazmic · Post by **Plazmic** » Tue Nov 04, 2003 9:37 am

Slice, yes you do ;) at least if you're me ...

bob_the_builder · Post by **bob_the_builder** » Tue Nov 04, 2003 9:46 am

You don't have to recompile every day to see what the latest and greatest changes are.

/snaps his fingers

Well damn , I could of sworn I had to, maybe its just in my nature.

Anyways, no you dont have to. And you can always keep backed up zipped versions so you can go back incase certain functions don't work. Or keep them all in diffferent directories based off the build date.

So many things you could do when you "gotta have the latest" but scared it "may break something".

Keep up the good work folks, a moving project is > a stagnant project.

/places two thumbs up and grins from ear to ear

Wont this work also for back rev versions?

http://macroquest2.com/downloads/

Bob

tehHax0r · Post by **tehHax0r** » Tue Nov 04, 2003 2:15 pm

I agree Plaz

shuttle · Post by **shuttle** » Sat Nov 08, 2003 12:06 am

just one question.

how do I get a /face that does not look up/down?

shuttle

MacroFiend · Post by **MacroFiend** » Sat Nov 08, 2003 12:19 am

/face nolook

Amadeus · Post by **Amadeus** » Sat Nov 08, 2003 1:27 am

This thread makes me want to kill halflings in large quantities.

NotSoCSharp · Post by **NotSoCSharp** » Wed Nov 12, 2003 11:45 am

The nolook option for /face is not in the readme.html. Adding it might prevent more questions like the one above. I had the same question until I found this thread.

vzmule · Post by **vzmule** » Wed Nov 12, 2003 2:36 pm

I initially agreed with the author of this thread last week as it wasn't stable and gave us more things to have to fix when sony messed with things...but now that the initial bugs worked out, after seeing how knowledgable Lax is and now that the new code is toggable, I welcome his contributions to the project.