Hi Lax.
Many people in IS Mods.com are wondering if it would be possible for you to give us a "heads" up before updates? The recent update to 1.06 rendered latest ISXEQ2 useles. Amadeus needs a couple of days to work things out with a new one. In the mean time we are kinda screwed:) Please advice as to how this can be prevented in the future.
Thanks
Request for Lax
Moderators: Lavish Software Team, Moderators
The funny thing about this is that the last few ISXDK updates have been hashed out a week in advance with the Development (unstable) release, AND Amadeus is aware of that fact. So not only is the answer "I already did", the answer is also "Amadeus refuses to do it in advance."
Like he posted on the forums, he doesn't care about the advance development release. He told me he'd rather work out the problems when it goes stable. So... that's what happens. All the other extensions get posted in advance, there's nothing more I can do to get Amadeus to update his in advance.
Please dont place the blame on me, I do everything I can.
Like he posted on the forums, he doesn't care about the advance development release. He told me he'd rather work out the problems when it goes stable. So... that's what happens. All the other extensions get posted in advance, there's nothing more I can do to get Amadeus to update his in advance.
If you want to complain about the issue, complain to him, and tell him that when there's a new ISXDK, he needs to distribute an unstable build of ISXEQ2 when the ISXDK is finalized. He doesn't have to "keep up with unstable builds", I tell him when it's finalized, he just simply says no to me.If Lax has patched the STABLE version to require an update, I'll recompile when I get home. I'm afraid that keeping up with unstable builds doesn't interest me much personally so isxeq2 will always be for 'stable' builds unless there is an EQ2 or ISXEQ2 specific bug that is fixed in an unstable build that begs for the update.
Please dont place the blame on me, I do everything I can.