Were we left out?

aChallenged1 · Post by **aChallenged1** » Sat Sep 23, 2006 8:18 am

The new release of MQ2 does not compile for ISXEQ without changes.

The changes that I've made, according to someone who knows what they are doing, allowed me to compile. However, as soon as I run my startup script it crashes.

What my startup script does is loads my HUD, my XPTracker, and my extensions.

I have not recompiled my extensions.

fearless · Post by **fearless** » Sat Sep 23, 2006 8:58 am

Come on man, you know the right way to post about bugs or crashes. Errors, changes you made, whatever else needs to be posted.

aChallenged1 · Post by **aChallenged1** » Sat Sep 23, 2006 9:10 am

I'm not doing a bug report. I'm asking a straight forward question.

You can't even build ISXEQ without modifications.

I you want to see what the mods were
http://isxeq2.twonk.net/paste/271
there you go.

I just logged in again, and only loaded isxeq (ext isxeq) and crashed.
Maybe later I'll do a bug report. But this was not a bug report, it was a question, because MQ2 compiles normally, while ISXEQ does not "out of the box".

Red-One · Post by **Red-One** » Sun Sep 24, 2006 4:30 pm

I just got back from being out for a couple days so I'm not 100% what is going on other than the expansion release. I will say that judging by the release notes for MQ2 that we were not "left out", typical fixes to MQ2 also affect ISXEQ since they use the same code in a lot of places. However, there are places where ISXEQ has its own code (think commands and such), therefore those places would have to be updated if there were changes in the ways things are accessed, and it looks like that is the case here.

So to fix it, you probably have to run a diff and figure out where the changes are that didn't make it to ISXEQ areas, then update them.

-Red

Lax · Post by **Lax** » Sun Sep 24, 2006 5:13 pm

The problem is that none of the active devs use ISXEQ. They update the MQ2 code, and then certain changes have to be merged into cvs when ISXEQ users post them.