LegacyMq2

Lacky · Post by **Lacky** » Mon Nov 21, 2005 7:53 pm

So with LegacyMq2 could one run multiple macro's as you can with IS scripts? and is there any lag? I am going to play with it but it will be limited without things like /stick and others from plugins.

Lax · Post by **Lax** » Mon Nov 21, 2005 7:59 pm

ISXEQLegacy implements the MacroQuest 2 script engine. It changes none of the properties of the MQ2 engine, as it is using MQ2 code directly. This means that because you can only run one MQ2 script with MQ2, you can only run one MQ2 script with ISXEQLegacy. The memory usage and execution speed (lag, etc) are going to be identical to using MQ2.

This is more of a crossover solution than a permanent way to switch to ISXEQ. Ideally, anything NEW would be written for ISXEQ instead of the Legacy MQ2 engine, which means you would get the full benefits of Inner Space and LavishScript. But, this does provide a way to begin experiencing ISXEQ while not losing the features of MQ2.

Lacky · Post by **Lacky** » Mon Nov 21, 2005 8:50 pm

The plugins and what not would still need to be switched over though? When we get enough interest to get plugin /command to work that is. Or will the Legacyeq allow us to load mq2 plugins as well?

Red-One · Post by **Red-One** » Mon Nov 21, 2005 9:00 pm

Currently ISXEQLegacy does not support plugins, although it is possible with some changes. Ideally it would be best for folks to convert plugins to use in Innerspace.

Realistically, for the author of the plugin, it would be simple to convert. So far I haven't enountered much other than having to change the way arguments/params are handled, and a tad bit of the logic, but what I have done so far aren't extremley complex plugins that use structs/types and stuff.

In my opinion there would be little accomplished by having isxeqlegacy support plugins.

-Red

Lax · Post by **Lax** » Mon Nov 21, 2005 9:01 pm

ISXEQLegacy does not CURRENTLY allow you to load MQ2 plugins. However, if people show an interest in this, I can fairly easily modify ISXEQLegacy to load them.

Plugins ideally should be converted as well, yes, because ISXEQLegacy is only for the legacy scripting engine -- the commands and such are only added to that engine, and not to Inner Space. So, you couldn't type /stick and have it work

Lacky · Post by **Lacky** » Mon Nov 21, 2005 9:07 pm

Hmm ok that is some food for thought. I am thinking about trying to port Autobot over to IS but in its current form it uses ALOT of plugins :) I will look at exactly which are needed and which arent under IS. Autobot working under IS would probably get alot more ppl interested in IS and seeing the light that is InnerSpace.

LegacyMq2

LegacyMq2

...