Reign of the Undead - Revolution

Reign of the Undead - Revolution > Development > Modding & Mapping > Uninitialized Variable in C Argument ???
Full Version: Uninitialized Variable in C Argument ???
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

CrazyCoder

03-18-2018, 01:23 AM
Keep getting errors when rearranging files and split it them off to own scripts. This seemed to have happened after adding AWE Callback Override into CoD2 Merciless Mod 2. So I don't have to edit each callback from gametype and do "thread _mc2/_player:Tonguelayerkilled(blah, blah);"

It makes it so _players.gsc loads other scripts without cramming everything into gametype files.

https://github.com/PlusIce4/Merciless-Mod-2

Going to post the revisions in "Testnet" Branch:

https://github.com/PlusIce4/Merciless-Mo...ee/Testnet

fabio

03-18-2018, 09:07 PM
What errors do you get?

How did you override the callbacks? Normally you don't have to edit the callbacks

CrazyCoder

03-19-2018, 03:11 AM
(03-18-2018, 09:07 PM)fabio Wrote: [ -> ]What errors do you get?

How did you override the callbacks? Normally you don't have to edit the callbacks

Made a new thread to explain the callback override. I think my issue may be is putting the level stuff in the parenthesis.

Code:
Something ( self.origin, model.range, level.mm2_something_range, model)
{
// code here
}

fabio

03-19-2018, 09:35 AM
Hm yea that's clearly wrong. You don't have to pass level. variables to other methods. level. variables are globally and accessible everywhere.

Additionally you have to define new variable names for the method arguments. For example like this:

Code:
// we call te method here
Something ( self.origin, model)

// the method
Something (origin, model)
{
// code here
// level.mm2_something_range = defined
// model.range = defined
}
Reign of the Undead - Revolution > Development > Modding & Mapping > Uninitialized Variable in C Argument ???