Just looking at the code I can maybe see why its crashing.
First let me try and explain to you guys what happened over time with the BroadcastHandler and the drastic change Epic did to it in 3339.
In UT1 there was no BroadcastHandler or anything that a Mutator could do to intervene with the screen messages and we all complained bitterly to Epic to change this in UT2003.
UT1 had a Message class but it was only available to Mods (Games) and it only loaded after the game had started and this sucked, as the more advanced coders could not even 'hack' it.
When UT2003 came out, it had a BroadcastHandle which was all chinese to us as we did not know how to interface into it so most mods just treated it as a UT1 Message class.
It was EL Muerte that eventually broke through to this handler and past the good news onto me but still we were not interfacing properly as it still only allowed one chat type program at any one time.
So between EL Muerte and myself we developed a multi manner for everyone to use the BroadcastHandler (he did most of it).
It was very simple and basically all we did was as follows:
MyMutator Starts up.
Have a look at the BroadcastHandle and see if anyone owns it yet.
No - I'm the first so I own it and others will hook into me.
Yes - someone does already own it so now I make a note of its address, store that address, use the BroadcastHandler for whatever purpose I want to use it for and when I'm finished I call the address that I stored.
In this way a zillion mutators could use the BroadcastHandler except on the odd occasion where a author did not know how to chain with everyone else and was to dumb or proud to ask how and owned it all to himself and we all lost out.
Anyway we soon passed the message to the modders on how to do this and by the time UT2004 was released everyone knew how to do this and we all lived in harmony.
During the development of Patch 3339 by Epic, their programmer suddenly decided "Hey I believe the modders are having problems with the BroadcastHandler - mmm let me make it nice and easy for them to use"
Grrrrrrr what an allmighty cockup.
The idea was good, their intensions were good, but it was a little too late as we had already done our thing.
What they did was add a routine where you have to Register your BroadcastHandler with theirs (the original) and then you can use yours and when done call the next one in the chain. Very similar to what we were already doing but instead of doing it via a memory address, you call a physical address.
Looking at the code of mods out there ONLY Zound47 had followed their new rule which screwed everything up.
So now for those modders who have spotted the new rule dont know which way to go, so that why Zound48 now looks to see what the handler looks like, memory or physical - lets hope it works.
Now getting back to the crash........
Zound starts up, it registers its BroadcastHandler with Epics one as required.
That BroadcastHandler now spawns and it tells the Game that "Hey I'm now your new BroadcastHandler"
Spot the error ?
The Zound BroadcastHandler has registered itself with itself and this now goes into a loop and will eventually end up in a crash.
Beta 3 will now be identical to Zound46 BroadcastHandler and to hell with Epic and their stupid moves that come 18 months too late.
First let me try and explain to you guys what happened over time with the BroadcastHandler and the drastic change Epic did to it in 3339.
In UT1 there was no BroadcastHandler or anything that a Mutator could do to intervene with the screen messages and we all complained bitterly to Epic to change this in UT2003.
UT1 had a Message class but it was only available to Mods (Games) and it only loaded after the game had started and this sucked, as the more advanced coders could not even 'hack' it.
When UT2003 came out, it had a BroadcastHandle which was all chinese to us as we did not know how to interface into it so most mods just treated it as a UT1 Message class.
It was EL Muerte that eventually broke through to this handler and past the good news onto me but still we were not interfacing properly as it still only allowed one chat type program at any one time.
So between EL Muerte and myself we developed a multi manner for everyone to use the BroadcastHandler (he did most of it).
It was very simple and basically all we did was as follows:
MyMutator Starts up.
Have a look at the BroadcastHandle and see if anyone owns it yet.
No - I'm the first so I own it and others will hook into me.
Yes - someone does already own it so now I make a note of its address, store that address, use the BroadcastHandler for whatever purpose I want to use it for and when I'm finished I call the address that I stored.
In this way a zillion mutators could use the BroadcastHandler except on the odd occasion where a author did not know how to chain with everyone else and was to dumb or proud to ask how and owned it all to himself and we all lost out.
Anyway we soon passed the message to the modders on how to do this and by the time UT2004 was released everyone knew how to do this and we all lived in harmony.
During the development of Patch 3339 by Epic, their programmer suddenly decided "Hey I believe the modders are having problems with the BroadcastHandler - mmm let me make it nice and easy for them to use"
Grrrrrrr what an allmighty cockup.
The idea was good, their intensions were good, but it was a little too late as we had already done our thing.
What they did was add a routine where you have to Register your BroadcastHandler with theirs (the original) and then you can use yours and when done call the next one in the chain. Very similar to what we were already doing but instead of doing it via a memory address, you call a physical address.
Looking at the code of mods out there ONLY Zound47 had followed their new rule which screwed everything up.
So now for those modders who have spotted the new rule dont know which way to go, so that why Zound48 now looks to see what the handler looks like, memory or physical - lets hope it works.
Now getting back to the crash........
Zound starts up, it registers its BroadcastHandler with Epics one as required.
That BroadcastHandler now spawns and it tells the Game that "Hey I'm now your new BroadcastHandler"
Spot the error ?
The Zound BroadcastHandler has registered itself with itself and this now goes into a loop and will eventually end up in a crash.
Beta 3 will now be identical to Zound46 BroadcastHandler and to hell with Epic and their stupid moves that come 18 months too late.
Last edited:
