You suck. Lol, ok. Your right. I threw that together in minutes without even testing it... Overlooked the pipe sign for singling out the exact spell name. Anyway, forgot about the not having to send params no biggie. Thanks for the correction and substitute implementation of a command. :shock: - Jala

I love a chance to show off the INI functionality in use. Here is an example of doing what you mentioned in your request using INI file access. There isn't much to it but I wanted to show that it could be done fairly simply with INI. Here is the code: |** [7-6-2003] Thanks to Valerian for catching s...

We have changed a few things in the script and I have also included a macro that will display all of your path names for you so that you may easily recall them when using the walkpath macro. Files included are: recordpath.mac walkpath.mac paths.mac RECORDPATH.MAC | RecordPath.mac | by BlueSkies and ...

Im sorry to keep this going I just don't like people trying to TELL me something when they don't even know what they are talking about. Appendix A: Macro Example |** Filename: skillbuild.mac ** Orignally written by Plazmic ** Bastardized by Rizwank ** Please note : This script doesnt use real items....

I see he was asking something different then I initially thought. Though I did take the time to try and answer what I thought he was asking.. Couldn't you do the same? And the point still remains! The information that he was looking for is stated in the manual. Sub Event_Chat: Event callback for mes...

ex: #chat ooc
ex: #chat tell


______________

rtfm

The point of using INI is that you could add mobs to your list on the fly and they are stored for later access. Not to mention the size of the macro would be reduced to about a 6 line loop. :p

Just wanted to add that these two scripts can be used with the latest CVS release of MQ.

Impressive. These are some great additions to MQ. I'd like to thank you again for taking interest in this and giving us a hand.

Damn, thats a bit harsh :p You'll have to forgive the strcpy mess that you were obviously referring to (and thanks for cleaning it up). Thats what a total lack of C++ knowledge will do to you. :p We have never programmed in C before this. FYI When I wrote out that iniexample.mac I was thinking the s...

Threw together a complete command and function example script for your enjoyment... | INI command and function example | by Jalapeno | | INI command and functionality | by Jalapeno and BlueSkies Sub Main |You might want to change the drive letter or whatever... /varset l0 "c:\newini.ini" |...

Thanks for the input Valerian it's always appreciated. We had thought about adding that in earlier but we were focused on other problems at the time and lost track of it. If no one else gets it we might look into adding the functionality in the future. We have a few other projects were trying to foc...

This is a moot point. File I/O; the fact still remains it COULD be (very) beneficial to have file I/O. This is why myself and BlueSkies have decided to implement it ourselves into the source. We will be doing INI file access to begin with then we might move to full File I/O. (Which might not be nece...

File I/O to me is an obvious benefit to writing scripts. It opens up a world of possibilities. One of which is recording and playing back PATHs. =)

I vote yes for file I/O... Since I'm working with BlueSkies on implementing it anyway. =p

It just occurred to me... With INI support being so easy to implement (a couple of VB programmers with minimal C++ experience could do it), why hasn't it been done already? It took up the better part of 4 hours to do, and we only have one unresolved bug that I'm sure is something that came about on...