Post
by Lax » Sun Feb 27, 2005 3:11 am
ISXEQ itself *is* MQ2. It is converted, however, to the Inner Space architecture. There's plenty that Inner Space does that MQ2 doesn't do. There's plenty that LavishScript does that MQ2's macro system cant do. So the difference doesn't really lie in ISXEQ itself, but rather the foundation it is built upon.
The announcement titled "What is ISXEQ? What will happen to MQ2?" describes a few of these things.
There are some things in ISXEQ that cant be done in MQ2, for example the data type members. This is more for scripting (aka macro), but consider targeting with MQ2. First you find the spawn you want to target. Then after you've already found it, you use the /target command, which has to find it again. With ISXEQ, you can use the object directly, such as entering the command "Me:Target", or "Spawn[Merchant Tekram]:Target"
The rest you would have to ask questions about LavishScript or Inner Space, or take a peek at the wikis describing them.
For a random MQ2 user that does nothing but use what is already there, and only for a single session, and doesn't use macros, the answer would currently be "nothing".