Inner Space vs. MQ2

[PureVirtual]

I've read on the MQ2 boards that Sony has implemented a new detection technology that tracks interceptors.

I've been considering switching from using MQ2 to using Inner Space. I'm an experienced Microsoft-centric systems programmer and, from an aesthetic stand, I prefer the Inner Space architecture to the MQ2 architecture.

Is Inner Space affected by this technology? And if so, what is your recommendation regarding using Inner Space? And, do you intend to implement a work around that will bypass Sony's new technology?

[PureVirtual]

I apologize for posting the previous posting in General. It more appropriately belongs in the Inner Space section.

[fearless]

Is Inner Space affected by this technology?

IS is NOT affected by this. ISXEQ (which is just MQ2 compiled to run in IS), is affected.

And if so, what is your recommendation regarding using Inner Space?

Any time you run third party code (in this case MQ2 / ISXEQ) inside the memory space of another application (IE eq) you are at risk of being detected. There is no recommendation to make as this is something that you have to answer for yourself and for your accounts.

And, do you intend to implement a work around that will bypass Sony's new technology?

There is nothing for Lax to implement from the IS perspective. This is an extension problem and the maintainers of the extension need to fix it, and they are working on it.

You are welcome to pitch in on the ISXEQ side of things (I know the MQ2 dev's routinely take diff's to fix ISXEQ issues ) or you are welcome to create your own extension for EQ.

[fearless]

I apologize for posting the previous posting in General. It more appropriately belongs in the Inner Space section.

Moved to IS section for you.

[qwkhyena]

I'm sorry to jump in here; however, if SoE can detect ISXEQ they can also detect MQ2 right? I.E., both are memory hackers right? I mean, you stand just as much of a chance of getting banned for using MQ2 as you do using ISXEQ? I started reading this thread and got confused on who is detectable by SoE and who isn't.

From what I've seen w/ MQ2, if you're generally keeping your head low, not doing active memory hacks (just passive hacks) and always at the keyboard SoE will leave you alone. I'm also getting ready to embark on using Inner Space technology w/ ISXEQ and write my own macros. Looks like lots of the plugins I'm using have already been converted over. I've been having all sorts of macro sluggishness lately and could really use a speed boost (plus: the Lavish Script looks more familiar to me then MQ2 scripting!)

-QH

[fearless]

if SoE can detect ISXEQ they can also detect MQ2 right?

ISXEQ and MQ2 are the exact same thing, which I said above (ISXEQ (which is just MQ2 compiled to run in IS), is affected.).

Inner Space itself is NOT detectable by SOE. Inner Space falls in to the same category as WinEQ2 to a certain extent.

When you add ISXEQ to Inner Space you start to encroach into EQ memory space, which IS traceable to some extent.

Hope this clears it up for you.

[qwkhyena]

Perfectly! Thanks Fearless!

I've been getting all hot and bothered about IS today and ran across this thread and got confused (and scared!)

Everything I've read so far about IS w/ ISXEQ running under it looks impressive! I already need to do a complete macro rewrite so I figured why not enjoy the zestyness of Inner Space