[IG]Intergalactic Morons WIP Thread

[ShadowSpartan]

Open Sauce can already do Multi Team Vehicles so this is nothing new and not that exciting.

[musicman888]

I shall not argue with you on that ShadowSpartan, but I will say that I do not think that everyone can use Open Sauce effectively. If you can "yay! Good for you." But this will be an easy to use app that anyone can use. Just saying...

[Jelly]

Do you plan to release the IGM programs as closed-source tools, or are they going to be open to the community?

I'm not bothered either way, but it might be useful for some of the other coders here if they can see what you're doing and how you're doing it.

[ShadowSpartan]

I shall not argue with you on that ShadowSpartan, but I will say that I do not think that everyone can use Open Sauce effectively. If you can "yay! Good for you." But this will be an easy to use app that anyone can use. Just saying...

So opening an app and having to enable MTV is easier than just placing a dll in your Halo CE directory and instantly getting MTV? I think not.

I'm not bothered either way, but it might be useful for some of the other coders here if they can see what you're doing and how you're doing it.

If I recall correctly from looking at Open Sauce's code, to enable MTV you need to change about 3 bytes. Not very complicated.

[p0lar_bear]

If I recall correctly from looking at Open Sauce's code, to enable MTV you need to change about 2 bytes. Not very complicated.

IIRC I think MTV is enabled by default.

e: o.

[ShadowSpartan]

IIRC I think MTV is enabled by default.

No I mean, in order to make MTV work, Open Sauce edits 3 bytes in the memory. MTV is enabled by default, but I don't think adding a toggle option would be very hard.

[Kornman00]

Um, you may want to actual test MTV's effects in campaign. IIRC, for OS anyway, the code it changes can have drastic affects to how the AI's code executes. Potentially the AI could wrongly accuse you of being an ally in some cases.

[Pooky]

Um, you may want to actual test MTV's effects in campaign. IIRC, for OS anyway, the code it changes can have drastic affects to how the AI's code executes. Potentially the AI could wrongly accuse you of being an ally in some cases.

If that means the AI would accuse me of being an ally while still killing the stupid Marines, I'd be all for it

[Lateksi]

If that means the AI would accuse me of being an ally while still killing the stupid Marines, I'd be all for it

The official make-aliens-go-high app.

[IGMBiti]

Open Sauce can already do Multi Team Vehicles so this is nothing new and not that exciting.

In response to that: Abyll had attempted to use the code in Open Sauce. It worked successfully for the dedicated 1.08 exe, but it caused exceptions when he tried to patch the client. I'm assuming that the address for the 3-byte change on the client (1.08) was off by a bit.
As far as choosing an executable instead of a DLL...I was originally planning on using a DLL that would be loaded using another project of ours (haven't released yet), but just because I was lazy at the time and I thought it may be more convenient for people who already have edited libraries and for those who do not want those libraries changed, I decided to use an executable.

        static MTV()
        {
            if (MemoryHandler.Version == MemoryHandler.HaloVersion.CLIENT)
            {
                MTV.INSTRUCTION_ADDRESS = 0x0056A3B1; //client address
            }
            else
            {
                MTV.INSTRUCTION_ADDRESS = 0x00518D41; //dedicated address
            }
        }
/* Addition: I think I could simplify this:
MTV.INSTRUCTION_ADDRESS = (MemoryHandler.Version == MemoryHandler.HaloVersion.CLIENT) ? 0x0056A3B1 : 0x00518D41;
*/

I'm not sure if those tags would work, but that's the constructor I used for a static class that enables/disables the ability. It sets the addresses if the intended target is client or dedicated.

Edit: Looked at Open Sauce's code (did not feel like making a new post to the one just after this):

FUNC_PTR(UNIT_CAN_ENTER_SEAT_MOD, 0x56A261, 0x56A3B1, 0x518D41);
#define FUNC_PTR(name, ce_offset, ce_107_offset, cededi_offset) enum FUNC_PTR_##name { PTR_##name = cededi_offset }; COMPILE_ASSERT( PTR_##name != NULL );

At the moment, the ce_107_offset matches the offset I have for client 1.08, and so I think that is what caused Abyll errors for the client patch.